Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I agree this is one of solutions. However, it doesn't seem to scale very well, based on my experience observing companies with 100 to 300 eng teams.

The problem doesn't disappear though, but shifts to other people. Unless you have seen it differently - can you tell me more?



No, I’ve never seen it done well at that size.

The architects didnt understand the code. The developers didnt understand how it would be used, and the managers didnt understand either. The executives understood none of this, nor appreciated what was involved, but focused on what sounded flashy.

A “tiger team” of exceptional people (who understood everything) was formed, tried valiantly, and managed to make progress even possible… But even Superman cannot boil the ocean.

The problem wasn’t even technology or management — just too many people who didn’t understand what the were building or how it would be used. This included both the technical side as well as the “use case” side. They also had no comprehension of how their component interacted with the rest of the system.

I’ve all seen small teams of 10-20 do amazing things because they all understand the goal. They may have different ideas but can quickly arrive at a final design and make it happen.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: