logoalt Hacker News

JoelMcCrackentoday at 1:35 PM3 repliesview on HN

This is one of the things I keep thinking about. At the very least, these tools make prototyping and idea vetting remarkably cheaper.

Then we go back to the old “the prototype works; I’m the boss and I’m telling you to deploy it to production”


Replies

saalweachtertoday at 3:42 PM

There's like three groups of developers you need:

The prototypers, who move fast and break things, who throw together shiny first versions that look great and work some of the time;

The architects, who take the prototypes and take the time to build it correctly;

And the gardeners, who maintain the built system for the next 10-30 years, fixing bugs, making incremental improvements to speed or resource usage, and updating dependencies so that it continues to function on modern machines.

The crazy thing is that there are a ton of developers with different tastes who would love to fill each of the roles, but not many companies that are able to manage all three types without pushing everyone into one bucket.

show 1 reply
rzmmmtoday at 1:41 PM

Prototyping is widely underappreciated. People think it's waste to throw away stuff but it's more costly to build upon shoddy foundations

show 5 replies
SkyBelowtoday at 3:20 PM

One of the major concerns with prototyping, at least in my experience and based on the general vibe I've felt from others over the years, is that clients will generally do some variation of "You have a working prototype? So how many days until it is prod ready? No more than a few weeks, right?" and that will be their expectation. AI makes prototyping easier, but makes this specific drawback much worse. Expectations are going to be misaligned, leading to many disappointments, and likely some number of developers taking undue negative outcomes. I'm not even sure if it will normalize to reasonable expectations, given that this tension never seemed resolved even before AI was in the mix.