who said it had to be production quality? just ship something that works and learn from there.
As long as your users know this and that your app is shipped of something that works and demonstrates a solution you have solved, that is all that matters.
Between browsers and Electron, even those of us who hate this ecosystem are forced to deal with it, and if one does, at least one can do it with slightly more comfort using the newer tooling.
haha. I've been writing code professionally for a very long time. The vibe-coded comment in my original post wasn't really necessary I guess. There's still plenty of design/logic/architecture to be done to ensure robustness.
Many of these still exist today, though is not as large of numbers. Maybe it's the same for software engineers. I still don't recall hearing of bank tellers accelerating the pace of ATMs or Travel Agents encouraging their clients to use Expedia.
> At this point, I’ve even stopped reviewing the exact code changes. I just keep pushing forward until the task is done.
I think this is becoming more normal. I wrote about it [1], but I have the opposite takeaway. This makes programming for me _vastly more_ enjoyable. It might come down to the type of programming you do.
1. Do you build and ship whole products?
2. Do you work mostly on non-user facing code (backend etc)
I'd be interested to know which of these you work on.
I don't disagree it's a naive take, and I would love to read about some examples where this happened.
I haven't seen too many industries be automated away first hand, and I'm sure there are historic examples. I wouldn't expect the lamp lighters to have been championing the rise of electric lamps. Maybe they did though because it meant they could work less hours.
Software developers have been automating away software developers since the beginning of the field. Higher level languages, better+safer languages, improved IDEs. All the ways in which we made developing software easier and more efficient. QA teams investing in automated testing.
One example is probably blacksmiths. Before, each larger village used to have one. Nowadays, this is not the case any more as people order replacement parts for whatever metal piece that broke in your car, house, etc. The metal molding happens in factories instead. But in order you still need to have people who know how to mold metals. The early folks for this profession were blacksmiths. Nowadays you would not call them any more. But it's definitely been "engineers with AI".
Same goes for industrialized food. The huge industrial bakeries still employ people who know how to bake bread, but they can do 1000x more than they could do if they had to knead the dough on their own, separate it, form little pieces of bread, order it nicely on a tray, etc.
Now it's a machine doing most pieces of work, but they still have folks who design new bread products, adjust machines, know what to change in the formula if one particular product from one particular supplier is not available in the quantities needed, etc. A lot of the skills needed aligns enough with the traditional job of a baker that these factories employ actual bakers.
As for software, whenever I use AI tools, I don't really feel that they help me save time much. But it's entirely possible that this is going to change in the future. They are only going to get better. And of course a lot of people say it's useful for them, so it already affects folks. Just because something is not useful to me doesn't mean it's not going to be useful to anybody.
I expect this to become standard for many roles. This is the future. It's hard to say when or how but for anyone who has spent > 6 months, interacting with LLMs on a daily basis, it's clear this is the way.
I've been writing code professionally for 10+ years and I love vibe coding. It's brought back the joy for me in creating things. All the tedious tasks can get farmed out and I can just think about the hard problems and direct the minions to build it.
