3 ms·
And you almost always can, it's just harder. Things are much easier with too much overhead. It's the same as computing performance. Working with 64K of RAM is h
by pc86 3y ago
And you almost always can, it's just harder. Things are much easier with too much overhead. It's the same as computing performance. Working with 64K of RAM is hard, because you spend so much time on performance. Add 10,000x the overhead and you don't end up with 10,000x more powerful software, you end up with Electron and senior developers who don't know anything about performance testing.
I worked for a company with maybe ~800 people in the IT division (IT in this context means software, DBA, security, help desk, actual IT, everything). Our reporting structure over the entire department, for each group, was something like Manager -> Sr. Manager -> Director -> Sr. Director -> VP -> Sr. VP -> Executive VP -> CIO -> COO -> CEO. We had about a dozen programmers, all one team. 12-14 people reporting to one manager. One manager reporting to one Sr. Manager. Two Sr. Managers reporting to one Director. I am not one of these "managers are worthless" people, I was a manager before and it was a lot of work. But you could have nuked half the management in the entire IT department, and probably 90% of the SVPs and EVPs, and after the dust settled work would have continued at exactly the same pace if not faster.
- Lutger 3y agoThank you, well put. I think that one of the things that make it hard, is not always knowing exactly what overhead can and what can't be eliminated (and how). This might be why its more helpful to just call it all waste (lean) to have a lens of optimization on both types.