> with the latest bizarre web stacks, frameworks for everything, node for this, npm for that, Angular, React, Vue, whatever - as if solving business problems just became too boring for software developers, so we decided to spend our cycles on the new hotness at every turn
I kinda feel the same way when I visit Home Depot once a year
oxidation is a chemical process where a substance loses electrons, often by reacting with oxygen, causing it to change. What does it have to do with JavaScript?
A huge part of implementation is how it’s done. A lot of companies made mp3 players, Apple made the iPod. Their implementation was different. It was done with more care and thought. The idea was cheap, 1,000 songs in your pocket. An implementation that connected with people and brought it to the mainstream was hard.
Someone quickly vibe coding something might fulfill the requirements of an idea. However, their implementation will likely be poor and lack the care needed to connect with people on a way that makes them want to use it.
I think understanding this has always been the key to standing out. That doesn’t change in the world of LLM, it becomes more important than ever.
Sometimes that's because they're making it worthwhile, by connecting the thing with those who will benefit from it and explaining how to use it, which is as valuable as doing the thing.
I.e. by making sure that they're doing the right thing.
Good taste. I just vibe coded some garbage in an hour. But it is so bad I can't see how to get to good code from here and so I'll spend the rest of the week doing it by hand.
now to be fair this is my first attepmt at vibe coding and so I might not know how to prompt the ai
Depends on the tool, but the first thing to do is to use a plan mode where the AI will ask you follow up question to precise the project. This gives a much, much better result than just have the AI start to work with a few lines of prompt.
That basically turns your bad prompt into a good prompt, then execute on it.
The challenge with AI doing architecture is assembling all the relevant stakeholder context, then having the wisdom to weigh it to produce an optimal solution. The context issue is solvable, but the wisdom part is complex and nuanced, it requires a deep understanding of power structures and organizational dynamics, as well as some understanding of where the problem domain is evolving over time.
Nothing. Most software "architecture" is simply repeating the same patterns, just like writing code, just at a slightly higher level of abstraction. There's a slight moat if you are good at the business domain, and can serve as a bridge, but honestly, AI is getting pretty good at that as well.
In some cases, that’s true, but sometimes you need to update cutting rules because of law changes, or you saw different way of cutting for example. There are cases where this is not one time investment. What I agree with that cutting-it-yourself became significantly cheaper
I kinda feel the same way when I visit Home Depot once a year
reply