Pro developery stuff
Software development productivity methods, tips, and thoughts from a generalist software engineer.
"What is better than building software?
Building it the right way."
Who am I?
Nowadays, engineering @ Automattic.
What makes me tick?
I subscribe to the jack of all trades philosophy. I strongly believe that to succeed in the ever-changing tech landscape of today, a software developer must constantly learn new skills as required at work. Gone are the days when specializing in one technology or stack could propel you in a traditional technical hierarchy.
My mantra to learn rapidly and effectively is to master the 20% of a skill that will account for 80% of my application's codebase (see Pareto Principle).
Why does it work?
By applying the 20% method of learning, I can be productive in any skill in less than a week. Time gained by focusing on fewer (but important) concepts allows me to jump into development early. However, it's paramount that I learn that 20% the right way*. Quick and deep-enough learning leads to robust code that scales and requires less refactoring later.
*with BPST aspects - big-picture, performance, security, testing
Let's start a movement
Together we can make a small positive dent in the fabric of software development by disseminating good practices and learning methods. Together we can make software better and more sustainable.
Every month I send helpful developer productivity tips and share my thoughts on other software engineering topics.
You can add your email below to receive updates from me. I promise to keep it safe and not share it with any person or company ever. It's a purely informational newsletter, without the corporate bullshit.