Search for a command to run...
I'm Al. I'm a self-taught web developer with a nack for learning new things and breaking stuff. I enjoy being creative but find expressing it artistically, difficult. But, once I found coding, I was able to express that creativity that no paint-brush or paint-mouse ever quite could do for me and I've never looked back since.
🎶 Started with the LAMP-stack, now I'm all about that JAM-stack. 🎶
No comments yet. Be the first to comment.
In this series, I explore the various learnings so far that I practice and uphold daily (Kaizen) as a self-taught web dev over a decade, and now manage a high-performance international web team.
What advice I would give myself starting web development, a decade later.
Listen up, virtuosos of the virtual realm and champions of childhood! As we reach the grand finale of our Agile Parenting saga, we reveal the ultimate boss-level strategy: Co-Gaming. It's time to draw on our shared passion for gaming to build lasting...
Hark, digital devotees and pioneers of parenting! Our Agile Parenting saga now takes us on a quest to decode gaming culture and understand its impact on our young adventurers. Strap in, folks! It's time to unravel this intricate tapestry of bytes and...
Greetings, warriors of the gaming realm and guardians of growing minds! Our Agile Parenting odyssey brings us to a vital stage often overlooked in our quest - the self-care of you, the Gamer parent (Dad, in my case). Yes, noble knights of the network...
All hail, sultans of the software and emperors of emotion! Our Agile Parenting saga draws us into a territory that pulses at the core of our journey - emotional connection. Yes, fellow gaming parents, today's quest unveils the power of gaming as a to...
Greetings, patriarchs of pixels and defenders of domestic duties! Today, on our Agile Parenting journey, we delve into a realm even the bravest of us may dread - the mundane yet crucial world of homework and housework. Fear not, fellow gamers! With o...
Diving a bit deeper into a previous article, the first practical advice I pass on is to learn why something is a "best practice" and then use it.
A senior developer I worked with in the past explained it to me using this Michael Jordan quote: "You can practice shooting eight hours a day, but if your technique is wrong, then all you become is very good at shooting the wrong way. Get the fundamentals down, and the level of everything you do will rise."
"But Al - I see developers doing horrible things in the name of "best practice" all the time, how is that okay ..."
Sometimes we forget that a "best practice" has two types as its definition "method or technique that has been generally accepted as superior to any alternatives because it produces results that are superior to those achieved by other means" OR "it has become a standard way of doing things."
A lot of the time, what started as the first part slowly became the second part, and this is only natural as teams develop over time.
A best practice is only "best" if it continues to deliver on that high value, and it should be re-evaluated and assessed every so often to see if the practice still is "best."
This is why I say it's essential to learn WHY something is a best practice - what pain did this solve? New people don't know that pain, so I always let a new person experience it, too, so then they also understand the importance of that best practice.
