Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



In this blog post I want to go over some of the software I use alongside my IDE/version control tools during my day-to-day work. These tools allow me to cut down on wasted time spent doing things inefficiently, track my work, take notes, and generally make my life easier.
I’ve also reached out to Damien, a local developer friend who has provided me examples of the tools they use as a front end developer.
In my opinion, Notepad++ is literally the best text editor you can use. I use it for almost everything that involves text outside of my IDE and I could dedicate multiple blog posts to cover all its features. But for now, here are my top 3:
Automate repetitive tasks with custom macros. Say you’ve got the boring task of opening a bunch of different documents. Once open you need to run a find and replace on the date values and convert them from using forward slashes ‘/’ to using hyphens ‘-‘’ (or something equally as tedious) and then re-saving the files as a different format. Notepad++ allows you to just record all the steps you take on the first file then run your recorded macro on the rest!

Powerful find & replace functionality. Notepad++ allow`3s you to apply your searches to not only the current file you are working on, but all open file or even all files in a directory, and their sub-directories!

It supports Regex search (and replace). If you’ve read some of my other blog posts, you’ll know I’m a big fan of regex. Regex searches even work with the sub-directory file searches, very powerful!

I could go on and on about Notepad ++ all day, I’ve barely scratched the surface. Not bad for a free tool right?
One of my most tedious workflows involves copying newly complied. dll’s to a remote server, then needing to restart a few services and recycle some app pools to register the changes on the remote machine. To do this manually it can take 5-10 minutes and I often have to do this many times a day. I quickly grew tired of this and instead created a little PowerShell script that takes care of the file transfers and service restarts for me.
PowerShell is a powerful tool for many reasons, but I find the ease in which you can automate away a lot of time sucks a true blessing.
cmder is mainly on this list because I love the way you can configure it to slide down from the top of the screen quake-style, I’m not even sorry. I love having it bound to a hotkey ( ` for maximum nostalgia of course )
It’s got a lovely default theme but includes many others. If you choose to install the git-for-windows version, you will have all Unix commands ready in PATH so that you can git init or cat instantly on every machine.
I must admit I mainly use it to look up things that would require me to use more mouse clicks than I would want to…

You can also do cool stuff like opening multiple different tabs of cmd windows, or even split them across the screen, all without your fingers leaving the keyboard.

Apart from that, it’s totally customisable and portable. If you can’t find the option you want to configure in the settings menu, you can fork & modify it to get under the hood and add features to your hearts content, and take it with you wherever you go.
Tools built specifically for building and testing API’s.
Insomnia is a tool designed to make designing APIs slick, streamlined and collaborative.
Whereas httpie is designed to let you call and test APIs directly from the terminal and is aesthetically pleasing to boot.
Damien’s picks for a fancy terminals (I’m going to assume he’s not heard of cmder…). These picks give you VSCode style auto complete, customisability, performance boosts and more. Or in Damien’s own words “Terminal super powers”.

Both tools enable you to produce quick mock-ups and application flow mapping directly in the browser by yourself, or collaboratively.

A Postgres DB that gives you GraphQL across all your data. Has a slick UI and makes implementing relationships super easy.
Deno is a simple, modern, and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust. Built to address the numerous shortcomings of NodeJS, but it’s on Damien’s list because “it has the best logo”.
I see what you mean.
You can find Damien at @damiensedgwick on Twitter if you want him to elaborate further.
There are a lot of tedious tasks and context switching in software development that can take your focus away from the task at hand. These can be mitigated or removed completely with the right tools. I’m sure you have your own keychain of useful software; I encourage you to speak to your dev friends about theirs!
I’m now off to read up about Insomnia and httpie, they look perfect for my next project, cheers Damien!
Share this
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
Find out everything you need to know in our new uptime monitoring whitepaper 2021