Colophon
I built this site.
Not as a portfolio piece for a career in software. I am not changing jobs. As evidence of how I work: I would rather build the thing than wait for someone to build it for me.
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 for the movement. It is static, so there is no database and nothing to break at 3am.
- Where did the interactive demos go?
- There were several: a calendar you could rearrange, a contract packet, a board that sorted itself. They went as the site got shorter, because the work it points at is the better demonstration. The transcript that condenses into minutes stayed.
- Are these real client documents?
- No, and they never will be. Every document here is a reconstruction with invented names and figures; the employers, dates and job titles are real and checkable.
- What did you deliberately leave out?
- Numbers I cannot source, testimonials, and any third-party script. The last is enforced rather than promised: this site's own content security policy blocks every outbound connection, so there is no analytics and no cookie banner.