Scaling Engineering Teams via Writing Things Down and Sharing - aka RFCs


44 bookmarks. First posted by bigiain 9 weeks ago.


Using an RFC-like model to avoid the lack of visibility on others building or having built the same things as other teams, and the tech and architecture debt accumulated due to different teams building things very differently.
agile  culture  engineering  management  programming  business 
4 days ago by garrettc
iterate on a lightweight, RFC-like process so it works well for your org or company.
agile  bestpractice  read 
7 days ago by stephan.poetschner
What if I said there is a way to tackle both these issues pretty well, using a few simple steps? A word of warning, one of the steps will sound a little crazy. Here they are.
10 days ago by itst
I have recently been talking at small and mid-size companies, sharing engineering best practices I see us use at Uber, which I would recommend any tech company…
from instapaper
10 days ago by muhh
I have recently been talking at small and mid-size companies, sharing engineering best practices I see us use at Uber, which I would recommend any tech company adopt as they are growing. The one topic that gets both the most raised eyebrows, as well the most "aha!" moments is the one on how the planning process for engineering has worked since the early years of Uber.
programming 
8 weeks ago by GameGamer43
I have recently been talking at small and mid-size companies, sharing engineering best practices I see us use at Uber, which I would recommend any tech company adopt as they are growing.
8 weeks ago by AnthonyBaker
Perhaps the key to scaling isn’t as complicated as we make it — just write things down!
_brief 
8 weeks ago by thingles
Scaling Engineering Teams via Writing Things Down and Sharing – aka RFCs
from twitter
9 weeks ago by jackysee
```Key Takeaways

1. Have a written document before building something new and create accountability by allowing engineers to discuss, talk and take decisions.
2. Document should include the key shared understanding, architecture and approach to be taken including any thing which might be risky or tricky.
3. Have a written agenda before the meeting, then write up and send out decisions and actions afterwards.
4. "Finally, allowing anyone and everyone to chime in is a key part of keeping a consi...
programming  agile  culture  management  engineering  cto 
9 weeks ago by acrookston
As unlikely it might sound, the above process both works and scales really well, from a handful of engineers to teams of thousands. It addresses not only issues on visibility or reducing tech/architecture debt, but also spreading knowledge and having engineers be more engaged day to day. This is the one, simple process I recommend any small or medium tech team to do, especially if they are in a growth phase. It's also the process we've successfully used and iterated on at Uber, going from tens of engineers to a couple of thousand ones.
engineering_management 
9 weeks ago by seanodonnell
Scaling Engineering Teams via Writing Things Down and Sharing - aka RFCs I have recently been talking at small and mid-size companies, sharing engineering best practices I see us use at Uber, which I would recommend any tech company adopt as they are growing. via Pocket
ifttt  pocket  architecture  article  management  programming 
9 weeks ago by jeremyday
I have recently been talking at small and mid-size companies, sharing engineering best practices I see us use at Uber, which I would recommend any tech company…
from instapaper
9 weeks ago by dorianj
I have recently been talking at small and mid-size companies, sharing engineering best practices I see us use at Uber, which I would recommend any tech company adopt as they are growing. The one topic that gets both the most raised eyebrows, as well the most "aha!" moments is the
9 weeks ago by cmhamill