prioritization

This post is cross-posted from bigeng.io — feel free to read there! I’ll be straightforward at the start of this post: I firmly believe that the most important issue a company deals with is how it reconciles itself with technical debt. Period. Now, here’s the real point of this post: Technical Debt is a Positive and Necessary Step in software engineering. First off, let’s define technical debt for the purposes of this post, as the words can mean many different things to different people....

A long while ago, I did a consulting gig for a mid-sized company. This company had spent thousands of dollars on a revamp for one of its sections on its website. It was pretty slick: filterable navigation, lazy-loading, compressed assets, blazing load times. It used all the modern design principles and standards. It was mobile friendly (a big deal for the time). The design was slick, informed and easy on the eyes....

It seems like every single company I’ve worked for, or interacted with, is currently striving to find the “10x” engineer, the rock-star developer, the genius game-changer software architect. Much effort and time are put toward getting these liberators of success, with companies not only believing but actively spreading the idea that these people exist, and they are going to get them. There’s just one small problem. No one really knows what the 10x engineer does, or looks like, or represents....