“It’s not that I mind filling out another survey, it’s more that we haven’t heard anything about the other one we just filled out.” The comment had no snarky tone or accusatory subtext. It was meant as a simple matter-of-fact comment on what I had just asked the team to do.
It’s 3 a.m. You’re wide awake. You’re having a conversation in your mind with a colleague, a boss, a client. Again. The same one. Seemingly on repeat for the past few days, weeks, or months even. Barring some intractable factors, it appears it’s time to transition that hard conversation from inner monologue to outer dialogue.
Most of us love a good personality assessment. They’re usually fun, can help us understand ourselves better and, at times, may even have implementable tips for us. But, there are unspoken pitfalls that we need to watch out for.
Legacy code is everywhere, and it's here to stay. Anything that someone else has left behind is their legacy. After a while, what they left behind might not play nicely with new code. Several key issues can come from legacy codebases, ranging from alarming security vulnerabilities to frequent bugs and plummeting developer productivity.
Nintendo started out producing handmade playing cards. Netflix was selling and renting DVDs by mail. Starbucks used to only sell high-quality coffee beans and equipment (no brewed coffee or delicious handcrafted espresso drinks!).