News for hackers. Stuff that matters.
Re:Designing Engineering Organizations by systemvoltage on Thursday January 07, 2021 @02:34AM (#25668280)
There is no way one could have picked up what you meant from just saying "Design vs. growth". You realize how general those terms are, right? Something that implies to you may not imply to many others.

Still your language is imprecise. Can you give examples?

> authoritative, non-iterative mega-deployment

Like what? Who designs a team like this? What are some concrete examples?

Re:Designing Engineering Organizations by contingencies on Thursday January 07, 2021 @02:56AM (#25668461)
Apologies if it was unclear to you. It's hard to know who reads all the comments here and impossible to address everyone clearly. Many people on HN are involved in building companies which means they have experience with this sort of thing and probably understood without explanation. Who designs a team like this? Bigco HR departments, the military, the government, emergency response NGOs, etc.
Re:Designing Engineering Organizations by systemvoltage on Thursday January 07, 2021 @04:01AM (#25668862)
That helps and I agree with the examples you cite. I think then we're arguing about mostly bureaucracy - they work great for stable work that needs to happen on a long term basis. Not agile. But, they have their purpose. If militaries and governments were formed like startups ("growth" as we define here), they would fail to function well. Hierarchy is important characteristic of militaries and big companies.

We develop everything from fighter jets to fiscal policy through "designed" organizations.