3 ms·
I think you don't understand the reason for middle-management. Let me paint you a picture where if you'd be CTO (or any other top-management) you'd be greatful
by romanovcode 7y ago
I think you don't understand the reason for middle-management. Let me paint you a picture where if you'd be CTO (or any other top-management) you'd be greatful for middle-management.
Imagine you are CTO of a pretty successful eCommerce company.
What you need to oversee as a CTO:
- iPhone and Android application
- Front-End Website application
- Back-End Website application
- SAP (Or something similar) integrations for billing and documenting
- BI infrastructure and reporting via tool like Tablou/Salesforce or similar integration with replica read-only DB
- DevOps (AWS, Azure, GC, or similar) maintanence and R&D
- Bonus: A lot of meetings with other top-management regarding company stuff (structure, plans, vision, etc..)
Now, how many people (Developers, QA, DevOps, BI, ...) do you think work under you - at minimum 30 (bare in mind I'm talking about successful stable company, not a 2-man garage startup).
Do you really think one guy will want to deal with all the 1-1 bullshit, day-to-day operations, everyoen asking raises, people leaveing, people coming (hiring)? It is literally impossible.
- goatinaboat 7y agoI think you don't understand the reason for middle-management. I think I do, I’ve worked at places with more middle-managers than engineers! They mainly held meetings with each other all day as us engineers got on with the real work, self-organised when necessary. It wasn’t too bad since we were mostly left alone but we still resented their generous salaries being paid off our labour.