Your app has an error. You paste it into an AI coding tool and say, "Fix this." That sounds reasonable. But what if the app correctly refused an invalid booking? What if an outside email service is unavailable? What if a customer is asking for a feature you never promised?
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend NOTE ON TIMING: LangGraphics isn't a weekend project. Its first commit is from January 2026. This year's rules ask for new projects built within the challenge window, so I'm not presenting this as a prize entry. I'm sharing it because the challenge asks the question this project was built to answer: who did you build it for? I built it for a group of people building an agent system on LangGraph.
In July I wrote about why I built verihook: every provider signs webhooks differently, and I was tired of maintaining five slightly different HMAC functions. Since then verihook has grown to 40+ providers, adapters for ten frameworks, testing helpers and a docs site. Supporting that many providers taught me where webhook verification actually goes wrong. It's rarely the HMAC. It's everything around it: the body, the secret, the URL, retries and tests.
In the previous post, I built the first real behavior for Platform Lab. A developer could create: apiVersion: platform.shubforge.dev/v1alpha1 kind: Application metadata: name: greeting-service spec: image: greeting-service:1.0.0 replicas: 1 port: containerPort: 8080 and the Platform Operator would create: Application | v Platform Operator | +------ Deployment | +------ Service That was the first point where the Application API actually resulted in real Kubernetes resources. But there was another important question. What happens when the Application changes? Creating resources once is useful, b
This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend My friend Shivin wanted to get into open source this October. He could code. What stopped him was everything around the code. He'd open a real project, see a long README and a hundred open issues, and the questions piled up before he wrote a single line: Which of these files actually matter? So I built him GoodFirst.
Discussion (0)
Log in to join the discussion and vote.
Log in