6 Lessons I learned while implementing technical RFCs as a decision making tool

As an engineering leader, I value trust and believe that individual contributors should be involved in architectural and high level technical decision making. I consider every line of code to be a decision made on behalf of someone else (including your future self) and having a fast-growing distributed team makes technical decision making particularly difficult to manage. In the early days of building <a href="http://www.businessinsider.com/uber-cofounder-oscar-salazar-launches-ride-2015-4" rel="noopener ugc nofollow" target="_blank">Ride</a>, we went from 3 to 25+ members across product, design, and engineering in the first six months. We were tasked with the challenge of taking an early <a href="https://techcrunch.com/2014/12/11/ride-b2b-carpooling/" rel="noopener ugc nofollow" target="_blank">prototype for a carpooling platform</a> and bringing it to life on the web, iOS, and Android. To make things more fun, we were also distributed across the US, Mexico, Colombia, Brazil, Argentina, and Ireland. In the process of building our apps I received a private Slack message: <a href="https://buriti.ca/6-lessons-i-learned-while-implementing-technical-rfcs-as-a-management-tool-34687dbf46cb">Visit Now</a> <ul> <li> </li> </ul>