PWV Portfolio Feed

Happy Monday.

Is adding a cookie banner still on your to-do list? 👀

those 1,000 hours taught me exactly what developers touch a hundred times a day, which turns out to be exactly the knowledge you need to design what comes after it.

i've never been more excited to build.

there's something very funny about the guy who built his career teaching editor mastery now building the thing that retires most of it. no regrets.

it ends somewhere much weirder.

the cli is the right first move. it's raw and native. it won't be beat. the agent should live on your machine, or in a sandbox, with your env, your repo, your private context, at least in this slow-takeoff world of jagged capabilities. but the terminal is where this paradigm starts.

3. the autonomy and human elements. how much do i want to steer right now: approve every tool call, or only review the final diff. the gui's job is making delegation legible. what did the agent do, why, and where should i look.

2. it'll be generated on demand. a refactor wants a different surface than a debugging session, which wants a different surface than a security review. the ui should rebuild itself around the task at hand instead of shoving everything through one chat box.

1. it'll be visual. vision is the 10-lane highway into the brain. diffs, dependency graphs, test matrices want to be seen. reading them line by line out of a scrollback buffer is brutal. watching an agent work should feel like watching a build pipeline. right now it feels like tailing a log file.

the gui for this new computer hasn't been invented yet. like anything, i wanna take a shot at this. i'm going to translate my entire shipsheet workflow into our upcoming gui.

i think some of its properties can already be predicted:

the part i can't stop thinking about: the agent interface is still primitive. chatting with a coding agent in a terminal feels like using an 80s computer console. text in, text out, scroll forever.

context engineering > keybinding engineering. reading code > writing code.

how fast can i review code and understand what's changing is the bottle neck now. not my snippets or multi cursor hacks.

i run Command Code now (3rd largest coding agent in the world) and my whole setup is a terminal, an agent, and taste. the scarce skill moved up the stack: from "how fast can you edit a buffer" to "how precisely can you specify intent and verify the result."

every one of them existed to speed up human-typed code. emmet expanded your html. linters caught your typos. gitlens prettied up your blame. snippets, keybindings, macros, all of it sanded down the keystroke.

then agents deleted the keystrokes. and more i guess.

the extensions are fine. the job they were installed for is just gone.

i hardly need snippets, or weird shortcut shenanigans, debugging is more hard core now then stepping over/in to code, Command Code writes scripts and wires itself in there, reads logs, and verifies everything for me.