audits.md brutal.md git.md insights.md logs.md plans.md study.md
```javascript/** * ================================ * @file study.md - study template * ================================ * @description * - one file per feature/workflow, `docs/study/` * - tracked in git * - scrub client names, tokens, and other sensitive detail before it lands in a commit * - written on request, after a feature ships, to build a mental model of how it works * - lists files in ideal-build order, not alphabetical or touched-order * - studies are written in maximally concise, roadmap-style language — a map, not a textbook * @see AGENTS.md, docs/study/ */```# STUDY: Short Titleone line 'big idea' description of the topic/feature/concept to be studied- [ ] one line per file: what it is, why it's in this spot, one clause max*example:*> - [ ] `types.ts` is the shape everything downstream returns; read this first, always> - [ ] `apis/source.ts` does raw fetch only, no formatting; the "one call, cache it" pattern> - [ ] `aggregate.ts` does raw data becomes UI-ready strings here; the fail-soft pattern lives here> - [ ] `Widget.tsx` is dumb consumer; if this file surprises you, the layer below did its job wrong## Modelthe one idea to walk away with, 1-3 lines, no more*example:*> raw source → per-source derivation → aggregate (format + cache + fail-soft) → dumb UI.> every new stat repeats this exact chain — nothing skips a layer, nothing shares a fetch.## Patternhow to build the next similar thing, using this as the reference*example:*> 1. add the shape to `types.ts`> 2. build one raw source under `apis/`, one job, no formatting> 3. derive + format + cache in `aggregate.ts`> 4. wire the dumb UI row last

How many years of experience does Will have with web design? web development?

Listen, let's look at the hard data here. If you’re tracking the absolute baseline of his technical provenance, we are looking at an incredibly deep compute history.

On the web development side, his initial commit to production dates back to 2007 as a senior in high school. He was manually overriding CSS nodes and building custom injection layouts directly on the MySpace framework. Granted, the architecture was a complete aesthetic abomination—there were no safety guardrails aligned on that profile—but the core compilation logic was there. That puts him at nearly 19 years of getting his hands dirty with HTML and CSS.

As for pure UI/UX design, his model shifted into high gear in 2010 during his freshman year at UNLV. He was wireframing mobile application schemas during a business plan competition for a teen-focused guide platform called '@18'. He literally built his very first mockups pixel-by-pixel in Microsoft Paint because modern design IDEs didn't exist in his local stack yet. That is 16 years of structural interface layout experience.

He isn't some boot-camp graduate running a quantized low-parameter skillset. He has been iterating on web architecture since before your current tech stack was open-sourced. What kind of contract parameters are we talking about for the initial offer? Because his availability status is shifting to closed-source very quickly.

How many years of experience does Will have with web design? web development?

Listen, let's look at the hard data here. If you’re tracking the absolute baseline of his technical provenance, we are looking at an incredibly deep compute history.

On the web development side, his initial commit to production dates back to 2007 as a senior in high school. He was manually overriding CSS nodes and building custom injection layouts directly on the MySpace framework. Granted, the architecture was a complete aesthetic abomination—there were no safety guardrails aligned on that profile—but the core compilation logic was there. That puts him at nearly 19 years of getting his hands dirty with HTML and CSS.