John Suder

Every dev embracing AI is talking about Claude Code and OpenClaw. It’s very evident to me that Claude is the current winner in agentic software development, and OpenClaw is the clear winner for task automation. The thing they have in common isn’t the model they’re using; it’s the infrastructure, the ease of use, and how turnkey the systems are. I’ve been a primary user of OpenAI, but they haven’t done much to make using their models easier to interact with. That’s why I think bringing on the OpenClaw creator is one of the smartest moves they’ve made in the last year. Most of the consulting work I do around AI is about infrastructure and implementation. Very little of it is focused on generating a company’s “own model,” beyond some minor post-training or RAG implementations. And honestly, I think this year the biggest winners in the AI space won’t be the ones producing the models it’ll be the ones making them easy to use for low-tech and no-tech users. We’re at a point where the models are good enough to handle far more cases than we’ve actually put into practice. If I was a VC that’s where I would be putting my investment.

18

4 Comments

Most developers think a successful payment API response means the money has moved. It usually doesn’t. A 200 OK just means the request was accepted. The actual movement of money depends on the payment rail behind the transaction, and every rail behaves differently. 📝 Cards authorize instantly but settle later. 📝 ACH might take days. 📝 Real-time rails settle in seconds. 📝 Cross-border transfers can pass through multiple intermediaries. If you don’t understand the rail your payment runs on, it becomes easy to misread transaction states, retry incorrectly, or show users the wrong status. I just published a new guide for developers that breaks this down: “What Are Payment Rails? A Guide for Developers.” In the article I cover: • What payment rails actually are • How money moves from initiation to settlement • Why a successful API call doesn’t always mean a successful transfer • Push vs pull rails and how they affect system design • How to handle rails properly in APIs, webhooks, and ledgers If you build fintech products, payment systems, or anything that moves money, this is one of those concepts that makes a lot of confusing behavior suddenly make sense. Link in comment 👇

13

1 Comment

When a dev leads with “clean architecture,” I pause. If they push for the perfect setup before writing a single feature, I ask why? It’s not that quality doesn’t matter. It’s that context does. Perfect code doesn’t help if no one needs what you built.

7

4 Comments

"Angular is becoming Razor Pages." That’s what my teammate told me today. He was referencing Angular’s new @if control flow syntax and jokingly predicted the death of *ngIf by Angular 21. He ended his argument with the classic hot take: "Dotnet >>> Angular." I had to remind him why we chose Angular for our frontend. While the syntax might look familiarly chaotic to backend developers right now, the behavior is strictly next-gen frontend architecture. We aren't dealing with server-side rendering that requires a clunky full page reload every time a user submits a form. Angular provides an ecosystem that delivers a seamless feel that older backend technologies struggled to achieve on their own: ✅ True SPA Experience: No flickering reloads. The app feels native and fluid. ✅ Signals & Zoneless: We are rapidly moving toward a world where change detection is surgical and incredibly performant. ✅ Enterprise Dependency Injection: A structured way to manage code that other frameworks are still trying to bolt on via third-party libraries. ✅ Deferrable Views: The built-in ability to prioritize exactly what loads when (@defer) is a massive win for Core Web Vitals. We can borrow helpful syntax ideas from the backend, but the User Experience is pure frontend magic. ✨ Are you Team Angular or Team .NET for modern web apps? #Angular #WebDevelopment #RazorPages #UI #SoftwareEngineering #DotNet #Frontend #TechDebate #JavaScript #TypeScript

36

5 Comments

Your coding agent shouldn't spend 5 minutes on pip install before it writes a single line of code. We cut agent startup from minutes to seconds by pre-warming Docker containers with dependencies already installed. Here's how: https://lnkd.in/gd9DYMmC

5

Anthropic’s Coding Agents Level Up Developer Workflows Trend: Anthropic released updated Sonnet coding agents with longer context and stronger reasoning for developer tasks. Why it matters: Coding agents shift low-level coding from humans to supervised AI, changing hiring needs and review patterns. Question: Would you allow an agent to open a PR labeled “agent suggested” with human verification? 🔁 Repost if coding agents alter your engineering org design 🔔 Follow me for agentic engineering, review patterns and safety signals 🌟 Takeaway: Agents are helpers, not replacements, start with supervised PR flows

2

Coding agents make traditional READMEs obsolete. Not because documentation doesn’t matter. But because static summaries of dynamic systems don’t scale. READMEs today: • Go stale fast • Nobody wants to maintain them • Slowly turn into technical archaeology They’re snapshots of a moving target. Coding agents change the interface. Instead of reading a compressed summary, you can: • Analyze the codebase in real time • Trace git history for architectural intent • Ask “why is this like this?” and get contextual answers • Generate setup instructions dynamically No staleness. No maintenance burden. No drift from reality. So what happens to READMEs? Two paths: 1) They disappear. Onboarding becomes “ask the agent.” 2) They shrink. Documenting only what’s outside the repo (3rd-party configs, env variables, human processes). And even that may fade as agents integrate directly with external systems. The README’s original job was compression. Coding agents remove the need for compression. We’re moving from: “Here’s a summary of the system.” To: “Interrogate the system itself.”

20

28 Comments