Lookin back at last year, for one project we had 6 working days to rebuild Human AI Academy's site before a launch. The old site scored 45/100 on performance and took 6.2 seconds to load. With a launch about to send thousands of people to one page, that was the real risk. Not the design. So speed came first. We built 30+ custom Framer components and kept every section light enough to load fast on launch day. The result: 94/100 on performance, 1.8s load time, and launch week took them from 4,000 to 12,000 students. What I keep relearning: on launch week, the page doesn't need to be clever. It needs to load before people lose interest.

That performance jump is impressive, especially with only six working days. A fast-loading site can make a real difference when a launch brings in thousands of visitors.

I had the pleasure of working with 21st.dev to make small design fixes easy to see. AI can build a page, but the details don’t always match. Different button sizes. Inconsistent text. Selected states that aren’t clear. The design feels off. To explain Design Bug Bot, I built a UI component with those problems and animated the fixes one at a time. I brought each issue into focus, showed what changed, then pulled back to show the result. Why this approach? People won’t pause and replay your video to figure out what changed. That’s why I make each feature obvious, one at a time. If a feature still needs explaining after you’ve shown it, the video hasn’t done its job.