This year I racked up just over ten thousand pages across twenty-five books. Here are a few of my favorites.
Biography and military history continued to top my reading list for another year. At the top of both these categories was Grant, Ron Chernow's thousand page biography of the Civil War general and 18th U.S. President. As I mentioned in my review, it may be my favorite Chernow book so far.
Seldom does such great storytelling meet such an epic story as in this book. In clear, descriptive language with military detail approaching any Clancy novel, the authors tell the story of Indy, her crew, their successful secret mission to deliver the world's first nuclear weapon, their loss at sea, and the pursuit of justice for their captain.
From sea to courtroom, it's an entertaining blend of action, adventure, courage, perseverance, love, heartbreak, loss, and redemption.
A fantastic book from Karen Swallow Prior that shows us how to read literature and cultivate virtue.
You can check out all of the books I read in 2018 on Goodreads.
I'm excited to be joining InVision as a Principal Engineer working on Studio.
ThoughtWorks has released their latest technology radar (PDF), a semi-annual analysis of the industry landscape from their vantage point as software consultants.
I've enjoyed reading past issues as a way to mindfully keep up with trends and discover new tools. With topics broken down into techniques, tools, platforms, and languages & frameworks, past reports have helped clarify my thinking and given me a concrete way to talk about patterns and techniques already in use.
I'm excited to see Apex and Netlify get mentions this year.
I'm also a little puzzled how GraphQL fell off the radar without landing in the Adopt category. Maybe because it's already arrived.
Both distributed and co-located teams can benefit from getting explicit about their role within the broader organization. Here are some practical things to include in your team's intranet page or GitHub team repository README.
Even with the best HR department, successful onboarding requires effort from the whole team. Here are some practical ways you and your team can onboard engineers with greater speed and success.
Inconsistency is a tax. We often struggle so hard to handle inconsistency in the problem domain, we never notice the cost of inconsistency in our code.
Has your team written down its process? There's incredible value in having a document that outlines "How we work."
The next time you think about writing another shell alias, consider these more advanced approaches to extending CLI apps.