Greetings, my fellow Rubyist! It's been a while! Getting back into the swing of things this year after the holiday break proved to be more challenging than I anticipated. But nevertheless, I am here and ready to talk shop.

I thought it might be worthwhile to switch gears a bit and write a philosophical post about a topic near and dear to my heart: less code. As many an experienced programmer will tell you, sometimes the amount of code you remove, or refrain from writing in the first place, is just as important as the code you contribute to a codebase. I explain in my article:​

I am always on the lookout for these higher-level abstractions. By ensuring many of the lines of code in your application serve a broader purpose, rather than comprise part of merely a single chain of logic, you can get way more done with (ultimately) less. And the more you pivot from solely writing feature-facing code and wade into the waters of authoring libraries and frameworks, the more vital this skill becomes.

Anyway, I hope you enjoy this article, and please let me know what you think! Your feedback is much appreciated. –J

​What’s Better Than DRY? DOEY! (Don’t Over-Exert Yourself)​