Skip to main content

My top 3 development tools

Every developer has a set of development tools which they use on a regular basis. Below is a list of my top three tools, why I use them, and how they benefit me. In the list below I haven't included code editors, IDEs, or extensions to IDEs. Please note: this may disappoint many of you who are expecting something "advanced" or "funky".
Some tools. Source: Wikimedia Commons


Git has become the VCS of choice these days, and I have previously advocated that those who use git should primarily use it from the command line. It does get annoying after a while doing a git status simply to see which branch you're on, or how far behind you are in respect to your tracking branch. Why I like using the posh-git prompt, is because gives you a representation of your state as part of a console prompt.


LINQpad is probably one of the best tools out there for C# developers. I use it primarily in a few ways. The first, is using it to communicate with data stores. The second, is using it as a quick way to validate my understanding of framework method calls. Finally, I use it to micro-prototype algorithms I'm writing.


cmder is a great console emulator. It can customise fonts, colour, and transparency. What I use the most is the multi-tab feature, where I can have git on one tab, front-end build tools running on another, and another for traversing my file system.

The above may come as a disappointment to some. You might ask "these are simple tools, they don't do much". That's probably true, I've always liked to keep things simple and have minimal abstractions when developing against a particular platform. It's a personal preference!


Popular posts from this blog

My first time speaking at a conference

Since time immemorial we humans have valued the art of public speaking. Today, I want to share with you my experiences in speaking at conferences for the first time. Recently, I spoke at both DDD Melbourne and DDD Perth. Both of which were positive experiences that I learnt a lot in.

from zero to production in eighty days

When I mean zero, I literally mean zero. A brand new project, a PO that's new to IT, no existing processes in place and a small team of four including myself and the PO.

The departmental organisation we were working for doesn't have any developers, scrum masters, product owners working for them. Everything they did was either done by another department or outsourced completely.

This is a story how we went from zero to production in eighty days.

Context and agile practices

At times we have competing responsibilities - ship code or don't ship it because of a small edge case bug; put pressure on our team or make the business happy; coach our friends or write code.

This is a normal part of our everyday professional lives, and it's important to strike a balance that will help us in the future, but also deliver in the short-term.