Start with structure
Understand the problem properly and plan the solution before building. Choose the simplest approach that works. If a plugin covers it, use it. If it doesn't, build exactly what's needed.
About me
I'm Damone Hartnick, a developer based in Cape Town. I build custom systems, reporting and business tools, and I look after the IT side of the businesses I work with.
I like fixing real problems. Most of my work is taking something messy, like a slow report, a clunky process or a system nobody fully trusts, and turning it into something people can rely on. I ask a lot of questions and never take the first answer for granted, whether it comes from a tool, a colleague or myself.
The biggest growth in my career came when I took over a live multivendor WooCommerce store. For about eight months I was the only developer on it. Management gave me direction and priorities, but when something broke, fixing it was down to me. So I learned the whole platform: the front end and user experience, the back-end PHP and database work, and the testing. I tested everything I built before release, checking results against SQL queries and exports, and I kept markdown documentation for every change, so I always know where to look and my AI tools have the context they need.
That role taught me as much about people as about code. I document every issue, explain it to management in plain language, and train the sellers who use the system, so they're comfortable with the interface and know what to do when something looks wrong. I went from building features to owning the outcome.I'm a different developer because of it.
When there's a problem, I don't stop at a workaround. I stay with it until I understand the cause and have a fix I trust. I've also learned that pushing through without rest has a cost, so now I step back when I'm stuck, go for a walk, and return with a clearer head. It's usually the fastest way to the answer.
I believe people understand things better when they can see them. I always start with documentation, then turn it into diagrams and mockups so everyone can see how a system will work before it's built. It's like cooking: a recipe lists what goes in, but a picture of the finished cake shows what you're aiming for. I love cooking, and I bring the same habit to every project.
Outside of work, I'm a runner. It has taught me patience and honest self-assessment. Progress comes from showing up, and when a race doesn't go to plan, I work out why, adjust and go again. I try to bring that attitude to everything: stay positive, stay curious, and don't take setbacks personally.
Connect on LinkedInI take responsibility for a system from requirements through to ongoing support. I don't wait to be told what to fix. I find the cause and act.
I explain technical issues in plain language to management and train the people who use the systems, so they feel confident, not confused.
I've picked up new platforms quickly, across Microsoft 365, the Power Platform, and custom PHP on WordPress and WooCommerce, and I keep going deeper. I built this portfolio from scratch in Astro, a stack I'd never used before. I also want to learn more about how the body trains, to become a better runner and a better person.
I trace issues to the root cause, from the code to the database, and check the fix against real data before calling it done.
Clear workflows, markdown documentation and solutions that are easy to maintain and hand over. I use AI tools, but with proper structure and understanding. Without that, AI hallucinates and the result won't hold up.
I'd say I'm an above-average runner, working towards a sub-20 5km and a sub-1:40 half marathon. In 2027, I'm taking on my first full marathon.
My approach
These are the principles I use when I learn, solve problems and build systems. They apply whether I'm writing code, setting up infrastructure or training for a race.
Understand the problem properly and plan the solution before building. Choose the simplest approach that works. If a plugin covers it, use it. If it doesn't, build exactly what's needed.
Document everything, then turn it into diagrams and mockups. When people can see what's being built, they understand it faster and catch problems earlier.
Take responsibility for a system from the first requirement to the last bug fix, including testing, documentation and support.
A solution only works if people understand it. I explain issues clearly to management and train users so they feel confident.
Tools are only as good as the person using them. AI will do almost anything you ask, but without understanding and structure, the result won't hold up.
Learn from testing, feedback and mistakes. And step back when you're stuck, because a clear head solves problems faster than force.

Diploma: ICT Application Development
2020 – 2022

Higher Certificate: Information And Communication Technology
2019

Secondary education
2016–2018
Mar 2024 – Present
Cape Town, Western Cape, South Africa · On-site
I develop and support business systems across Microsoft 365, WordPress and WooCommerce, and the Power Platform. I work from the first requirements through documentation, build, testing and ongoing support, and I'm the person users and management turn to when something needs fixing, explaining or training.
Feb 2023 – Mar 2024
Cape Town, Western Cape, South Africa · On-site
Provided customer-facing technical support, device setup and troubleshooting.