audits.md brutal.md git.md insights.md logs.md plans.md study.md
```javascript/** * ============================================== * @file brutal.md - brutal scorecard template * ============================================== * @description * - tracked in git, one brutal file per day, appended across runs * - scrub client names, tokens, and other sensitive detail before it lands in a commit * - written by `@gitbrutal` only, appended each run, many scorecards per file * - `scorecards` capture the doc-vs-reality gap at a moment in time, never edited after the fact * - `grades` are A-F per lane; strong infra grades CANNOT mask weak app/test ones * - `lines` should contain a single clause/fact/action, limited to 100 characters * - name specific files, claims, and commits; an unfalsifiable criticism is worthless * - skip the raw telemetry dump; keep the read of it, not the printout * - never soften a written scorecard, and never re-grade an older one to match a newer mood * - grade drift across dated files is the point; a lane stuck at D is the signal * @see AGENTS.md, AGENTS/git/gitbrutal.md, docs/brutal/ */```# docs/brutal/YYYY-MM-DD.md## Brutal #1: YYYY-MM-DD HH:MM### reality checkeach documented claim, followed by what the telemetry actually shows:- [claim from docs]: [harsh reality]*example:*> README claims "strict commit types": 31 of the last 100 commits are bare `update`> AGENTS.md claims hooks are tested: zero test files touch `AGENTS/hooks/`### effort vs outputwhere the time actually went, in one or two lines*example:*> 4 days and 30 commits on github actions, 2 hours on the ui components anyone will see### risk & maintenance trapsspecific files, ignored rules, or architectural landmines*example:*> `gitbrutal.sh` greps `content/**` for mirrors, a path that no longer exists> 6 unresolved TODOs, oldest is 41 days### grades- **infra/tooling:** A-F- **app/features:** A-F- **tests/reality:** A-F**verdict:** one unapologetic sentence on the actual state of the codebase*example:*> **verdict:** an immaculate build system wrapped around software nobody has proven works## Brutal #2: repeat the above format for each `@gitbrutal` run on the same daynever edit an earlier scorecard; a grade that has not moved in a week is the finding

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.