The False Trade-Off Between Quality and Speed 7 minutes read.
"In the current world of service development, products are built as long-term services that keep evolving over time to adapt to their users’ needs. As a consequence of this, most product development work happens in the context of an existing code-base and an existing live product. [...] For most cases and in most stages of the lifecycle of a project, building low quality software is slower than building high quality software." -- Mario Caropreso with a brilliant and important take. First, writing your definition of quality would be a great exercise. Second, shifting the framing that software should work for years, you now look at the notion of speed very differently. It's not always true (e.g. early startup stage), but once it does, your mindset should change if you want to build a sustainable company.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
PM & EM: Rules of Engagement 8 minutes read.
Writing how you see two roles in the company interact has massive value in setting explicit expectations: "This was created as an internal document at Segment a year ago and it’s been incredibly well-received. It’s used by new PMs + EMs looking to build a successful partnership, by seasoned PM + EM pairs looking to debug specific responsibility and ownership issues, and by managers wanting to help their teams understand how to become better functional partners." -- Where do you think writing such a working relationship will help your company?
Read it later via
Instapaper.
Share
it via
Twitter
or
email.