Without markata-go’s web awesome integration, the above would look like:
<scripttype="module">import'https://ka-f.webawesome.com/[email protected]/components/comparison/comparison.js';</script><wa-comparison><imgslot="before"src="https://dropper.waylonwalker.com/file/d628ffba-de18-4fff-91a8-700f037df119.webp"alt="Grayscale version of kittens in a basket looking around."/><imgslot="after"src="https://dropper.waylonwalker.com/file/ca30665f-1a15-453e-aab8-221901c7df99.webp"alt="Color version of kittens in a basket looking around."/></wa-comparison>
Today I found a way to test model syntax, cause the clankers always get the
exact model name that copilot wants wrong.
copilot --model claude-sonnet-4.5 -p "Reply with OK" --allow-all --no-ask-user -s
copilot --model gpt-5.4 -p "Reply with OK" --allow-all --no-ask-user -s
Jaime’s title hooked me in here, what guitar riff from Linkin Park had the greatest riff of our generation. Theres something about Linkin Park unlike Killswitch Engage, Atreyu, Avenged Sevenfold, bands I would listen to at this time that I cant remember a single riff, I can think of Chesters vocals, or the unique scratching they did, but mostly the songs were a whole piece. What riff is he talking about. The very first note of “One Step Closer” plays and I’m immediately transported back to 2003 sitting in my garage watching HuevosIII on repeat. I can still remember the timing that Wes Miller did on the edit. I can see the riders I looked up to for so long riding in formation. Turns out this riff is so recognizable it takes me exactly where I was when I listened to it hundreds of times.
A cozy blend of work tools and thoughtful mementos, reminding me of good people and moments.
Do you ever vibe code out a POC, and you can just feel the shitty code
underneath? Every change causes 3 things to break and wires get crossed all
over the place. Sometimes I just want to write the code again. Maybe its time
to slow down.
Hot take, if you are unwilling to approve rm you should rethink
your workflow, git state, or backups.
!!! Note
This is meant for normal project work with an agent working in
the context of a single project, with directory level access
to the project.
When you reach that f-it moment and screw your carpet to the floor
I'm regressing back to boomer ai for more plan mode style prompting at home...
It does a decent job at ingesting a repo and coming up with plans before I
start spending precious tokens.
Not sure if this is simply the flavor of the month, or a shift in gpt5.4
being super subsidized on release and now that we have gpt5.4-mini-fast out
they have shifted, but I'm burning through half of my $20 gippity sub in a
day with hobby level use. Second week in a row its burning so fast.
Stow comes with a local and global ignore list that you can use to ignore
certain files or directories.
If you put Perl regular expressions, one per line, in a .stow-local-ignore
file within any top level package directory, in which case any file or
directory within that package matching any of these regular expressions will
be ignored. In the absence of this package-specific ignore list, Stow will
instead use the contents of ~/.stow-global-ignore, if it exists. If neither
the package-local or global ignore list exist, Stow will use its own built-in
default ignore list, which serves as a useful example of the format of these
ignore list files:
Casey had an interesting point here. I think demitri came back with some sense of sanity that its just not how corporations look at employee cost, but I still thought it was a head scratcher. Roughly translated not quoted If the sellers of ai are telling you that your developers are going to be 10x productive, why are they only spending half their salary in tokens? Why not 9x?
I hate how he called out terminal user interfaces as shit… then proved web interfaces to be superior. Damn him. I love working from my terminal, but having ai prove itself through html reports including video, image, metrics, charts, and text is goated. Rethinking yourself has the bottleneck not the orchestrator feels real. Validating the work is hard, theres a shift right now and everyone is trying to figure it out. Lucas’s technique is a little bit of be lazy and tell it to prove itself to you, so as you juggle your 15 agents you have a nice report to read.
This is a really good guide, with quite a few good nuggets. I need to try deleting my AGENTS.md and rebuilding it from scratch more often. I liked how he talked about having agents prove their work and tell them up front how they will be judged. What I didn’t care for so much was the feeling that a lot of the rules go in markdown, thats not a rule, thats a suggestion. Rules should be deterministic. They should be tests and linters that ensure they are followed. Suggestions are good, but dont trust the agents to always follow them. And don’t trust that they wont change your rules, keep them honest.
Write It First, Then Let AI Drive There's a thing that happens when you start using AI coding tools seriously. You assume the best workflow is obvious: let AI generate the first draft, then... Kenneth Reitz · kennethreitz.org Interesting take by Kenneth Reitz. Not quite sure how I feel about it anymore. It kinda hurts, but I’m not sure if code aesthetics matter as much as the product anymore. I cared when I was the one editing, but at this point I’m not doing a lot of edits by hand. Do these aesthetics affect the final products that users use, Not sure. AI makes me sad.
ThePrimeagen (@ThePrimeagen) on X I am slowly coming around to AI assisted programming. I am genuinely trying to codify every rule about programming that I have and using that + several stages to build out small changes. Not s… X (formerly Twitter) · x.com If agents make prime a bit faster, what does that mean for the rest of us mortals?
