What are people doing with prototypes afterward? Do you end up shipping it as is to production? What about at work? Are the prototypes useful in that context?
The Speed of Prototyping in the Age of AI
21–30 of 119 posts
Re: The Speed of Prototyping in the Age of AI
#22I'm truly hopeful that AI will open a new of prototyping. Back in the day, prototyping was how you figured out what to build, you'd very deliberately toss the entire first (or second!) version, and you'd plan to do that. High quality ensued. Usually ;)
Most places I've worked, devs were basically afraid to prototype Either you would get chastised for wasting time with prototypes, or worse, your prototype would end up in production I think the software industry really needs a cultural reset to embrace slower and deliberate development to build quality, but unfortunately AI has us racing recklessly in the wrong direction I am so tired of it. Are there any companies o…
Re: The Speed of Prototyping in the Age of AI
#23I'm truly hopeful that AI will open a new of prototyping. Back in the day, prototyping was how you figured out what to build, you'd very deliberately toss the entire first (or second!) version, and you'd plan to do that. High quality ensued. Usually ;)
Most places I've worked, devs were basically afraid to prototype Either you would get chastised for wasting time with prototypes, or worse, your prototype would end up in production I think the software industry really needs a cultural reset to embrace slower and deliberate development to build quality, but unfortunately AI has us racing recklessly in the wrong direction I am so tired of it. Are there any companies o…
Has this (for me, normal) process really been that arduous in your past jobs? It's a slam dunk to leadership, as we do this to corral time wasted.
Re: The Speed of Prototyping in the Age of AI
#24Earlier quoted context omitted.
Yea cause it's done while you're still reading the docs for your code generator. lol
Code generators are usually one short command. It’s less typing than a prompt would take.
Re: The Speed of Prototyping in the Age of AI
#25Earlier quoted context omitted.
> But is it really any faster than using an already existing code generator/scaffolding tool? Yes, very much so. Our team was fast with those tools and created many of our own before this LLM AI (we used other AIs though to go faster), however it still took weeks to months from idea to launch; the same complexity now takes days, including everything. We already had rigorous processes and those really help now moving…
But “are you really moving at speed after you generate the majority of your application?” is my other point. If you were to start working somewhere with an existing product the changes you would apply are more than likely incremental. What is the advantage of using LLMs to change 1-10 lines of code on average? How do you measure the ROI for that? What did the time savings gain you? A quicker release date? How can you…
Re: The Speed of Prototyping in the Age of AI
#26What are people doing with prototypes afterward? Do you end up shipping it as is to production? What about at work? Are the prototypes useful in that context?
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 Gist (served via gisthost.github.io) or stick in a public S3 bucket so I have a URL for them.
If a prototype is against an existing project sometimes I'll leave it to silently rot in a branch on GitHub.
Re: The Speed of Prototyping in the Age of AI
#27Re: The Speed of Prototyping in the Age of AI
#28What are people doing with prototypes afterward? Do you end up shipping it as is to production? What about at work? Are the prototypes useful in that context?
I think what people ARENT doing is interesting.
Usability isn't even in your list, it is not something most people even think of.
The best thing you can do with a prototype is give it to (potential) users and observe what they do with it. Just because you think that you're clearly communicating the intent of your system does not mean you are.
Re: The Speed of Prototyping in the Age of AI
#29I'm truly hopeful that AI will open a new of prototyping. Back in the day, prototyping was how you figured out what to build, you'd very deliberately toss the entire first (or second!) version, and you'd plan to do that. High quality ensued. Usually ;)
Most places I've worked, devs were basically afraid to prototype Either you would get chastised for wasting time with prototypes, or worse, your prototype would end up in production I think the software industry really needs a cultural reset to embrace slower and deliberate development to build quality, but unfortunately AI has us racing recklessly in the wrong direction I am so tired of it. Are there any companies o…
Quality must come from engineering. If you’re depending on a product manager to ask you that you can improve the quality of the code, you already lost.
So it requires soft skills, proper framing and ability to iterate quickly on quality-related tasks without leaving junk and multiple-versions behind.
But I completely understand push back for “doing improvements developers want to do”: A lot of developers confuse quality with familiarity or even complexity/verbosity. So business people have a reason to be reluctant.
And as an engineering manager I also had to push back several times. The thing that makes money is not the place to learn new skills, for example.
Re: The Speed of Prototyping in the Age of AI
#30While 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…