Once your codebase reaches the size needed to solve actual business problems, the quality of the output varies wildly, the complexity of the prompts required to produce useful code increases, and the output code requires significant editing to actually integrate without bugs or errors.
My personal opinion is that for vibe coding to be viable as the complexity of feature requirements or the size of the code base increase, the specificity and complexity of the input prompt will eventually demand more from the engineer than just writing the code, since code is more specific by definition than natural language.
How?, who?, Where? I'm afraid it is too late to find a group of people interested in creating a real network outside of the system. The best that i found was the LoRa communities but are useless for anyone submerged in the Tiktokian distopy.
Maybe my stack is easier or the product is not too complex but if I take my own experience as a truth, my truth, (we) Engineers are going to suffer for a long time.
Everybody will have different experiences but my guess not all developers are working in frontier projects so their jobs will be the first to suffer the change. At least for me this is going to happen.
1. Security > Privacy > Convenience 2. Security > Convenience > Privacy 3. Privacy > Security > Convenience 4. Privacy > Convenience > Security 5. Convenience > Security > Privacy 6. Convenience > Privacy > Security
Dead Comment