Chrome & Burger
A full-stack database assessment: one live menu, sourced from two different databases at once, to see the same data modelled two ways.





Practice
Selected Work is what shipped. This is where it came from — a database assessment with two backends, a pixel-matched clone, a DOM clicker, a live API pull, a product page for my own bike, a café-discovery concept, a terminal game, and a team booking flow still in draft. Not production work. Practice, on purpose.
A full-stack database assessment: one live menu, sourced from two different databases at once, to see the same data modelled two ways.





A pixel-matched front-end clone exercise — reproducing a real design's typography, spacing and layout instead of inventing my own.





A Specialized S-Works product page, built from scratch — because I ride, and wanted to see if I could design for it: feature copy, spec breakdowns, a pricing grid.





A DOM-manipulation exercise that turned into an idle clicker — upgrades, an auto-clicker, and a character I drew myself standing in for the "click me" target.





One button, one live call to PokéAPI — pulls a random Pokémon's sprite, name and type every time, and keeps every card you've drawn on screen.





A café-discovery concept that started as a week-three e-commerce exercise and ended up somewhere else entirely: a taste-matching engine, a filterable café list, and editorial copy written to sound like a real product.





A classic terminal exercise — a 2D field, hidden holes, one hat, and a class written to explain its own reasoning in comments as it goes.





A team project, Sprint 2, still a working draft — a luxury travel-booking flow for Thailand. Search, a filtered listing, a property page with live pricing, and a full booking journey through to a confirmed reservation.




