Not “the best tools” - just the ones that fit how I work.
As developers, we all build our own little ecosystem of tools that make our workflow smoother. These aren’t universal recommendations or “must‑haves” - they’re simply the tools I reach for most often, and why they work for me.
1. VS Code + Python
My main development environment.
VS Code gives me a clean, flexible editor with just enough features without feeling heavy. I use it primarily for Python scripting, small utilities, and workflow automation. The built‑in terminal and extensions make it easy to stay focused.
2. Double Commander
A dual-pane file manager that speeds up everything from folder cleanup to bulk renaming. It’s lightweight, predictable, and perfect for navigating large directory structures without getting lost.
3. WinMerge
My go-to tool for comparing files and folders. I use it for diffing scripts, checking changes, and merging updates. It’s simple, visual, and does exactly what I need without extra noise.
4. Everything
A lightning-fast search tool for Windows. If I need to find a file anywhere on my system, Everything gets me there instantly. It’s one of those utilities you don’t realise you rely on until you use someone else’s machine.
5. Trello
I use Trello to keep track of tasks, ideas, and small project plans. It’s visual, easy to reorganise, and works well for both personal planning and client work.
6. Vivaldi
My daily browser. I like its customisation options and the way it handles tab management. It’s flexible enough to adapt to how I browse rather than forcing a fixed workflow.
7. GitHub
Where I store my code, track changes, and keep small projects organised. I use it for version control, documentation, and sharing work with clients or collaborators.
8. Copilot & ChatGPT
I use Co-Pilot and ChatGPT for brainstorming, drafting ideas, and exploring solutions. It’s great for getting unstuck or thinking through a problem from a different angle. It’s not a replacement for thinking - just helpful assistants.
Final Thoughts
These tools aren’t a “perfect stack” - they’re simply what fits my workflow right now. Your setup might look completely different, and that’s the beauty of development: we all build our own toolkit.
If you want to share your own favourites, I’d love to hear about them.
Top comments (0)