Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

i tend to share your view. but then your comment describes a lot of previous cycles of enterprise software selling. it’s just that this time is reaching a little uncomfortably into the builder’s /developer’s traditional areas of influence/control/workflow. how devs feel now is probably how others (ex csr, qa, sre) felt in the past when their managers pushed whatever tooling/practice was becoming popular or sine qua non in previous “waves”.


This has been happening to developers for years.

25 years ago it was object oriented programming.


or agile and scrums.


Our new CTO decided to move to agile and scrum, in an effort to reduce efficiency and morale.

He doesn't even take responsibility for it, but claims the board told him to do that.


is it supposedly to “improve velocity “?


Is it supposed to add 30% overhead?


unless you’re exceptionally lucky!


The difference is that with OO there was at least hope that a well trained programmer could make it work. Nowadays, any person who understands how AI knows that's near impossible.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: