A developer who cares how things work underneath.

My story

I started with simple web pages and kept going: first the interface, then the server behind it, then the database, then getting it all online reliably. Learning in that order taught me that good software is mostly about the boundaries between parts, such as what the browser sends, what the server trusts, and what gets stored.

I build real products rather than only exercises, and I learn from what breaks. That habit is the reason this site includes a practical development guide: explaining something clearly is the quickest test of whether I understand it.

How I work

• Clarity first. I agree on scope in plain language before writing code.
• Security by default. Validate input, protect secrets, keep dependencies lean.
• Performance as a feature. Small pages, optimised assets, CDN delivery.
• Maintainable code. Readable structure so the next change is easy, whoever makes it.

Skills

• JavaScript and Python for front-end, back-end and automation
• HTML and CSS with a focus on semantic markup and accessibility
• REST APIs, authentication and database design
• Git workflows and deployment on modern hosting platforms

Where I am heading

I want to keep building useful, dependable products for the web and to make the process of building them easier to understand for people starting out.