alt Hacker NewsI've seen too many similar posts on Hacker News. From 2025 to 2026, I've seen countless articles with titles like 'The Prototype Isn't the Product.'
I think these are defensive mechanisms, a kind of lullaby for the Gen AI era.
Why is this discourse endlessly reproduced? In my view, it's because the industry is still searching for a new methodology to control the waterfall of Gen AI code. The cognitive dissonance that results is being resolved by relying on vague personal virtues like 'craftsmanship,' 'fundamentals of computer science,' and 'human judgment.'
If the goal is to review Gen AI code in its entirety, the way an engineer would review a PR, then honestly, I don't see the point of using Gen AI in the first place.
Yes, models lack judgment and only do pattern matching. But lately, I've noticed that in closed systems, Gen AI often produces more logically coherent code than humans do. If that's the case, maybe programmers should shift toward designing closed systems where algebraic data types ensure the program works correctly.
Because using Gen AI means you're committing to codebases that go beyond individual cognitive limits. Once you start using Gen AI code, there's a subtle mismatch with human written code, a fundamental impedance mismatch, like the one between ORM and SQL.
In that sense, I honestly don't know.
The arguments that have been repeated for nearly a year all sound basically the same. But when I look closer, this isn't Gen AI era coding. It's just old era methodology with 'human' swapped out for 'AI.' If the subject changes, the methodology should change too.
Looking at the countless repetitive posts on HN, it shows what HN programmers are afraid of. They're afraid of the destruction of their overall meta-methodology.
All the arguments being made now are about how to become a good senior engineer in the old days.
But is that analogy really appropriate for the volume of code AI is generating?
The amount of code being generated is exploding. The amount of complexity is exploding. Responsibility is becoming unclear. These aren't issues of individual skill. Saying that drivers just need to be more careful when traffic increases is bad road policy. The core is that the roads and signaling systems need to change.
A new subject requires a new methodology.
In that sense, I think the recent post from Jane Street is more like a new solution. Of course, ADT doesn't guarantee that modeling always holds either.
So honestly, I don't know. When I look at HN, it seems like all I see is what social signals people are most anxious about.
Replies
> Looking at the countless repetitive posts on HN, it shows what HN programmers are afraid of. They're afraid of the destruction of their overall meta-methodology.
I think this already happened. What's hard to swallow for us is the countless years spent studying, researching, and investing our time to be the best possible professionals in a very demanding, skill-intensive industry.
Now that software development is starting to be industrialized, I think it's fair to react with fear and uncertainty.
Yep, we are trying to find new strategies and methodologies to still stay relevant, but I think they'll become obsolete soon once the technology reaches a maturity point for full automation and the industrialization of the development process.
What it will look like, I don't know (I have a few guesses), but what I know is that I'll struggle a lot, in the middle of my forties, to reskill myself, especially considering a country of no opportunities like Italy.
> In that sense, I think the recent post from Jane Street is more like a new solution.
Can you please share it?
The lullaby for the Gen AI era exists, but its for CEOs and it is being played in management meetings, it's main theme is about maximizing EBITDA.
The defensive mechanisms kick in because even though more code is generated than ever, we are not observing an equivalent rise in software quality or usefulness, some would perhaps argue it's even opposite.
If gen ai for code was really what it is being sold as it would all be obvious to everyone, we would be seeing better software all around us everywhere and posts such as the one here would just be laughed off, delusional, but they are not.
The code explosion did happen, the value of software this code makes - not yet. Not to say it won't, its just not here right now, and it never happening is still a possible outcome.
> Because using Gen AI means you're committing to codebases that go beyond individual cognitive limits.
Sure, the amount of code generated is exploding but where are these successful production applications that have "[gone] beyond individual cognitive limits"?
It's been some time now. Half a year ago I was concerned with the impact Gen AI might have on this profession. Today I am primarily tired of Gas Towns, Loops and the next fad.
Why do I have to still debug complex problems myself. Why do I have to still do detailed examinations.
Gen AI helps building big software. But the only thing it has truly replaced me in is building small software that in most cases I wouldn't have bothered building in the first place.
I disagree tbh, the prototype is not the product not just because of technical abilities but also because of product expertese in a topic.
If it was otherwise outsourcing companies would've dominated the market for a long time, but it is with the exp from clients and many users that you get to build a great product.
It takes a lot of time to understand what is the pain of the user, in many cases we know what the problem is but we have not time to think of a good solution to it.