Start with the problem.
The most useful tools begin with something that gets in the way. A question people keep asking. A manual task that keeps coming back. Information that takes too long to find.
THE PERSON BEHIND THE PROJECTS
A little
context.
I’m Scott Hudson.
I work with networks and build practical software. I’m interested in the point where infrastructure, automation and everyday problems meet — and where a useful tool can make someone’s day a little easier.
This site brings that work together: the projects I’m building, the systems behind them, and the things I learn along the way.
Gold Coast, Australia
NETWORKSAUTOMATIONPRACTICAL SOFTWARECONTINUOUS LEARNING
01 / FOCUS
Tools with a reason to exist.
Some problems are small enough to become part of the routine. Finding out where a colleague is. Digging through call records. Repeating the same checks because the information is scattered.
Those are the kinds of problems I like working on. Take something that costs time or creates friction, understand how people deal with it, then build a clearer way through.
- NETWORKS & SYSTEMS
- The infrastructure that connects people, applications and information.
- AUTOMATION & TOOLS
- Less repetitive work. Better access to the information that matters.
- SOFTWARE & INTERFACES
- Practical applications that are clear to use and manageable to run.
02 / IN PRACTICE
Two problems. Two projects.
PEOPLE / PRESENCE
Attendr.
“Where is everyone?”
A shared presence board that brings staff status, location and return times together. Built to run on an organisation’s own network.
EXPLORE ATTENDRVOICE / VISIBILITY
CDR Search Tool.
“Can we find that call?”
A local tool for receiving, searching and reporting on Cisco CUCM call records, so useful information is easier to reach.
EXPLORE CDR SEARCH TOOL03 / APPROACH
How I think about building.
Make it useful in practice.
A feature only helps if someone can use it. Clear interfaces, sensible defaults and straightforward documentation matter as much as the code behind them.
Think past the first run.
Getting something to start is one part of the job. Installation, configuration, updates, troubleshooting and recovery all belong in the design.
Keep improving it.
Build, learn, improve, repeat. Test the details, listen to the people using it, and take the time to finish the things that make a tool dependable.
ABOUT THIS LITTLE CORNER OF THE WEB
A home for the work.
The network map on the homepage is a nod to the systems I work with. Each connection leads to another part of that work. Context is this one: a little about the person behind it.
Have a look around. The projects are a good place to start.
BACK TO THE MAP