How do you organize projects in ways where adding more devs improves productvity?
Posted by sext-scientist@reddit | ExperiencedDevs | View on Reddit | 2 comments
Lets say you're building a greenfield project, you can organize it however you want. What sort of structure would be best if you want to throw 42 devs in say 7 teams.
Obviously the correct choice is a monolithic C++ project using randomized rotating templates, zero documentation, and randomized standards. Every day each team picks a ticket from a hat. The hat is a wizard hat. Seriously though wondering what is practical here, especially in terms say a CTO being able to plan 1-3 quarters in advance with few changes, minimalistic systems. Book recommendations are welcome.
Stubbby@reddit
Google "Bezos API Mandate".
A few very simple rules to live by that enabled standardizing and scaling products into the organized, simple and user friendly ecosystem called AWS \s.
There are a few elements that were critical - acknowledging extra effort (often unnecessary) and firing everyone who wasn't on board as you can't make it work in steps or as a portion.
So yeah, that's a good data point to have for reference.
ExperiencedDevs-ModTeam@reddit
Rule 9: No Low Effort Posts, Excessive Venting, or Bragging.
Using this subreddit to crowd source answers to something that isn't really contributing to the spirit of this subreddit is forbidden at moderator's discretion. This includes posts that are mostly focused around venting or bragging; both of these types of posts are difficult to moderate and don't contribute much to the subreddit.