Most software engineers are facing an identity crisis bordering on depression.
As CTOs aggressively evangelize tokenmaxxing, a class divide ensues.
The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working.
The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy.
This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.
I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem.
As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)!
I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work.
It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results?
88ms => 1.5ms
150K allocs => ~500 allocs
Incredible right? Nope.
My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path.
This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput.
The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity.
Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.
Why is no one talking about this?
@nvidia is offering around 80 AI models via hosted APIs absolutely for free.
You get access to MiniMax M2.7, GLM 5.1, Kimi 2.5, DeepSeek 3.2, GPT-OSS-120B, Sarvam-M etc.
This plugs straight into OpenClaude, OpenCode, Zed IDE, Hermes agent and even with Cursor IDE.
Setup:
– Grab API key: https://t.co/Wfdclm0hY2
– base_url = "https://t.co/VOGC10LmGP"
– api_key = "$NVIDIA_API_KEY"
– select model (e.g. minimaxai/minimax-m2.7)
If you’re building or experimenting, this is basically free inference.
Lock in and start building today anon.
Thank me later.
Yes, these agents are absolutely horrible at writing decent-quality code.
But any time you say that out loud, there's a swarm of AI-apologists who've never built anything that scream at you, "skill issue!"
You might not care about the code, and that's alright, but you can't gaslight anyone who cares about good code.
Tired of 10 terminals just to run your project? Launchpad starts ALL your services with one button in VS Code / Cursor. Procfile-style → single terminal → one Ctrl+C to rule them all. 👉 https://t.co/Y31JyQH8tl #VSCode#Productivity#Nodejs#RubyOnRails#Cursor
I get why closed-source AI labs feel threatened by open-source AI labs.
But let’s be honest. Today’s AI takeoff was built on open research and open-source software.
Without PyTorch, TensorFlow, JAX, the Transformer paper, and all the open-source codebases on GitHub used as free training data, these closed-source companies wouldn’t even exist.
Tired of 10 terminals just to run your project? Launchpad starts ALL your services with one button in VS Code / Cursor. Procfile-style → single terminal → one Ctrl+C to rule them all. 👉 https://t.co/Y31JyQH8tl #VSCode#Productivity#Nodejs#RubyOnRails#Cursor
🤖 Grok Everywhere: AI assistant in your browser side panel
• Chat about any webpage
• Screenshot analysis
• Real-time streaming responses
• Tab-specific conversations
Free on Chrome Web Store! 🔗 https://t.co/WL3Mb4ISAY
#AI#ChromeExtension#Grok
�� Problem: Switching between browser tabs and AI chat is annoying
✅ Solution: Grok Everywhere - AI assistant in your browser side panel!
🔗 https://t.co/WL3Mb4Jqqw
#Productivity#AI#ChromeExtension#Grok