3,577 karma · joined October 24, 2009
Exactly. Even something as seemingly mundane as hosting your own email is a major challenge.
Should it not be the other way around?
"I need a caching component in my stack. Oh, I just let AI create it from scratch, so AI can also run it, maintain it etc."
or
"I need a caching component in my stack. Oh, let me just grab an existing, well maintained and supported cache component and let AI write the glue logic to run it, maintain it etc."
Personally I think it will be the second one. There definitely is a case for generating one off tools but I don't think AI will replace established, well written and maintained software (being it open-source or not).
Not all software is equal. I can get 80% of my new SaaS to be generated by AI as it's mostly considered boilerplate and mostly the same as any other SaaS. It's the 20% that makes it unique OR something that AI can't touch like a special relationship with a supplier or a first to market position etc.
What is really happening here is part of the Monroe Doctrine [1]. Trump is trying to consolidate the Western Hemisphere. Remember Canada being the 51st state?
It's in the lead in to the article.
> First, you should locate yourself on the chart. What stage are you in your AI-assisted coding journey? > Stage 1: Zero or Near-Zero AI: maybe code completions, sometimes ask Chat questions > Stage 2: Coding agent in IDE, permissions turned on. A narrow coding agent in a sidebar asks your permission to run tools. > Stage 3: Agent in IDE, YOLO mode: Trust goes up. You turn off permissions, agent gets wider. > Stage 4: In IDE, wide agent: Your agent gradually grows to fill the screen. Code is just for diffs. > Stage 5: CLI, single agent. YOLO. Diffs scroll by. You may or may not look at them. > Stage 6: CLI, multi-agent, YOLO. You regularly use 3 to 5 parallel instances. You are very fast. > Stage 7: 10+ agents, hand-managed. You are starting to push the limits of hand-management. > Stage 8: Building your own orchestrator. You are on the frontier, automating your workflow. > *If you’re not at least Stage 7, or maybe Stage 6 and very brave, then you will not be able to use Gas Town. You aren’t ready yet.*
So, 2026 is going to be the year I'm going to run this experiment on myself and see what I can accomplish with this way of working.
Why?
Someone decided to walk across the road, was wearing dark clothing, had an eyepatch on so he couldn't see one side of the road well, and was struck by a forklift while the operator was on the phone.
What combination of coincidences is striking? People are careless all the time.
Sounds to me like that there is simply more React code to train the model on.
This sounds a bit like an oxymoron. More diversity will only help the ecosystem IMHO.
They want you to be Jesus
They'll go down on one knee
But they'll want their money back
If you're alive at thirty-three
https://genius.com/U2-hold-me-thrill-me-kiss-me-kill-me-lyri...When I hire grads or juniors onto my team I will focus a lot more on leetcode style problems because a) they don't have much work experience so delving into real-world problems they have solved is typically not useful (exceptions there) and b) leetcode is usually closer to their recent experience which tends to be more academic in nature.
More senior roles typically have very different requirements. I don't need a staff or principal engineer to pass a leetcode test as it typically isn't relevant to that role. I respect their lived experience so I dive into real world problems they have solved, not just software but also people, culture, etc.
> "Hey, the federal portal says we owe $60,000 in penalties for not filing a tax return."
That doesn't sound like they're asking you to pay tax on your $0 income business. It sounds like you need to pay a fine for not filing a tax return.
What's a "normal" fine anyway? The point of having a fine being a large sum of money is to create incentive so you to do the thing they want you doing, which you didn't do.
It reminds me of that movie "The Billion Dollar Code" [1] where some guys claim that Google stole their Google Maps idea. Whereas in reality, it's more likely that due to certain technological advances, different people came up with the same/similar idea of how to store and display maps.