3 ms·
the techniques described sound like just as much work, if not more, than just writing the code. the claimed output isn't even that great, it's comparable to the
by dingnuts 1y ago
the techniques described sound like just as much work, if not more, than just writing the code. the claimed output isn't even that great, it's comparable to the speed you would expect a skilled engineer to move at in a startup environment
- CharlesW 1y ago> the techniques described sound like just as much work, if not more, than just writing the code. That's very fair, and I believe that's true for you and for many experienced software developers who are more productive than the average developer. For me, AI-assisted coding is a significant net win.
- dhorthy 1y agoI tend to think about it like vim - you will feel slow and annoyed for the first few weeks, but investing in these skills are massive +EV long term
- criemen 1y agoYet a lot of people never bother to learn vim, and are still outstanding and productive engineers. We're surely not seeing any memos "Reflexive vim usage is now a baseline expectation at [our company]" (context: https://x.com/tobi/status/1909251946235437514 https://x.com/tobi/status/1909251946235437514) The as-of-yet unanswered question is: Is this the same? Or will non-LLM-using engineers be left behind?
- moregrist 1y agoPerhaps if we get the proper thought influencers on board we can look forward to C-suite VI mandates where performance reviews become descriptions of how we’ve boosted our productivity 10x with effective use of VI keyboard agents, the magic of g-prefixed VI technology, VI-power chording, and V-selection powered column intelligence.
- dhorthy 1y agoletting people pick their own editors is a zirp phenomenon
- withinboredom 1y agoHow many skilled engineers can you afford to hire? Vs. Far more mediocre engineers who know how to leverage these tools?