The Lone C++ Coder's Blog

The Lone C++ Coder's Blog

The continued diary of an experienced C++ programmer. Thoughts on C++ and other languages I play with, Emacs, functional, non functional and sometimes non-functioning programming.

Timo Geusch

6-Minute Read

If you look at really productive programmers - like the top 10-20% - there are usually a couple of characteristics that they share. Aptitude and in-depth understanding of both the system they are working on and the technologies involved is obviously one very important factor. Another factor that tends to be overlooked is that these programmers are also masters of their tools in the same way that a master craftsman - say, a carpenter - is also a master of their tools. That includes potentially obscure tools, and the ones handed down from grandps or found at a yard sale.

I think that mastery of your tools plays an important role in your ability to be a productive software engineer. If your tool interrupts your workflow because you need to figure out how to accomplish a task at hand, you immediately waste precious brain cycles on this disruption rather than being able to use them in the flow of software creation. That sort of disruption can easily drops you out of “the zone”, and those brilliant thoughts might never make it into your software as a result.

There’s also a trend that I’ve seen over quite a few years in a lot of companies (usually large, with IT departments that most developers would find overbearing, but it’s not limited to these companies) limiting the tools that are available to developers. The usual attitude seems to be that if a certain tool is not included in , it is not needed for serious software development and thus developers are only requesting these tools because of their magpie like tendencies or worse, because it allows them to polish their resumes and then wander off and get a better job.

Leaving aside the latter “justification” - if you work for a company like that, my suggestion is that you find yourself some career opportunities elsewhere anyway - you’ll end up running into the issue that the one tool you need hasn’t been requested by anybody else and thus is not on the very short “approved” list. Your manager will have a hard time justifying the expense because nobody else “needs” that tool and thus requested it. Plus, IT departments tend to have an ingrained dislike of exceptions of any kind, because it usually tends to make their job a lot harder. A short list of approved software with everything else banned does make it possible for them to support thousands of machines, but at the expense of inhibiting the creation of a work environment that is designed to give people all the right tools they need for maximum productivity.

Most craftsman own their own tools. A carpenter will show up at a job site with their own tools, a car mechanic uses tools he’s acquired over his career. If you subscribe to the view point that software development is a craft and not an assembly line operation, then maybe it is time for us software engineers to step up and tell our employers or clients that we don’t expect them to pay for certain tools, but we will bring them with us and expect to be able to use them. Of course, the latter is going to be the issue - there will be clients and workplaces with the IT policies designed by Mordac The Preventer’s cousin that will under no circumstances allow a tool on the premises that has not gone through an 18 month vetting process by the secret IT ninjas - but to me this is the sign of an environment that is conducive to good software development if it is being recognised that a craftsman’s tools play an important role in both their ability to produce quality work and enjoy producing said quality work.

If your development team doesn’t enjoy what they’re doing, they’re not going to be at their best and create the absolute best software they can. And we already have virtual shelves of “good enough” software available, we don’t need more of that.

While there is a need for some standardized tools like the compilers and the basic build environment - I really do not want to work in an environment where everybody gets to bring their own compiler, I’ve seen how that movie plays out, thankyouverymuch - there is absolutely no reason to hire someone who is a SublimeText/VIM/MultiEdit/BBEdit wizard and force him or her to use Notepad or edlin. Let them bring their own editor, IDE plugins, customizations and let them use it. Let them use the shell they can drive in their sleep.

The same goes for certain types of specialised tools or plugins, heck, even keyboards. For example I expect to use a certain type of keyboard at my workplace due to an old injury and I’m happy to bring one in so I don’t have to use the “but it came standard with the Dulls we buy and it is the only keyboard you are allowed to use” $5 RSI-waiting-to-happen piece that gets inflicted on seemingly everybody.

That said, I am in no way advocating anarchy in the workplace here. There are certain limits that need to be set in a case like this - for example, one of my rules is that no matter what editor you use to write your code, it has to apply the same formatting in all editors across the team. Yes, as a result everybody in the team will have to tweak their editors to ensure they don’t litter the code with tabs instead of spaces and result in formatting that make the source code unreadable in six out of ten editors used by other members of the team. The code will however look the same in everybody’s editor and its readability (or lack thereof) will be the same. Large bodies of code are already hard enough to read as is, we don’t need to introduce additional hurdles.

You also don’t get to pick your own build tool and thus be the only person on the team using CMake while everybody else is using MSBuild. Or use the latest nightly build of GCC when the production code is built using Visual C++.

At the end of the day it’s a balancing act, but as a manager you want to ensure that the tools your developers use are the ones that provide the least distraction to them. You absolutely do not want to inflict tools on a team that get in the way (ClearCase, anybody) when there are tools out there that are designed to complement the workflow rather than inhibit it.

Recent Posts



A developer's journey. Still trying to figure out this software thing after several decades.