Colophon
I built this site.
Not as a portfolio piece for a career in software. I am not trying to become a developer. As evidence of how I work.
Back- Why build it myself instead of using a template?
- A template would prove nothing. When I need a tool that does not exist I go and make one, and that is the same habit that turns a messy handover into a tracker.
- Did you use AI to build it?
- Yes, heavily, and I would rather say so than have you assume otherwise. I decided what this had to say and who it was for; Claude handled the parts I do not know how to type. That is exactly how I use it at work.
- What is it made of?
- Next.js and React for the pages, Tailwind for the styling, Motion, GSAP and Lenis for the movement. Every page is prebuilt HTML: nothing is assembled while you wait, and the only thing the server keeps is the count in the last answer here.
- Are these real client documents?
- The paper is not, and never will be: the transcript, the minutes and the handover print are reconstructions with invented names and figures. The screenshots are the opposite, real captures of software I built, with any staff names redacted before the file went into the repository. The employers, dates and titles are the ones on my resume.
- What did you deliberately leave out?
- Numbers I cannot source, testimonials, and any third-party script. The last one is enforced rather than promised: this site's own content security policy blocks every outbound connection, so there is nothing here that could report to anyone.
- Am I being counted?
- Yes, by this site and by nothing else: the server adds one to a file it keeps itself, with the page, the country, the browser and the site you arrived from. It sets no cookie, and it stores no address it could trace back to you.