3 ms·

I'm not surprised. There is a complete meltdown in the Cursor subreddit because some update made code generation worse in "agent" mode. It seems that there are

I'm not surprised. There is a complete meltdown in the Cursor subreddit because some update made code generation worse in "agent" mode. It seems that there are many people completely relying on prompting without reviewing any code at all.

bluefirebrand 2y ago
Code Review is vital, but probably the least enjoyed part of any software job I cannot fathom why anyone who writes and maintain code would embrace AI tools that essentially shift their job to be more code review and less coding Especially given the quality of AI generated code is all over the place People say "it's like a good junior" but I disagree wholeheartedly. Good juniors eventually stop making the same mistakes
- yimby2001 2y ago
  I mean it has improved greatly about as fast as an actual junior programmer…
  - bluefirebrand 2y ago
    Any given model never improves ever The overall technology may. A new model may be better than an old model But a model is fixed That's the difference
    - yCombLinks 2y ago
      Worthless argument, no one cares if chatGPT 3 was a good code in their day job.
      - bluefirebrand 2y ago
        This is relevant when companies are paying for access to specific models and are restricting their employees access to other models Your model isn't improving Get ready to jump on the "pay us more for better models" treadmill or get left behind
        yimby2001 2y ago
        Well, I don’t believe it pay more for something better when this ever happened?! unprecedented?!
        terrydavissim 2y ago
        Haven’t most models dropped in price per token in the past few years? Despite being far better? Even if we say they haven’t, humans also get paid more as their skills/ability improve. If this hasn’t happened for you I’ve got bad news (or your boss is a dick)
    - terrydavissim 2y ago
      Aside from this pedantry being useless, GPT-4o as 1 of many examples, has had several updates including both its knowledge cutoff but also meaningful improvements (usually) in other benchmarks, without any official renaming etc.
_fat_santa 2y ago
It's honestly kind of entertaining to read the posts on there where folks are talking about Cursor messing up their codebase and every comment is telling them to learn coding basics and start using git. It will be really interesting how "vibe coding" will cause the field to evolve. My gut says that right now it's just non-technical folks that do it and programmer that do it for fun. But IMO this will creep into the industry and will eventually result in an even bigger junior/senior gap.
- threecheese 2y ago
  “Will creep” is the wrong tense: we’re doing it now. At $bigco we’ve rolled out GH Copilot and an AWS sandbox with Sonnet3.7 et al to the whole engineering org (which is big). We already have a 2025 KPI around copilot use by devs, human review required for generated code commits (by policy) for now. Just this week we started rolling out automated copilot PR reviews for human code, it’s already packaged in github action runners. PMs are already using genai for fleshing out epics and features and the architecture org has a demo next week of a genai diagramming tool. If this tech saves four cents net/net it doesn’t matter how many engineers go away. It’s short sighted for sure, nobody cares if we don’t have junior devs in five years as long as we decrease headcount. Senior leadership was on the fence a bit until they came back from re:invent, AWS must have pushed hard in those closed door meetings. They came home positively GIDDY

bluefirebrand 2y ago

Code Review is vital, but probably the least enjoyed part of any software job I cannot fathom why anyone who writes and maintain code would embrace AI tools that essentially shift their job to be more code review and less coding Especially given the quality of AI generated code is all over the place People say "it's like a good junior" but I disagree wholeheartedly. Good juniors eventually stop making the same mistakes

yimby2001 2y ago
I mean it has improved greatly about as fast as an actual junior programmer…
- bluefirebrand 2y ago
  Any given model never improves ever The overall technology may. A new model may be better than an old model But a model is fixed That's the difference
  - yCombLinks 2y ago
    Worthless argument, no one cares if chatGPT 3 was a good code in their day job.
    - bluefirebrand 2y ago
      This is relevant when companies are paying for access to specific models and are restricting their employees access to other models Your model isn't improving Get ready to jump on the "pay us more for better models" treadmill or get left behind
      - yimby2001 2y ago
        Well, I don’t believe it pay more for something better when this ever happened?! unprecedented?!
      - terrydavissim 2y ago
        Haven’t most models dropped in price per token in the past few years? Despite being far better? Even if we say they haven’t, humans also get paid more as their skills/ability improve. If this hasn’t happened for you I’ve got bad news (or your boss is a dick)
  - terrydavissim 2y ago
    Aside from this pedantry being useless, GPT-4o as 1 of many examples, has had several updates including both its knowledge cutoff but also meaningful improvements (usually) in other benchmarks, without any official renaming etc.

_fat_santa 2y ago

It's honestly kind of entertaining to read the posts on there where folks are talking about Cursor messing up their codebase and every comment is telling them to learn coding basics and start using git. It will be really interesting how "vibe coding" will cause the field to evolve. My gut says that right now it's just non-technical folks that do it and programmer that do it for fun. But IMO this will creep into the industry and will eventually result in an even bigger junior/senior gap.

threecheese 2y ago
“Will creep” is the wrong tense: we’re doing it now. At $bigco we’ve rolled out GH Copilot and an AWS sandbox with Sonnet3.7 et al to the whole engineering org (which is big). We already have a 2025 KPI around copilot use by devs, human review required for generated code commits (by policy) for now. Just this week we started rolling out automated copilot PR reviews for human code, it’s already packaged in github action runners. PMs are already using genai for fleshing out epics and features and the architecture org has a demo next week of a genai diagramming tool. If this tech saves four cents net/net it doesn’t matter how many engineers go away. It’s short sighted for sure, nobody cares if we don’t have junior devs in five years as long as we decrease headcount. Senior leadership was on the fence a bit until they came back from re:invent, AWS must have pushed hard in those closed door meetings. They came home positively GIDDY