The future of software development belongs to those who can best articulate what they want to build and how it should work. The ability to just write good code is no longer enough. Developers will have to write good words as well. www.nytimes.com/2026/03/12/m...
Early day is for this new offering from the creator of Kotlin. But the guiding principle is one that I think is going to fundamentally change the way we create software into the future.
Write specs, not code. Need to change the code, change the spec first. 🏆 👏
codespeak.dev
Screenshot of codespeak spec
CodeSpeak is a new "language" from the Kotlin creator, where you write a spec describing the program, and it generates the program.
https://codespeak.dev/
I can see this working for utilities/pure functions, but I have a hard time imagining it for full-stack app.
Important bit from this recent blog post that highlights both why up front spec development is so important in agentic engineering, and also why its so hard to do well.
www.claudecodecamp.com/p/i-m-buildi...
Agentic coding is changing the way software is developed, but it likely won't remove humans from the process. Human expertise is as critical as ever.
adhoc.team/2026/03/09/h...
#AI #ChatGPT #Claude #Gemini #Cursor
New on the SpecOps Blog - Modernizing Government Regulations with AI. spec-ops.ai/blog/posts/m...
Trim down those bloated AGENTS.md files.
mheadd.github.io/agent-slimmer/
#ai #cursor #copilot #agents #claude
If this doesn't get your body moving in some kind of way, get your pulse checked. 🏵️ ❤️ 🎤 🎧
Left side says We Love Open Source. #WeLoveOpenSource. ATO. A community education resource from All Things Open. Right side has Illuminated robotic balls, blacking color with a white stripe and blue lights.
🚀 NEW on We ❤️ Open Source 🚀
AI is making code cheaper to write & easier to understand, shifting the real scarcity to domain knowledge. Mark Headd explores why future collaboration may center on sharing specifications and institutional expertise.
allthingsopen.org/articles/ai-...
#WeLoveOpenSource
This is important.
"CLAUDE.md is not a one-time setup. It’s a living document — but not an ever-growing one."
For government projects with mandated platforms and compliance requirements, those defaults are wrong. That's what AGENTS files are for. 3/2
amplifying.ai/research/cla...
#AI #ChatGPT #Claude #ClaudeCode #LLMs
New data from amplifying.ai shows Claude Code defaults to Railway for deployment, hand-rolls auth from scratch, and never picks AWS/GCP as a primary choice. 2/2
New research has lots of people saying AGENTS.md and CLAUDE.md files aren't worth it. But the research shows that AI coding agents follow these instructions reliably — the problem is most of these files are full of things agents would figure out anyway. 1/2
New research: AI agents given human-curated Skills improved performance 16 points on average. AI Agents that generated their own skills files? Essentially zero benefit. Human expertise still matters most.
spec-ops.ai/blog/posts/s...
#AI #Claude #ChatGPT #LLMs #Codex #Copilot
Me, coming back to work after vacation:
"I'm coming back to this project after being away for about a week and there have been several non-trivial changes committed to the code. Can we do a fresh git pull and discuss the changes that have been made?"
You can learn more about the SpecOps Method and obtain a copy of the book I wrote about it here: spec-ops.ai
I wrote a book about exactly this challenge. The SpecOps method proposes creating that verification artifact for legacy modernization efforts by leveraging AI to generate specifications that domain experts can read and confirm. The trends called out in the Anthropic report verify this approach.
This is why the role of humans doesn't disappear or diminish as AI coding tools gets more capable. AI can handle legacy code base analysis and new code generation. Humans are best suited to handle judgment and verification. Each actor in the process is focused on what it does best.
Domain experts know whether business rules are correct. But they often can't read COBOL, Java or other legacy languages. The verification problem in legacy modernization isn't about technical capability. It's about creating an artifact that human judgment can engage with.
The report makes a prediction of significant relevance to governments: AI will handle COBOL fluently soon. But reading old code isn't the hardest part of legacy modernization. Verification is. AI can describe what code does. It can't verify that system behavior matches policy intent. Only humans can
Anthropic's new report on #AI coding trends shows that engineers use AI in 60% of their work but fully delegate less than 20% of tasks. They call this "the collaboration paradox." The report also predicts AI will handle COBOL fluently soon. Let's dig in. 🧵 resources.anthropic.com/hubfs/2026%2...
"Your coding agent is not malicious. It's amnesiac."
mahdiyusuf.com/why-your-cod...
True story
Thanks, Randy!
Lots of chatter online about what people are seeing with the rapid evolution of #AI coding tools, but I don't see as much conversation about what these changes mean. Here's what I think it means for a sector that I have worked in on and off for my entire life: government. civic.io/2026/02/11/g...
I been saying this: "The SaaSpocalypse - The week AI killed software" www.fintechbrainfood.com/p/the-saaspo...
How government platforms make #AI coding assistants more effective.
adhoc.team/2026/02/05/h...
Cool new feature to add agentic workflows to your GitHub repos. Another banger coming from the group at @githubnext.com and further validation that the future of software development is opening up for people that have developed the ability to communicate clearly. Words > Code github.github.io/gh-aw/
There's a good series on Netflix about the Philly Mob Wars, which features Skinny Joey in his youth. www.netflix.com/title/81763602
