Hacker News Reader

Comment by thinkindie | Hacker News Reader

I’ve found myself raising the bar every day with my team in terms of my expectations of what their deliverables should be. I gave them enough time to adjust but I observed that the average engineer believe they can do the same with less effort while they should rather think about delivering more and of higher quality, and taking the extra time available to connect the dots.

I believe this is going to be a huge filter moving forward.

View on HN

My feeling is that this will be near apocalyptic for the devs who found their joy in the finer grained aspects of implementation, like crafting individual “perfect” blocks of CSS and component code. Many developers enjoy the practice of writing software, as something distanced from actually delivering a product.

Retooling thought to be delivery-oriented is very difficult.

I used to be among those that appreciate a well structured codebase. I used to spend a lot of time thinking about that and making sure each file was as clean as the timeline allowed, with regular tech debt cleanup when you had to cut some corners or you accumulate some cruft.

And I’m still are, with the difference that I still enforce this at agent and code review level because I believe a solid foundation is important for long term success, especially now that it can be cheaper to achieve if you choose to

Yeah this is the difference between personal projects or being a team lead with serious influence, versus being a typical developer employee.

The typical employee is not given the leeway to spend time building up the infrastructure needed to enforce good output from LLMs. Previously understanding the codebase was just part of doing the work you were assigned, but now it requires that side effort of creating infrastructure. And unfortunately a lot of teams won't approve letting developers spend their time on that infrastructure, they just want the deliverables they're asking for.

Reply on news.ycombinator.com