Skip to content
AJ

02·2001 → 2026 · Chapter 02

Every chapter
solved a
bigger problem.

Technologies expired. The problems didn't. Each chapter carries an artifact, the tech that defined it, the lesson it taught, and the mindset it forged.
  1. Illustration of a beige CRT monitor on a small stand, its screen showing a simple pink browser window with the word HTML, representing the very first web page built in 2001.
    01 · First website · HTML
    Ch. 012001

    First Website

    Curious teenager

    The problem: I wanted something that didn't exist yet, so I built it. A page on the open web, hand-typed, no permission needed.

    What I learned

    The call was to publish before I felt ready. That instinct, ship, then improve, never left.

    Mindset forged

    Curiosity as an operating system. The compounding advantage that outlasts every framework.

    Tech

    GeoCitiesHTML

    → The web became the medium. Craft became the next problem.

  2. Illustration of a creative technologist's toolkit: a graphics tablet with color wheel and stylus, a 3D wireframe cube, and an After Effects motion timeline, representing design, motion, and 3D craft.
    02 · Design + motion + 3D
    Ch. 022006–2010

    Creative Technologist

    Design + motion

    The problem: interfaces felt lifeless. Static comps couldn't answer how an experience should feel in motion.

    What I learned

    The call was to treat design and code as one discipline, every pixel, easing curve, and frame a decision, not a default.

    Mindset forged

    Taste as a skill. The belief that rhythm, weight, and restraint are engineering choices, not decoration.

    Tech

    DreamweaverFlashActionScriptPhotoshopIllustratorAfter EffectsCinema 4D

    → Craft opened the door to client work, and the harder problem of owning outcomes end-to-end.

  3. Illustration of an independent design studio desk: stacked brand identity samples, an open magazine of logo studies, a brand mark on a display podium, and a laptop showing a website mockup, representing running a full-service studio.
    03 · Independent studio
    Ch. 032010–2015

    Founder, RealiDreams

    Independent studio

    The problem: clients didn't need a deliverable, they needed a result. Nobody was coming to bridge the gap between what they asked for and what would actually work.

    What I learned

    The call was to start with the business outcome and reason backward to the artifact. Scope, price, and say no on my own signature.

    Mindset forged

    Ownership. Product thinking begins with the client's business, not the file you're about to open.

    Tech

    BrandingWebMotion3DPrint

    → Running the studio revealed the ceiling of solo work, and the leverage of shipping inside a team.

  4. Illustration of a laptop screen displaying a marketing campaign dashboard with a rising conversion chart and upward gold arrow, representing web work that improved conversion for agency clients.
    04 · Marketing → conversion
    Ch. 042015–2016

    Caldwell & Kerr

    Designer → Senior Frontend Web Developer

    The problem: automotive campaigns shipped weekly, with real ad spend and real deadlines. Perfection was a luxury nobody paid for.

    What I learned

    The call was to trade artisan pace for repeatable velocity, templates, patterns, and disciplined tradeoffs a team could inherit.

    Mindset forged

    Attention as a system. Visual hierarchy and conversion literacy every interface engineer needs before they touch a component library.

    Tech

    HTMLCSSJavaScriptPHPWordPressCoda

    → Agency cadence prepared me for owning long-lived codebases at CMS scale.

  5. Illustration of modular content blocks and a cursor assembling them into a page frame, next to a rendered CMS preview, representing modular content management systems built for editors.
    05 · Modular CMS systems
    Ch. 052016–2020

    Priority Marketing

    Web Developer, CMS specialist

    The problem: fifty-plus sites, each with its own editor, each needing to survive years of hand-off, plugin churn, and content the client hadn't written yet.

    What I learned

    The call was to build for the second engineer and the third editor, conventions, guardrails, and predictable seams over clever one-offs.

    Mindset forged

    Systems built for other humans. The seed of every design system I've touched since.

    Tech

    PHPWordPressHTMLCSSJavaScriptApacheGSAPSEO

    → Volume and accountability set the stage for product engineering with real state.

  6. Illustration of a small bank vault marked with a gold shield, a padlock, stacks of gold coins, and a secure transaction card, representing engineering for a regulated fintech product.
    06 · Fintech · trust & rigor
    Ch. 062020–2022

    Midland Trust

    Software Engineer, Fintech

    The problem: client, payment, and pro portals had to move real money and hold real trust, across auth boundaries, regulated workflows, and Salesforce integrations that could not be papered over on the client.

    What I learned

    The call was to design the data shape and API contracts first, then the interface. Every state, error, and edge case is a promise to the user.

    Mindset forged

    Regulated-industry rigor. Full-stack judgment, database, service, UI, treated as one decision.

    Tech

    ReactTypeScriptPostgreSQLSequelizeExpressIonicSalesforce

    → End-to-end product engineering readied me for systems that multiply other teams.

  7. Illustration of a central gold design-token coin with thin lines radiating out to surrounding UI components: a button, a toggle, an input, and a card, representing the Legato enterprise design system.
    07 · Enterprise design system
    Ch. 072022–2026

    CDW, Legato Design System

    Senior Software Engineer I / Technical Lead

    The problem: ten-plus product teams, fifteen-plus enterprise apps, each drifting toward its own vocabulary. Every diverging button was a tax on every future decision.

    What I learned

    The call was to treat the system as a product with its own users, engineers, designers, PMs, and lower ambiguity as a measurable outcome. Tokens, accessibility, and docs as first-class API surface.

    Mindset forged

    Leverage at scale. When the system answers a question once, ten teams stop asking it. Judgment compounds.

    Tech

    ReactTypeScriptStencilWeb ComponentsStorybookNxDesign TokensA11y

    → Fortune 500 depth plus AI-assisted workflows shaped what I'm building next.

  8. Illustration of an engineer's workstation with two laptops and a monitor, a glowing AI knowledge-orb hovering above with two agent nodes orbiting it, representing today's AI-assisted engineering practice.
    08 · AI-assisted engineering
    Ch. 082026

    Now

    Staff / Principal engineering roles

    The problem worth solving now: full product lifecycle, architecture, backend seams, product surface, accelerated by AI without ceding judgment to it.

    What I learned

    The call is to treat AI as leverage, not authorship. Widen the surface I can hold; keep the last read before ship human.

    Mindset forged

    Engineering judgment as the axis. Technologies expire. Problems, and the taste to choose which ones, do not.

    Tech

    MCPClaudeChatGPTCopilotReactTypeScript

    → The next chapter is being written, by design.