There was a time when I believed that becoming a better developer was all about learning more, knowing more, and mastering new languages. But then I realised, it’s not just about being better—it’s about being faster. Fast enough to impress, delight, and sometimes even save the day. Today I want to talk a little bit about working faster as a developer.
Why do you want to move fast?
The faster you work, the more experience you get in the same amount of time. As I’ve blogged about before, experience density is incredibly important for getting ahead. Secondly, the faster you go, the faster your customers get the value you’re creating, and this is particularly important in start ups and small businesses. Finally, the time I think its most valuable to have these skills is when things are going wrong. Mastering the skills to code, troubleshoot, and work faster is crucial during downtime issues, critical bugs or urgent matters can make you the hero of the office and hugely valuable to your company.
What working fast doesn’t mean
I don’t want you to think I’m advocating for rushing in this blog post. Working fast does not mean rushing. It does not mean putting out lower quality work. It does not mean skipping steps. And finally it does not mean putting out a worse product your customers hate. Working fast is working to your usual high standards but simply in a shorter time frame. With conscious effort and practice, you can make it happen.
It’s all about habits
If there’s one thing that I’ve found to be scarily true, it’s that habits cumulate. Good habits speed you up, and when they cumulate, you can go faster and faster. But the opposite is also true, bad habits can slow you down, and when you have many bad habits, you can approach a glacial pace. This post is about habits. Habits you should work on over and over again, collecting more and more as you cumulate to approach the most efficient version of yourself.
Why?
You might think “Why should I work faster?It's a problem of motivation, all right? Now if I work my ass off and Initech ships a few extra units, I don't see another dime; so where's the motivation?” This is true. I’m not advocating you work at 120% every day at the office only to burn out to a crisp in weeks. And I certainly don’t advocate it if you feel you won’t be recognised for it. Good companies with good managers will recognise it (bonuses etc) and these companies will open doors faster for you than they would for others. And of course finally, you have your own ethics, values and craftsmanship to consider when deciding how much effort to put in. Do what feels best for you.
Disclaimer
I’m not perfect. I don’t follow all these tips myself either 100% of the time, and I’m not claiming to be faster than you or my team. Finally, this list of tips is not al the tips out there. Please keep looking for them and collecting them. And I’d love if you found some that worked for you and you let me know. Perhaps this list can keep growing. Let’s get into the tips.
1. Develop a Sense of Urgency
This idea is borrowed from the retail space, where work happens quickly in order to keep a store running smoothly. If you want to move fast, you have to want to move fast. It’s not about rushing or cutting corners, but about cultivating a mindset where you’re driven to deliver value swiftly. A sense of urgency isn’t something that just happens — you have to nurture it. Start now.
2. Copy and Paste Effectively
Let’s be real: copying and pasting is a developer’s best friend when used wisely. But the key is knowing when to start and when to stop. Don’t just blindly copy code; understand it, and make sure it fits your current context. Sometimes, it’s better to copy the idea rather than the actual code. Ask yourself: “Surely another team has solved this” (and go look at their code) or “Surely I’m not the first person to do this” (and go to Google/StackOverflow/CoPilot). On the team idea - its a good idea to keep a bit of a mental map of what other projects your team or wider team are working on, to give you a some places to check. Paying attention to work going on around you pays off in all sorts of ways, but this is one I’ve enjoyed a lot. Start unmuting those slack channels now.
3. Master Your Language
Whether it’s TypeScript, Python, or any other language, having the syntax in your muscle memory is crucial. Practice regularly, beyond just your backlog tasks, to make sure you’re always sharp. Finding solutions for tricky parts is just as important as mastering the language itself. Go write a lines of code for practice.
4. Use IDE Extensions to Your Advantage
Your IDE is a powerful tool, but it’s only as good as the extensions you use. Regularly explore new extensions and ask colleagues for recommendations. For instance, tools like JSON to TS or Toggle Case can save you loads of time. Share the ones you find, and even set them up in your code templates so fellow devs get recommended they install them. Also, if you see a colleague do something when you’re pairing that looked fast/magical - stop and ask them how they did that– you want that power too! Ask your colleagues for their recommendations now.
5. Use Terminal Aliases and Dotfiles
Long commands slowing you down? Create aliases. For example, gco for git checkout or gcob for git checkout -b. These small shortcuts can add up over time. Check in your dotfiles and use them everywhere you go. Even think about creating a standard set for your team. Get yours into Github now.
6. Search Documentation Smartly
When you’re deep in the weeds, knowing how to efficiently search through documentation can be a game changer. Use shortcuts like Command + F in Chrome to find what you need quickly. However, when you’re new to something, it pays to slow down and read the full documentation to get a comprehensive understanding. The better mental model you have for what should be in some documentation is the better – as it makes it easier to find stuff. Finally, you’ll realise there’s a few popular tools for documentation out there that a lot of OSS uses and so eventually you’ll build some skills on how to find the search bar, toggle dark mode, even if you’ve never been to that particular website before.
The other part of this tip is knowing how to get do the documentation of your tool fast. Command clicking on method definitions, or googling certain terms, or having it bookmarked. Work on reducing the lag time from deciding you need to look something up to being in the right place and reading it. You should also be very effective in documentation you use regularly.
7. Understand the Big Picture
Stepping back to understand the broader concepts behind what you’re doing can speed you up in the long run. For example, don’t just learn how to use AWS SQS; understand the concept of queues, messages, retries, visibility, etc so when you encounter similar tools like Azure Queue Storage, you can adapt quickly. Mapping existing knowledge onto new things is only as good as the existing knowledge - so keep building it. Reflect a lot on your work. Reflect, reflect, reflect. Lock in that learning. It will cumulate. Remember my saying: Work + Reflection = experience. The more experience you have, the faster you go.
8. Be an Expert in Your Tools
Spend hours a day in tools like VS Code, AWS, or GitHub? Make sure you know them inside and out. Learn the shortcuts, understand the error logs, and know when to restart your tools. Mastering this expertise shaves precious seconds off your workflow. Let’s say you’re a VS Code User, you’re in it eight hours a day. Do you know the shortcuts? Do you know multi-cursor editing? Do you know how to see logs for extensions? Do you know when your extensions aren’t kicking in? Do you know when it’s time to give up and restart VS Code? If you’re using something for 8 hours a day, there’s really no excuse to not know your tools inside and out. This is a sign of any good craftsman. Watch some tips and tricks videos on your IDE today.
9. Shorten Your Debug Loop
The debug loop is the time between writing code and seeing if it works. Aim to shorten this as much as possible—ideally to just a few seconds. Setting up a quick debugging environment or even creating a small test project can pay off in the long run. Learning how to enable debugging (or at least logging) in your tooling is also hugely important, as it will save you time and time again. Start thinking of ways to shorten your loop on your current task.
10. Leave And Read The Clues
Code changes over time. Additions, subtractions and substitutions. There are small but powwerful things you can do to help the next person change the codebase (which will likely be you). Comments, README files, and a well-structured codebase are your future self’s best friends. The more clues you leave, the faster you’ll be able to navigate your code later on. Of course, learning to read the clues is just as important as well - for example, recognising the codebase structure by the patterns it uses, Clean Architecture, Singleton, Serverless. Next time you’re in your codebase - try ‘read the room’ a bit more - what do you notice?
11. Bookmark Everything
Websites, code snippets, curl/postman requests—if it’s useful, bookmark it. This way, you’re never more than a click away from the information you need, or you once had. Both physically bookmark it (in a tool like your browser or snippet library) and mentally bookmark it – so you remember you have it stored. A forgotten bookmark is no use to anyone.
12. Automate Repetitive Tasks
If you find yourself doing the same thing every day, automate it. Whether it’s a bash script or a custom tool, automation can save you hours over time. My teams often build internal CLI tools or script collections, making it easy for everyone to write and share scripts. This is a super powerful way of keeping yourself and others speedy. Pitch this to your team today!
13. Slow Down to Speed Up
Sometimes, the fastest way forward is to slow down and learn something properly. Don’t hack away at things just to get them done—take the time to understand what you’re doing, and you’ll move faster in the long run.
14. Practice Makes Perfect
Side projects, hackathons, or even working on internal tools can give you the extra practice you need to get faster. The more you code, the more efficient you’ll become. It’s cliche, but practice makes perfect. There’s always more stuff to be done, in both side projects and at work, so as your team if you have capacity and want tasks to practice on.
15. Document What You’re Learning
Struggling to learn something? Document it. Writing things down not only helps you retain information better, but it also gives you a reference to look back on later. I might even be doing this right now. By typing out stuff you're struggling with, you will learn it and retain it better. You will find gaps in your knowledge as you try to paint a narrative. Start a blog or a personal diary today.
16. Be Aware of your Surroundings
Its highly likely another developer has solved the same problem you have. Keeping an eye on your teams work channels, emails, sprint reviews, etc will help you learn waht others are doing. Store a mental bank of all of it, so you can go ask people or their code for help. You can do things like searching slack or emails to help you recall. Finally, peers teams to work and ask questions in public forums can benefit everyone, even if it is a little awkward and be embarrassing. It also helps to build a network in your team and company to collect the set of gurus who can help you with various things. And pay that forward - if you become a guru in something, be approachable as well.
17. Ask for Help at the Right Time
Knowing when to ask for help is an art. A skill you will build over your career. Don’t spend hours in the weeds—reach out when you’re stuck. But also recognise when struggling through something on your own will lead to valuable learning, and perhaps make you faster at the future. Keep working on that intuition of when to ask vs when to push through.
18. Lean Into Your Tools
Tools like TypeScript (over JavaScript), Unit test frameworks, linters, formatters can save you so much time. Lean into these tools and understand their features and powers and reap the benefits. Be on the lookout for more tools that you can add to save you time. Ask your more senior developers if they have ideas for tools they think would benefit your team.
19. Stay Busy
Always have more than one task on the go. If you’re blocked on one, even for a few minutes, move to the next. And if you run out of work, don’t wait for the stand-up—reach out to your lead or manager immediately to get more work. There’s always more to do and downtime robs you of experience you could be gaining. After you finish this post, check the backlog for something to do in parallel.
20. Scale Yourself
If you’re creating packages or working on shared code, document it thoroughly. The more you document, the less time you’ll spend answering questions about the work later on. If you contribute 10 internal code packages to your team, but don’t document them – can you imagine how your days will look? You’ll be bogged down answering questions. However a good readme or changelog that does the talking for you can free you up for more interesting things. What is essentially happening here is your past work is working for you without you doing anything. It’s what this blog post is doing for me right now. Saving a 1:1 conversation with every reader. Try this on your next work package.
Bonus: Using AI Coding Tools
I’m in my early days of using AI Coding tools (at home) – Like GitHub CoPilot – so my observations are limited. However I’ve noticed for situations where you would think many other developers have done what you’re about to do, like write a map function or do some bread-and-butter react coding, then AI tooling can quickly generate boilerplate code. However, I’ve wasted plenty of time expecting too much from my AI assistants, so do be careful and take your time to figure out when they work and when they don’t. Also be sure not to rob yourself of a learning opportunity when asking the AI to solve it for you - you may be robbing yourself of future speed.
In the end, moving faster as a developer isn’t about rushing—it’s about building the right habits, using the right tools, and continuously refining your process. Start implementing these tips today, and watch your productivity soar. And remember, the aggregate effect of all these small changes is where the magic happens. You’ve got to want to move fast, and that’s not for everyone, but I recommend it. In the end, moving faster isn’t just about speed—it’s about efficiency, creativity, and staying ahead of the curve. It’s about wanting to be the best you can be, without burning out. Good luck.
Top comments (0)