Reading software and thinking about it
Normal software work is so much about changing the system. Add capabilities. Change behavior. Imagine what could be or should be. Understanding what is – always a byproduct or a precondition of change.
Do you worship work?
Three book recommendations for thinking about getting meaning from work
Mere Being 012 - April - More from other Pivots, Magic, Criminal Business Processes
I'm not the only person writing about Pivotal. Plus, an old way to play Magic, and some notes on the Sopranos.
One weird trick for... figuring out your values?
Seriously just write a Rails (Phoenix) app
Basically, it's this: I don't have to think as much about where to put a piece of behavior. If I'm wrong about where it ought to go? I just move it. I don't have to change what language it's in or update a client or write new tests or any of that.
Don't lie in interviews
If your model is "it's okay to lie if I've been lied to" then we're all knee deep in bullshit forever and can never escape Transaction Cost Hell.