I’m very pro AI, but in terms of the Twitter software engineering discourse I see mostly people doing single person vibe coding, or AI labs …

I’m very pro AI, but in terms of the Twitter software engineering discourse I see mostly people doing single person vibe coding, or AI labs with infinite compute Ralph Wigguming giant codebases. What I don’t see are people doing AI software engineering that has multiple humans contributing to a single code base, each using AI agents, working in a non-commodified domain. In this world I believe the AI hype bois are over their skis in terms of proclaiming the death of software engineering. Maybe in the future but for now in this 6 month gradient of the Singularity the reality on the ground are things like: - Using CI as a harness to ensure agentic coding is correct and validated - Balancing velocity with other concerns (reliability, choosing the right problems, quality, etc) - Making sure the system has an architecture and philosophy so that you don’t end up with spaghetti - Still doing code reviews (though they can be augmented with AI) to ensure you don’t end up with cognitive debt. - Balancing AI costs, and mixing in “human tokens” where appropriate - etc I’d love to hear more from others in this domain! Ie those not just doing solo development projects or AI labs with infinite compute

Related

• What Software Engineering Looks Like to AI Agents? -- An Empirical Study of AI-Only Technical Discourse on MoltBook
• AI-native software engineering teams operate very differently than traditional teams. The obvious difference is that AI-native teams use cod…
• Agentic Agile-V: From Vibe Coding to Verified Engineering in Software and Hardware Development

Source: Jeremy Howard (X) | 2026-10-15