Tag: codegeneration
-
Design systems are much more valuable now
Design teams have spent years trying to get people to actually read their design system documentation. Agents read it every single time. Related, check out this discussion of how the design team at Tanzu works with AI. Plenty of design system talk there. 🔗 Design Systems for AI Agents
-
What a Claude Code Max plan pays for shifts around a lot
It’s hard to tell how many tokens you’re getting, and it changes on you for mysterious reasons: Before the change, somewhere between 30% and 67% of requests included a thinking block, and output averaged 250 to 960 tokens per request. After it, 95% to 100% of requests included thinking, and output rose to 2,500 to…
-
Enterprise AI ROI at Bank of America: developers, optimizing normie workflows, double spending
Thus far, the most measurable AI returns are found within technology units, such as with software development and coding, BofA’s DeMare said. Across most industries, AI is boosting coding productivity about 15% to 20%, he said, and that’s the gain BofA is seeing as its 20,000 software developers use coding agents to optimize the development…
-
Enterprise architect as context engineer
Sadly: the major issue with EA has always been cost of delay. The big problem is not that architecture tells development teams to change direction — development teams do this routinely. The problem is that architecture historically has taken too long. We have validated that assertion repeatedly with many chief EA pros. Now with agentic…
-
programmers are managers now
The central task becomes describing an objective precisely enough for the system to divide it, establishing the rules under which the agents operate, and judging whether their collective output belongs in the codebase. 🔗 Claude Code Turns Software Development Into a Management Job
-
Inside OpenAI’s agentic software factory
We’re talking about roughly a 10x increase in load on some systems. At most companies, that kind of growth might happen over two or three years. At OpenAI, we see it in about six months. 🔗 Inside OpenAI’s agentic software factory
-
The Interfaces Are Arriving
For an engineering organization, the immediate consequence is reuse. An MCP server for an internal ticketing system can serve every compatible IDE, chat application, and agent. Models and hosts will keep changing; the interface contract, server implementation, schemas, and authorization wiring can endure. The integration becomes an asset shared across applications. Language servers followed the…
-
Slop Is Really Good Now. Slop Is Where We Start Now
When the baseline is good enough, being intentional about which aspects need to be great is the whole job. The floor is rising; our job is to spot how to raise it further. Design here is knowing how to articulate and leverage craft. That’s a real opportunity for designers to be articulate, and to work…
-
Your coding agent got the onboarding your developers never did
before you tune the tone of your next prompt, look at the AGENTS.md file your team wrote this quarter, and ask why the onboarding doc for your newest hire still doesn’t exist. 🔗 Your coding agent got the onboarding your developers never did
-
the programmer’s boss is not competition
Perhaps more intriguing is the makeup of that adoption, and how it appears to be blurring roles. Senior leaders are doing more of the hands-on IC work, adopting AI aggressively to help them do it, and non-engineers are committing code. The suggestion that everyone in an organization is becoming a “builder” seems to be directionally…
-
We need more than a metaphor: here are testable diagnostics for comprehension debt
“Comprehension debt” In Sonar’s State of Code Developer survey from January, 96% of developers said they don’t fully trust that AI-generated code is correct, but only 48% of them check it before committing. This stat is old now relative to the pace of AI adoption, but based on my continual interviews and conversations with development…
-
There is no organizational-level ROI for AI, just IC ROI
The best theory of elusive enterprise AI ROI yet: AI makes workers more productive, not organization: “How can you reconcile the failure of AI in the enterprise with the individual claims of skilled technologists who insist that AI is helping them do great work?” The answer is that these AI users are “centaurs” — experienced…
-
Reorganizing the dev teams at Visa to take advantage of AI
When you speed up the SDLC process, you should collapse silo’ed teams into one team to prevent human bottlenecks based on handoffs. Here’s that at Visa: As a result of the unlocks we can realize with this new tooling, we are re-forming our product development teams that used to be 10 or more into smaller…
-
Relative to your interests, Wednesday
After reading many of the below and other links in elusive enterprise AI ROI, I wrote this theory on how to be successful with enterprise AI projects. It’s the usual “culture” cliché, but hopefully a little more practical than usual. Are PMs becoming irrelevant? – Once you remove the need for a bunch of “paperwork,”…
-
Relative to your interests, Tuesday
I have been on vacation for a little while, in Finland for the third time. Finland feels different than the other parts of Europe I have been to. Perhaps it’s because I spent my time there in rural Finland. But it also feels like most of Finland is rural. In that way, it feels a…
-
short feedback loops always works
Using short feedback loops to experiment and direct software development is always a good idea, especially with AI: What survives from Agile is the feedback logic. Short cycles still matter. Thin vertical slices still matter. Customer or stakeholder review still matters. Working software is still better than progress theater because agents can generate a lot…
You must be logged in to post a comment.