When I used to code all the time, I'd go to bed and have code-mares. The same problem I was wrestling with would play in a stressful loop in my mind - but on some rare occasions I'd actually find the solution in my sleep. I'd wake up and, impatiently, couldn't get back to the keyboard fast enough. I was filled with excitement that a solved problem gives you.

Recently I've been doing some mild carpentry at the house (building a mudroom bench and laundry cabinet). Carpentry, I've found, produces the same kind of feelings that coding can. I love it but I find myself frustrated when the right solution feels slightly out of reach.

Suffice it to say, I had my first carpentry-mare. The dream made me realize I'd missed an important detail - and so, waking up, it was the first thing I had to do.

That's when I realized a very important lesson about the difference between coding and carpentry: despite their similarities, coding is much much quieter.


Let's Clear Up The Ambiguity!

FAQs for a Software Engineering Hiring Manager

7 Steps to Writing an Amazing Resume

7 Steps to Building your Portfolio MVP

On Systems Debt