131–136 of 136 posts
One think I think is strange about the m programming world we live in now is the mythologization of pre llm code. As if people weren’t copying code from stack overflow, auto completing their way through APIs using intellisense, intellicode, tab nine, or checking in code there didn’t properly test or understand
Earlier quoted context omitted.
You absolutely can deny long term productivity gains. Pre AI it took 100 engineers 5 years to get into a legacy code situation. Once you’re in a legacy code situation it’s very hard to add new features and your code is full of bugs. Fortunately most old companies with legacy code are making loads of money so they can pay the increased development costs to add features to their legacy code. Now with AI five engineers…
Why five? What do the other four do?
Earlier quoted context omitted.
You should really look at studies on how happy employees are much more productive than unhappy ones. And the trend continues way above the bare minimum of not being miserable.
not sure why you've equated the team's happiness is less important than the software to make the team unhappy . that's an incredibly binary perspective. there's usually more than two priorities. and i agree with you that a team's wellbeing is important. it should be up there in priorities. i'm just pointing out that a team that accepts being happy, focussing on the software as more important than their own happiness…
In my startup, I am currently in consideration for doing this exact thing. The interesting part is it's not really the AI that's causing the issue. It's the ease of my developer to make a mess, either with messy code or feature bloat. After figuring out the exact product we need with some very quick development cycles with AI, we now have some problems that I can't keep under control because of AI. So, currently unde…
I think devs themselves won't want to work for a company that doesn't let you use Codex et al.