That's Not Our Code 3 minutes read.
Figuring out ownership over code (or service/application/component) is always challenging in a company with more than 3 engineers. It becomes even harder when teams emerge. Norberto Herz shares how you can create a hybrid model: "We should be more strict when working on something planned (like our roadmap) and more flexible for unplanned situations (like emerging bugs)." -- I believe this model can work well. It requires strong leadership (individual contributors and managers) that do not let people point fingers, calling code "ours" and "theirs."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Lessons Learned From Setting Up Instagram’s New York Team 5 minutes read.
Read this if you're thinking of opening another office, as Instagram's preparations and takeaways can save you serious pain. My biggest takeaways to think about: "So before making the investment in NYC, we went through the most significant re-structuring to date on our engineering team, instead organizing ourselves by product vertical — Explore, Feed, Search, Content Creation. This meant we could consider much more atomic units of teams..." and "we wanted to kick things off with a base of people who had been at Instagram in California for a while and could be the culture-carrying pioneers. Specifically, we wanted to move tech leads and senior engineers, rather than managers, first."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.