4 ms·

I've been a software engineer for over 30 years and I have to say using AI and vibe coding has made me a 10x programmer. It's all about prompting and debugging,

I've been a software engineer for over 30 years and I have to say using AI and vibe coding has made me a 10x programmer. It's all about prompting and debugging, knowing how to fix issues is still a necessary skill and how to build/architect things from a prompt perspective. I've released 8 npm modules in the past 2 weeks alone just for some silly stuff I was using.

brvier 1y ago
Maybe there was no need for 8 more npm modules ... is_odd ...
- mmcromp 1y ago
  Finally the treadmill of endlessly reinventing JavaScript frameworks and libraries is available for us Joe Schmoes too.
- maksimur 1y ago
  How do you know? I'd have to see those modules first to have an opinion.
  - anonzzzies 1y ago
    They said 'maybe'. I'm gonna say they are right, because there is no need for 99%+ of npm modules (and indeed, by far most are not used by anyone except the org author). Especially with AI, most npms are trivially generated faster than you can find and install them and usually less influenced/opinionated by the usually terrible star vying programmer that uploaded it in the first place. If AI trivially generates your npm (so you can make 4 per week next to whatever you were doing), why would I need it instead of having AI trivially generating a specific (without the features I don't need) version for what I am doing at the moment?
  - cranberryturkey 1y ago
    https://www.npmjs.com/org/profullstack https://www.npmjs.com/org/profullstack
- antifa 1y ago
  Counter-point: there's plenty of need for modern-es6/typescript-first/promise-aware/tree-shakable npm libs.
pjmlp 1y ago
Coding since 1986, and what I see is the dream of CASE tooling finally coming true, eventually as AI matures, assuming we aren't getting through yet another AI cycle that will stabilize until the next wave, I see ourselves writing requirements documents in a UML kind of way (in spirit, doesn't need to be boxes and arrows) for AI minions to actually do the work with one third of current team sizes. The other two thirds can search for something else, just like the factory workers when robots took over most factory roles. The remaining one third, are the folks doing the jobs robots can't yet do, or doing their maintenance. Software factories are no different from physical ones, in this regard, a few iluminaries will be able to profit from AI, everyone else needs to re-train themselves.
- viraptor 1y ago
  > I see ourselves writing requirements documents in a UML kind of way That's what I've had most success with. Chat to create a requirements/spec document. Then convert it into a work plan. Then feed the stages into an agent for implementation. Works great and the extra "let me know which areas should be more refined" does wonders.
JackSlateur 1y ago
[flagged]
- ChromaticPanic 1y ago
  I bet it can code an entire app faster than you can. If you already know what you want, AI is a huge productivity boost.
  - JackSlateur 1y ago
    Writing code takes me little to no time Thinking about what I want is what takes me most of my time I am an engineer and, as such, are paid to think, not "just" use my hands

brvier 1y ago

Maybe there was no need for 8 more npm modules ... is_odd ...

mmcromp 1y ago
Finally the treadmill of endlessly reinventing JavaScript frameworks and libraries is available for us Joe Schmoes too.
maksimur 1y ago
How do you know? I'd have to see those modules first to have an opinion.
- anonzzzies 1y ago
  They said 'maybe'. I'm gonna say they are right, because there is no need for 99%+ of npm modules (and indeed, by far most are not used by anyone except the org author). Especially with AI, most npms are trivially generated faster than you can find and install them and usually less influenced/opinionated by the usually terrible star vying programmer that uploaded it in the first place. If AI trivially generates your npm (so you can make 4 per week next to whatever you were doing), why would I need it instead of having AI trivially generating a specific (without the features I don't need) version for what I am doing at the moment?
- cranberryturkey 1y ago
  https://www.npmjs.com/org/profullstack https://www.npmjs.com/org/profullstack
antifa 1y ago
Counter-point: there's plenty of need for modern-es6/typescript-first/promise-aware/tree-shakable npm libs.

pjmlp 1y ago

Coding since 1986, and what I see is the dream of CASE tooling finally coming true, eventually as AI matures, assuming we aren't getting through yet another AI cycle that will stabilize until the next wave, I see ourselves writing requirements documents in a UML kind of way (in spirit, doesn't need to be boxes and arrows) for AI minions to actually do the work with one third of current team sizes. The other two thirds can search for something else, just like the factory workers when robots took over most factory roles. The remaining one third, are the folks doing the jobs robots can't yet do, or doing their maintenance. Software factories are no different from physical ones, in this regard, a few iluminaries will be able to profit from AI, everyone else needs to re-train themselves.

viraptor 1y ago
> I see ourselves writing requirements documents in a UML kind of way That's what I've had most success with. Chat to create a requirements/spec document. Then convert it into a work plan. Then feed the stages into an agent for implementation. Works great and the extra "let me know which areas should be more refined" does wonders.

JackSlateur 1y ago

[flagged]

ChromaticPanic 1y ago
I bet it can code an entire app faster than you can. If you already know what you want, AI is a huge productivity boost.
- JackSlateur 1y ago
  Writing code takes me little to no time Thinking about what I want is what takes me most of my time I am an engineer and, as such, are paid to think, not "just" use my hands