| ▲ | bigfishrunning 3 hours ago |
| A rewrite with another, more subtle mistake. That you must spend energy discovering and diagnosing. |
|
| ▲ | dawnerd an hour ago | parent | next [-] |
| And potentially trick you into going down a rabbit hole as you try to steer it when it would have been faster to edit the code yourself. The best use is editing code with it instead of purely relying on prompting. Also new contexts for different changes make a huge difference. Seems a lot of devs get stuck in the single context chat stream and it starts to break down as context gets fuzzy. |
| |
| ▲ | catlifeonmars 26 minutes ago | parent [-] | | > The best use is editing code with it instead of purely relying on prompting. What does this look like in practice? |
|
|
| ▲ | fluidcruft 3 hours ago | parent | prev | next [-] |
| How is that different from working with a n00b except that it only took 30sec to get to the next bug rather than a week? |
| |
| ▲ | bigfishrunning 3 hours ago | parent [-] | | The junior engineer will grow into a senior engineer | | |
| ▲ | bayarearefugee 2 hours ago | parent | next [-] | | > The junior engineer will grow into a senior engineer And then quit after accepting a new job that pays them their modified value, because tech companies are particularly bad at proactive retention. | | |
| ▲ | Kirth 12 minutes ago | parent [-] | | .. and because the job and environment weren't that pleasant or rewarding to offset that delta in income offered elsewhere at an equally drab employer |
| |
| ▲ | fluidcruft 2 hours ago | parent | prev [-] | | And then they get their own junior engineers and you get fresh new junior engineers. |
|
|
|
| ▲ | square_usual 3 hours ago | parent | prev [-] |
| > another, more subtle mistake. That you must spend energy discovering and diagnosing But this is literally what senior engineers do most of the time? Have juniors write code with direction and review that it isn't buggy? |
| |
| ▲ | bigfishrunning 2 hours ago | parent [-] | | Except that most of the code seniors review was written with intention, not just the most statistically most likely response to a given query. As a senior engineer, the kinds of mistakes that AI makes are much more bizarre then the mistakes junior engineers make | | |
| ▲ | square_usual 2 hours ago | parent | next [-] | | I've worked with many interns and juniors in my life and they've made very bizarre mistakes and had subtle bugs, so the difference in the kinds hasn't made much of a difference in the work I've had to do to review. Whether or not there was intention behind it didn't make a difference. | |
| ▲ | sokoloff an hour ago | parent | prev [-] | | I’ve definitely seen absolutely bizarre creations from junior devs decades ago (so, well before modern AI). I can also think back to some cringey code I wrote by hand when I was a junior as well. I mentor high-school students and watch them live write code that takes a completely bizarre path. It might technically be intentional, but that doesn’t mean it’s good or useful. |
|
|