James Avery

No-code platforms are selling a lie. Not entirely. But mostly. I just read through a roundup of 7 no-code app builders and the pitch is always the same: "Build your SaaS without coding skills." Cool. Except that's not how it works in reality. I've built products with actual code. I've also used Bubble, Webflow, and other visual builders. Here's what happens: You hit a wall. Fast. The moment you need something slightly custom, slightly different, or slightly more scalable than the template allows, you're either paying someone to code anyway or you're stuck. The real advantage of no-code isn't "build without developers." It's "get to market faster to validate your idea." That's it. That's the actual value proposition. If you're using a no-code tool to ship an MVP in 2 weeks instead of 2 months, that's brilliant. You'll learn what customers actually want before you've burned through your savings. But if you're thinking "I'll never need a developer," you're fooling yourself. Most of these platforms will eventually become a bottleneck. The honest pitch should be: Use no-code to prove the idea works. Then decide if it's worth building properly. https://lnkd.in/evZ-6vBC

3

Why Claude Opus 4.5 Has Become My Primary "Co-Architect." I was skeptical. Sonnet 3.5 was efficient. GPT-5.1 was flashy. But after running Claude Opus 4.5 (released just last month) through our production workflows, the verdict is in: It is legendary. But not for the speed. For the Reasoning Depth. In the agency world, we often deal with "Spaghetti Code" in legacy themes that have been patched together by five different developers over three years. Refactoring this is dangerous. One wrong move breaks the checkout. This is where Opus 4.5 separates itself. 1. The "High Effort" Parameter: Most models guess. Opus 4.5, when set to "High Effort," effectively simulates the code execution in its head before outputting the result. It engages in "test-time compute," exploring multiple architectural angles before committing to a solution. 2. The Contextual Integrity: With a 200k token window, I can feed it the entire schema of a custom app like JourneyGlow. It doesn't just see the file I'm working on; it sees the dependencies. It understands that changing a variable in product-template.liquid will break the map widget on the PDP. It can now do really incredible things if given the right tools and prompt. 3. The Cost of Intelligence: At $5/M input tokens, the economics finally make sense for deep, agentic code reviews. We can afford to let the AI "think" longer because the cost of a regression bug is infinitely higher. If you are still using generic models for complex architectural work, you are optimizing for the wrong metric. Don't optimize for speed of output; optimize for depth of thought. #ClaudeOpus #ShopifyApps #CodeArchitecture #DevOps #GadgetDev

1

One of my goals with On Rails has been simple: talk to the people in the trenches. The ones still shipping. Still learning. Still proving that Ruby on Rails can scale when you treat it with care. This week’s guests, Miguel Conde and Peter Compernolle from Gusto, live that story every day. They’ve evolved from one massive monolith into what they call a biolith — two Rails apps that power a platform serving millions. Along the way, they’ve refined how boundaries are defined, how teams collaborate, and how tools like Packwerk and Sorbet shape life inside large Rails systems. If you’ve ever wondered what Rails looks like at enterprise scale… this one’s for you. Listen here 👉🏻 https://lnkd.in/g-YMqcRN

6