The Lone Developer Problem
Being the only person able to program in a small team, I know I am the target of the criticism in this post.<p>I think it is mostly true, I wish there were other people looking at my code, but for years I&#x27;ve been working on projects alone.<p>What I came to realize is that there are some kinds of software where quality is paramount, mainly the code that will carry on for years, and require constant changes.<p>But there are some software that only exist to fix a particular issue that doesn&#x27;t require change over time. The typical Perl script that lives unchanged for years doing a single task. For this particular case, quality matters less than portability and relying on solid dependencies that do not require maintenance.<p>In the end, management does not care about code quality, as long as money is flowing.<p>For lonely programmers, identifying the code that should be high quality (the one you will be looking at continuously) and the one is only there to fix a single problem is really important.