Culture
The Conjoined Triangles of Senior-Level Development 12 minutes read.
Figuring out your own defintion of Senior Engineer is hard, so much so that you can see it in this sentence I'm sure you've experienced before: "It’s completely possible for a person applying to multiple dev jobs to be evaluated as junior at one, mid-level at another, and even senior at another, with very little feedback as to why." -- While I'm not sure I agree with it all, I feel it's a honest attempt to make this defintion concrete. Making it helpful. Brandon Hays ends the post with this golden nugget: "Let’s bring open source thinking to how we hire and grow our people."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Sunk Costs and Managing Assholes 5 minutes read.
One of my favorite reads for this week by Jessica Rose. "Having your team build informal processes to work around bad actors creates an environment where additional time and energy costs are included in all team activities. It’s the HR version of technical debt, draining the team’s time, energy and morale." -- so much truth in this statement. I highly recommend reading the section "You can afford to lose toxic people".
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Reducing Risks by Taking Risks 4 minutes read.
This post by Yonatana Maman reminds of me Stripe's "learning from kill -9" post a few years back. Experimenting is how you can gain real confidence in the strength of your system. Are you doing enough to play with your system, figuring out single point of failure by playing the role of a "chaos monkey"?
Read it later via
Instapaper.
Share
it via
Twitter
or
email.