I am…

A trusted digital partner

I love a twisty technical challenge (type 2 fun ftw!) and love partnering with forward-thinking people to deliver high-impact tech.

Open, transparent, honest

I believe that openness, transparency and honesty are essentials to doing good work.

Let’s collaborate,
or just say hi!

Index

28 August, 2025 – 4 min read

My philosophy for building things

Written by Shaun Jenkins

Building good software is hard. Over the years, I’ve collected a set of principles and reminders that help guide my work. They’re not hard and fast rules, just notes I keep for myself to try and build better things and stay sane while doing it. Maybe some of them will be useful to you too.

1. Design & User Experience

• Guide users; don’t disorientate them. Make it obvious where the user is and what comes next. A good interface creates an intuitive and logical path for the user to follow.
• Solve for the user. Don’t confuse technical elegance with user value. Debates about the ‘correct’ architecture or tool are secondary. A user never sees your code; they only feel the result. Measure your work by how well it solves their problem.
• Performance > Superfluous stuff. Every time. People want to get things done quickly, not sit around waiting for an irrelevant animation to finish.
• Accessibility matters. Designing for accessibility often has benefits for everyone (e.g., big buttons, clear contrast, generous spacing).
• Creative solutions > Overtly technical ones. The best solution is often the one that feels simplest to the user, not the one that uses the most complex technology.

2. Code & Craft

• Stand on your own shoulders. Reuse your own proven code and components. It saves time and lets you build on a solid foundation that you understand inside and out.
• Write reusable code. Always be thinking, “I might need this for something else later.” Name things clearly, spin logic out into functions and methods, and use classes well.
• Aim for general but specific. Build things that are specific enough to be useful now, but general enough that they can be adapted for another purpose later without a complete rewrite.
• Build for adaptability. Avoid making architectural choices that are so rigid you can’t adapt or change direction later without a massive, painful effort.

3. Mindset & Philosophy

• Be bold. A bold vision provides a clear goal you’re working towards. This builds morale and momentum, making your team ready and willing to take on the curveballs that will inevitably come your way. It’s what makes you happy to work a little extra, because you’re passionate about what you’re creating.
• Don’t box yourself in. It’s easy to convince yourself there are only one or two ways to solve a problem (X or Y). In reality, there are often many more options (A, B, C, D…). Be careful not to mentally build the walls of a box that you then can’t escape.
• Think long-term. Aim to build things that are designed to stand the test of time, not just solve today’s immediate problem.
• Never compromise on quality. Negotiate on features, timelines and scope – but the quality of what you actually deliver should be non-negotiable.
• Steal like an artist^[1]. Understand, learn from, and be inspired by the good ideas of others, then combine and remix them into your own work.

4. Awareness & Execution

• Tackle problem-solving disorientation. When solving a tough problem, it’s incredibly easy to get lost. Take notes. Be methodical. If things aren’t making sense, it might be because there’s more than one issue happening at once.
• Open your eyes. You can’t fix what you can’t see. Use your debugging tools religiously: error logs, var_dump, print_r, console.log.
• Know how problems present. Be vigilant. A critical issue rarely announces itself clearly. It usually looks like something else: “not enough time to do the work”, “important design considerations yet to be figured out”, or “a lack of clarity around who’s doing what”. These are often symptoms of a deeper problem.
• Control what you can control. Focus your energy on the parts of the project and process that you have influence over.
• Build, get feedback, iterate, improve, repeat. That’s how good things get made.

Just some principles I try to follow. It’s all an ongoing process.

^[1] From the book Steal Like an Artist: 10 Things Nobody Told You About Being Creative by Austin Kleon.