2 ms·
You think "code reviews, tests, CI, and issue tracking" are just "things that someone said are cool to do"? Your argument is genuinely that these do not broadly
by seattle_spring 3y ago
You think "code reviews, tests, CI, and issue tracking" are just "things that someone said are cool to do"? Your argument is genuinely that these do not broadly fall under the umbrella of "good software engineering basics"?
- ipaddr 3y agoThose items add overhead, are hard to add to some existing systems after the fact. Issue tracking is very important if you have someone creating the issues. A lot is going wrong here that some of the elements you suggest could help but by themselves probably not.
- jesterson 3y agoThe problem here is classical - for someone with a hammer every issue looks like a nail. Are those cool things may be beneficial for some abstract project. It certainly may be. Will those things be good for any project? Certainly not. How do you think software development existed before all those things were invented? Code was better, systems were more reliable. And there were no managers solving “issues “ with buzzwords