Adam Yost

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

Software engineers fear the AI that will take their job while the real danger I see should be in companies and solution owners themselves. Products that you spent years and tons of dollars for buildng selling it for whatever the number of subscriptions is can now be easily cloned and it costs nothing but the Gen AI subscription and some small resources. I am really curious of how the scene will look like after maybe Q2 of 2026. The development that business owners needs to follow “not to fail in the common nokia example” is now talking days not years like all used before!! #ArtificialIntelligence #GenerativeAI #SaaS #StartupLife #ProductManagement  #SoftwareEngineering #TechTrends #DigitalTransformation  #Innovation #FutureOfWork #Entrepreneurship  

5

2 Comments

You don't need to hire a software farm for anything anymore. You need one developer who sits next to you for 6 weeks and learns how your business runs. Not how it looks in a deck. How it actually runs. The messy inbox system. The Notion doc nobody follows. The 4-step process your EA does manually every morning. A good AI developer, someone who works in n8n, Claude, and modern automation tools, turns that into systems that run without you. We placed one with a 12-person e-commerce brand. In 8 weeks he'd automated their order exception workflow, their influencer outreach follow-up, and their weekly reporting. The admin team is being trained in AI. Those that don’t adopt are gone. 3 tasks. Each one was eating 6-8 hours a week from someone on the team. That’s money in your pocket. 416h per year. That’s almost a full quarter's worth of work. A dev shop's savings don't matter if they can't ship. Ours do. I wrote more on this on more detail in the blog linked below: https://lnkd.in/gVpWJGZw DM me if you have been seeing AI happening in front of you and want to know how you can avoid missing out.

32

10 Comments

Developers weren’t just builders. They were gatekeepers. If you couldn’t code, you didn’t create. You waited. On engineering bandwidth. On roadmaps. On someone else’s priorities. Syntax was the wall. Know where the semicolon went? You shipped. Didn’t? You stood outside. That divide shaped more than workflows. It shaped status. Developers got the leverage. The scarcity gave them the power to decide what shipped and when. Everyone else adapted around them. It wasn’t about being smarter. It was about access — and access wasn’t evenly distributed. Some people were in the right rooms early, tripped into syntax, and built from there. Others never got the chance. That was the difference. But syntax was only the first kind of alpha. The second was quieter. Harder to see. More enduring. System knowledge. Knowing which database could survive Black Friday traffic. When to debounce vs. throttle. How to shard writes across regions. Not just writing code — architecting it. That’s the tacit layer. Built from war stories. Outages. Scaling pain. Years in the trenches. It’s still here. And it still matters. For now. I remember the first time I tried to shortcut it. I’d tell Claude what I wanted. It would spit out code. I’d paste it. It would break. I’d send back the error. It would try again. Loop by loop, something shifted. Reddit called it “copy-paste monkey.” They saw a hack. I saw a door opening. People who’d been locked out started building demos. Then products. Then real companies. The wall between “technical” and “non-technical” was never about intelligence. It was about translation. And now, translation is free. What matters now isn’t syntax. It’s clarity. How well you can think. Break things down. Iterate. That’s what the agent understands. And that’s what it rewards. The syntax advantage is gone. Developer privilege is flattening. System knowledge is next. Today, the agent can’t always choose the perfect database. But if you tell it the trade-offs, it will. If you give it context, it will architect with precision. That tacit edge still holds. But only for now. Soon, even that will be embedded. And leverage will shift again — to anyone who can think clearly enough to guide the machine. That shift isn’t coming. It’s here. And it’s not going away.

18

2 Comments

Your Rails app works. But it’s messy. Controllers are bloated. Models are doing more than they should. Every new feature feels risky. The problem isn’t Rails it’s where you put your logic. Policy Objects solve this by separating business rules into their own classes: Deciding who can edit or delete a resource Checking permissions based on complex conditions Making those rules reusable across controllers, services, and views Why it works: Business logic lives in one clear place Code becomes easier to test and maintain Adding new rules doesn’t break old ones Good Rails apps don’t just work. They stay clean as they grow. Policy Objects make that possible. #BilalAhmad #RubyOnRails #CleanCode #PolicyObjects #BackendEngineering #SoftwareArchitecture #DevBestPractices #BuildInPublic

8

1 Comment