Here’s a fun fact about my career: in almost a decade of working in Ruby, I’ve never been paid to write rails new
into a console.
At Groupon and Braintree I’ve helped build some of the largest and longest-lived Rails monoliths in the world. As such, I’m sometimes asked for advice on writing Rails code that lasts.
Someday I’ll write more on this subject. For now my definitive answer is my last talk at Ancient City Ruby, “Ancient Rails”
I’d also be remiss if I didn’t link to this excellent series on the topic from Braintree’s original CTO, Dan Manges, who had a major role in many of the things we got right.
I’ve been reading THINKING FAST AND SLOW by Daniel Kahneman. There is a real risk this blog temporarily becomes flooded by small bits from this fascinating work.
Friends know that I endlessly talk about team values. They’ve made a huge difference in my career - I still have a framed copy of Obtiva’s values next to my desk (complete with our Big Hairy Audacious Goal courtesy of Dave Hoover).
Let’s say you only have 5 minutes with one of your teammates to answer the question “How satisfied is this person with their job?” What do you ask and what do you look for?