You can either scroll down for a straight archive or all my archive, or click one of the below tags to see writing from a specific category. Or surprise yourself with a totally random blog post.
My first (of hopefully many) weekly lessons learned covers brittle tests, complex components, stupid questions, and existential emotions.
Testing is a topic I overlooked too much early in my career, which may have hurt my progress the most. This is everything I'd have told my past self about testing.
Look at anything from a narrow enough perspective, and it can be whatever your mind wants.
As a coder and a writer, I've often felt inadequate with what I'm giving back to the world. But there are ways I can give back, however small they are.
My project skeleton is a base starting point for simple, vanilla Ruby creations. I examine how the basic parts work together for fellow Ruby newbies.
Automation has always been a sensitive spot in my coding career, but I finally took a solid first step.
Many priviledged coders make a common mistake when thinking other coders should simply 'try harder.'
My mind's first reaction is often negative, and I try to work around these carefully so they don't pull me down.
Seeing so many professional writers emerge on Dev.To has helped me see, and accept, my casual blogger habits.
Another message to my past self, this time on the importance of accessibility, how to achieve it, and how to test it.
Asking for help is important, but so is learning how to give problems your best shot beforehand.
Three useful lessons taken away from my first, and possibly last, actual luxury vacation
Discovering ourselves means finding activities to fuel our productivity, empathy, and sense of empathy.
Willpower is less about 'powering through' lazy moments and more about evading them with careful planning.
I write a letter to my past self about the Shell's importance I wish I'd focused on earlier in my career.