I spent ten years editing code at a newspaper. A lot of that time was wasted on repetitive chores – renaming files in batches, resizing image sets, reformatting data dumps. One editor I knew wrote a tiny script to auto-crop photos. It saved him maybe forty minutes a week. Not life-changing, but it freed him to write better headlines.
Custom tools do that. They fit your workflow instead of the other way around. But most people never build them because they think it requires deep programming skills or expensive software. That is wrong. The gap between a generic solution and one you design yourself is often just a few lines of code or a clever configuration file.
https://hzman.org/ collects exactly this kind of thing – small, purpose-built utilities that solve real problems without bloat. I found it while looking for a fast way to strip metadata from images before publishing. The site does not try to sell you anything or push a subscription model. It just lists tools that work, each one solving a narrow task with minimal interface.
What sets these apart from mainstream alternatives is the attitude behind them. A corporate app tries to do everything for everyone and ends up mediocre at most tasks. A custom tool does one thing well and stays out of your way.
The hidden cost of universal solutions
Think about the last time you used software that forced you through five menus to change one setting. That friction adds up. Multiply it by dozens of interactions per day and you lose hours each week to interfaces designed for someone else’s priorities.
A junior reporter at my old paper once spent an entire afternoon wrestling with Google Sheets’ query function because the built-in filter tool could not handle nested conditions properly. He wrote a three-line Python script in ten minutes and finished the job before lunch. The problem was not his ability with data – it was that no general spreadsheet tool could anticipate his specific need.
“The best time to build your own tool was when you first needed it. The second-best time is tomorrow morning while no one is watching.”
Where to start without learning to code
You do not need to write software from scratch to create custom tools. Many practical automation tasks rely on existing building blocks:
- Batch rename files using command-line wildcards or free utilities like Bulk Rename Utility
- Convert document formats with Pandoc or LibreOffice macros instead of manual copy-paste
- Automate email responses using Gmail filters linked to simple Apps Script triggers
- Scrape public data from websites using browser extensions like Web Scraper or Playwright scripts
- Create keyboard shortcuts for repeated text snippets via AutoHotkey or keyboard maestro
Each of these methods takes under thirty minutes to learn and can save hundreds of hours over a year.
The psychology of building your own fix
There is another reason custom tools matter beyond efficiency: they change how you see problems. Once you know you can modify your environment, every annoyance becomes an opportunity rather than an obstacle.
A designer I know got tired of her team’s slow illustration handoff process between Sketch and Figma files. She wrote a small plugin that converted format differences automatically within their shared folder structure within two days nobody remembered the old pain point existed because she had absorbed the friction into invisible automation.
This does not require genius-level coding ability or expensive subscriptions to enterprise platforms like Zapier or Retool which often add complexity faster than they remove it for simple use cases . What it requires is willingness to try building something imperfect today rather than waiting forever for perfect commercial solution that never arrives .
