Culture
The Career Story Interview: Give the Best Interview of Your Life 6 minutes read.
You can use Rich Paret's framework for how to interview for competencies based on past-behavior questions. The biggest takeaway is that you need to come prepared with a list of questions and what you're trying to learn from them (including good/bad answers). Most people don't spend more than 1 hour picking questions and then using them on hundreds of candidates. Write down what you want to ask, what you want to learn from it, how great answers (and why!) look like, and how bad answers look like. Share it with a few people in your team who interview as well, and see if these are useful questions to use, or you can iterate on them.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Fulfilling the Promise of CI/CD 6 minutes read.
"The time elapsed between writing and shipping is the room temp petri dish where pathological symptoms breed and snowball. Longer lead times lead to larger code diffs and slower code reviews. This means anyone reviewing or revising these nightmare diffs has to pause and swap the full context in and out of their mind any time they switch gears, from writing code to reviewing and back again." -- Worth reading this post by Charity Majors and the post from last week, "When costs are nonlinear, keep it small," to think about your deployment strategy.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
What Makes A Strong Product Culture? 7 minutes read.
Ken Norton shares questions you can use for your current company or future ones, asking the interviewers these questions. Most companies can do better is the third bullet, forming "Empowered Product Teams" as the company scales. Easier said than done. Keep this pot in your bookmarks. Worth reading every few months and see if there is a positive trend.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.