5 ms·
When it comes to number of engineers, always keep in mind that it costs more engineers to maintain (and understand) software than the initial development push.
by Cthulhu_ 5d ago
When it comes to number of engineers, always keep in mind that it costs more engineers to maintain (and understand) software than the initial development push.
- bonesss 5d agoI’d add on to that lifecycle demands: a development project with no users has a tight cheap feedback loop with high quality bug reports with relatively obvious bug sources, once issues start working through layers of QA and customers the per-issue costs raise by several factors (50x to 200x are numbers I’ve seen from research, YMMV). I would feel very confident slapping something onto Chrome ‘back then’ with only internal users. Today, with millions of users and CEO-level attention to screwups, I’d use a lot more time per issue. It’s a fundamentally different risk/reward/confidence situation.