In an early job I skipped writing tests, thinking it would make my code more flexible and maintainable. I slowly found it did the exact opposite.
In 2019 I focused on numbers for doing better in work and play. That focus caused most of my past year's regrets, and I plan to take a much different approach for 2020.
Webpack is great, but too big a tool for my personal site. This is how I viciously murdered my Webpack processes for NPM scripts.
A beginning coder's guide to structural design patterns with an alternate telling of Cinderella.
A beginning coder's guide to the other half of behavioral design patterns with an alternate telling of Snow White and the Seven Dwarves.
Being insecure about my career and skills likely won't change anytime soon. Finding the positives is something I can do now.
After weeks of looking for a workable approach, I finally build a Node Twitter bot to automatically share anime quote artwork.
I don't consider myself a tech ally, but have several ways I try to act as one.
A beginning coder's guide to half of the behavioral design patterns with an alternate telling of Goldilocks and the Three Bears.
A beginning coder's guide to understanding creational design patterns with an alternate telling of The Three Little Pigs.
Refactoring code is a tricky business. This is a small example of how fixing old CSS code creates even more problems to solve.
The Dev.To community chatted about how they manage digital addiction. In case you missed it, here are the big takeaways!
There's plenty of common arguments against web accessibility that are dead wrong. Here are five of them with some ready-to-go counterarguments.
A SubAtomic Frontend Architecture balances Atomic CSS and BEM class naming to build a fast, flexible framework.
I celebrate a long-overdue side project by examining its most important pieces - services, singletons, and which Eeveelution matches my personality.
This week was learning about balance - balance of work and play, and balance of explore and exploit.
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.
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.'
Seeing so many professional writers emerge on Dev.To has helped me see, and accept, my casual blogger habits.
I write a letter to my past self about the Shell's importance I wish I'd focused on earlier in my career.
When getting feedback from coworkers about your code, don't let your ego stop you from doing better.
Despite confidence in my 'Maintainble CSS' talk, a lack of focus made it go long. Here's how I don't plan to repeat those mistakes.
Two months after redesigning my site, a big event makes me do it all over again.
I revisit my first real Node program to refactor it with more ES6 syntax, asynchronous functions, and anime wallpaper feeds.
As you’ve (hopefully) seen by now, we have completely overhauled the SeeClickFix homepage and corporate website. I share my favorite code from the new site.
If you don't know what rebasing in Git is, read this before it's too late. Especially if you love cupcakes!
For my first web project that wasn't a website, I broke down a goal that involved Node, scheduled functions, the Twitter API, and a feed of anime wallpapers.
All web developers will fight Impostor Syndrome at some point, and find their own way to fight back.
It's easy to see why pattern libraries are useful, but tough to successfully maintain them over time.