While the speed of prototyping and even shipping to production has increased, I have been asking myself at what cost? I see a lot of garbage being shipped. Not because the code quality is bad, because execution has become cheap now. Ideas even though crap, are getting prototyped. Things which look effective on the surface, but has real UX problems in the underneath, are getting prioritised because someone in the room…
The Speed of Prototyping in the Age of AI
41–50 of 119 posts
Re: The Speed of Prototyping in the Age of AI
#42While the speed of prototyping and even shipping to production has increased, I have been asking myself at what cost? I see a lot of garbage being shipped. Not because the code quality is bad, because execution has become cheap now. Ideas even though crap, are getting prototyped. Things which look effective on the surface, but has real UX problems in the underneath, are getting prioritised because someone in the room…
Everyone understands that a wireframe isn’t done yet and it’s easy to change at that phase.
Re: The Speed of Prototyping in the Age of AI
#43While the speed of prototyping and even shipping to production has increased, I have been asking myself at what cost? I see a lot of garbage being shipped. Not because the code quality is bad, because execution has become cheap now. Ideas even though crap, are getting prototyped. Things which look effective on the surface, but has real UX problems in the underneath, are getting prioritised because someone in the room…
Re: The Speed of Prototyping in the Age of AI
#44But is it really any faster than using an already existing code generator/scaffolding tool? How do you know your project isn’t just a regurgitation of another repository? Would it be just as fast to clone some existing project and hack on it? These are the questions everyone seems to be ignoring and saying “only LLMs can make projects quickly” but ignoring everything those LLMs are built on (your llmis probably calli…
Your tone makes me think you already decided that agents aren't worth your time, but I'll give it a try anyways. I work as a DevOps engineer and have been using agents exclusively to code since the beginning of the year. Agents are really nice to quickly craft utilities to speed up planning. For instance I had it create a small cli for me that'll pull my cards from azure DevOps, load them as json, markdown and csv, a…
Reminds me of a conversation I had with Kelsey Hightower where he suggested that using agents to build utilities and software was a smarter way to proceed than using agents to do the work. It is almost like the software artifacts are a cached version of your understanding of the problem and can be used over and over again until the problem (or your understanding of it) changes.
Re: The Speed of Prototyping in the Age of AI
#45Earlier quoted context omitted.
I've started making most of my prototypes single HTML documents with inline CSS and JavaScript, because a single file is a lot easier to store somewhere and share and will probably keep on working forever (browsers are really good at backwards compatibility). I chuck some of them on my public tools.simonwillison.net collection, others in their own GitHub repos with GitHub Pages enabled, and some I just share in a Gis…
The single file is interesting, we’ve been observing something similar too. Do you have a specific prompt that you load in by default to make this work? Are these react files, or just pure HTML/JS/CSS? Aka do you compile it via Esbuild or webpack or something, or are you asking the model to generate something that works out of the box? We’ve been seeing Claude artifacts sometimes come out as JSX or TSX
Re: The Speed of Prototyping in the Age of AI
#46While the speed of prototyping and even shipping to production has increased, I have been asking myself at what cost? I see a lot of garbage being shipped. Not because the code quality is bad, because execution has become cheap now. Ideas even though crap, are getting prototyped. Things which look effective on the surface, but has real UX problems in the underneath, are getting prioritised because someone in the room…
I haven't seen these in at least a decade in the industry!! Everywhere I used to work was always "PM wanted" or similar and the validation was always just QA making sure the thing works/does the bare minimum!!! Customer input was just for bugs.
I hope that with AI speeding up prototyping we can actually go the other way long term, where we go back to ACTUALLY talking to a customer and then quickly prototyping it to see if it is what they wanted. Figuring out what the customer wants remains the hardest part of software engineering, but at least right now its mainly because we just dont talk to the customer.
Re: The Speed of Prototyping in the Age of AI
#47While the speed of prototyping and even shipping to production has increased, I have been asking myself at what cost? I see a lot of garbage being shipped. Not because the code quality is bad, because execution has become cheap now. Ideas even though crap, are getting prototyped. Things which look effective on the surface, but has real UX problems in the underneath, are getting prioritised because someone in the room…
Can you help me understand what the "cost" of other people producing garbage is? Prototypes are generally shop jigs. You'd feel weird gold-plating a stop block.
> the "cost" of other people producing garbage is?
Sure can! It's a well known phenomena, won the researchers a Nobel, and explains a lot of the American economy and "lack of taste". The Market of Lemons[0].Lemon Markets really require one important thing: at time of purchase, the average consumer is unable to differentiate the quality of the product.
Consumers are "rational"[1], so with "all other things being equal"[2], will make their purchases based on price. Therefore, the product that is cheaper but is also _in reality_ lower quality wins. This then pushes out any competition who is trying to differentiate their product through quality. Thus all products in that category decrease in quality and it becomes a race to the bottom, maximizing profits.
I want to stress that this doesn't require that the quality of products are distinguishable by experts, but only by the average consumer. You can probably look around at tech and notice this pretty quickly. The average consumer is not really tech literate[3]. They can't tell the difference. Hell, my parents don't even know the difference between the internet speeds from their ISP, even with the numbers displayed. The numbers mean nothing to them. Do they want 1GBps? 100 MBps? They don't know!
> Prototypes are generally shop jigs
The problem is people are shipping prototypes. We may disagree what is a prototype and what is a shippable product, but that disagreement in itself is worth noting as part of the problem. I mean FFS we in the tech industry love selling things with the promise of future improvements. The last few iPhones shipped with the promise that they were going to get better with AI (did Apple intelligence really pan out? Did it pan out anywhere near what they promised? My Google Pixel phone still can't schedule a haircut for me or book a reservation at a restaurant, despite multiple promises).[0] https://en.wikipedia.org/wiki/The_Market_for_Lemons
[1] Economics uses this term differently than what we use colloquially. Read "consumers make decisions based on the information available to them" not "consumers are geniuses and making perfect decisions"
[2] i.e. the only distinguishing purchase criteria is price
[3] If you think I'm wrong, please go spend a month outside Silicon Valley. Hell, go try a different country, and not in the major metro areas. We're nerds here. Every single person on HN is above average in this respect.
Re: The Speed of Prototyping in the Age of AI
#48While the speed of prototyping and even shipping to production has increased, I have been asking myself at what cost? I see a lot of garbage being shipped. Not because the code quality is bad, because execution has become cheap now. Ideas even though crap, are getting prototyped. Things which look effective on the surface, but has real UX problems in the underneath, are getting prioritised because someone in the room…
The project has tracked your imaginative state, and perhaps the states of your beta testers as they imagine things. It's a power armor suit tailored to specifically you. Nobody else will ever fit it because it's evolving too fast, all to implement your every whim.
I've seen this take 1.0 projects that are intentionally wildly scope-limited and great at that, and balloon until the project is the Everything Machine, doing everything but send email. I guess in the new era, every project expands until it becomes alive and devotes itself to your service… or at least, does its level best to be that for you and your beta team.
These things are not approachable. They're fever dreams, unparsable by outsiders. Discipline is lacking.
Re: The Speed of Prototyping in the Age of AI
#49While the speed of prototyping and even shipping to production has increased, I have been asking myself at what cost? I see a lot of garbage being shipped. Not because the code quality is bad, because execution has become cheap now. Ideas even though crap, are getting prototyped. Things which look effective on the surface, but has real UX problems in the underneath, are getting prioritised because someone in the room…
Re: The Speed of Prototyping in the Age of AI
#50While the speed of prototyping and even shipping to production has increased, I have been asking myself at what cost? I see a lot of garbage being shipped. Not because the code quality is bad, because execution has become cheap now. Ideas even though crap, are getting prototyped. Things which look effective on the surface, but has real UX problems in the underneath, are getting prioritised because someone in the room…
Time saves on stupid shit management thinks works!