@ThePrimeagen You don't need CSS for a beautiful html. motherfuckingwebsite.com

discovering basic web dev from first principals

@antoinecojp @mattpocockuk The flow seems similar to forking a session, then either summarizing or compacting that fork and re-ingesting back into the 'parent' session.

@mattpocockuk Im not familiar with CC. (I use OpenCode) But how do you summarize the prototyping if you’ve already rewinded to the question?

A flow I just tried and LOVED: 1. /grill-with-docs, talking about a new bit of UI 2. Asks me a question I can't answer unless I prototype 3. /prototype 4. Iterate on the prototype, burning tokens freely until we get a good spot 5. /rewind to the question, and select 'summarize' (Claude Code feature), saying 'summarize what we learned from prototyping' 6. Continue the grilling session, retaining the prototype Smoooooooth

@kentcdodds I'm maxing onto adaptability. Long held ritualistic patterns are drying up. If the only constant is change, then my staying power relies on flexibility. I know how good programs work, and I know I don't know a lot. This won't change. So I focus on idea communication.

If you voted Yes, Yes, what value is there in spending a bunch of energy maxing on your workflow if you expect it to require changing so soon?

I have two questions about how you develop software. 1. Is your workflow today significantly different from 6 months ago 2. Do you think your workflow in 6 months will be significantly different from it is today?

In 2026, AI models expire faster than session cache.

@trashh_dev For your sake, im taking this tweet entirely literal.

got absolutely shitted on at jiu jitsu today

I don't often see Reddit agree on things. But a small sample set apparently agree with you @tannerlinsley on directives reddit.com/r/javascript/s… tanstack.com/blog/directive… Me? I'm just dealing with fomo here and my SPA 😂

@VicVijayakumar I have stupid strong opinions about stupidly inane aspects of coding. When I started to recognize little contradicting patterns, I started to develop a generalistic rule: if I can't make the linter recognise it, I'll not enforce it on others.

This is why you implement a linter and style guide that are autorejected by CI for failing them, and then your engineers aren’t wasting time commenting on trivial shit. Argue once about which linter + style rules, then merge it. “Please add additional rules as a fast follow”

@trashh_dev How do you even tweet without kubernetes?

going to start a blog. should i use kubernetes?

@SQU1NCH @KylleSebree @TimHortons Truth bomb time: our politicians are all polar bears or Canadian geese wearing human meat suits.

@ericbdev @KylleSebree @TimHortons you are my primary source of canadian corporate/political gossip

wrong answers only

@SQU1NCH @KylleSebree @TimHortons MacDonalds is more Canadian than Timmies now days , atleast since the Brazilian majority RBI took over and MacDo scooped up their coffee supply.

@KylleSebree @TimHortons probably should be with all these canadians

@VicVijayakumar > customers asked for X, product thinks they would be served better by Y, and here’s how to ship Z which accomplishes X ∩ Y without busting the budget or accumulating too much technical debt This line of thinking, and ability to comm it with salient points, drives career growth

There’s a lot of material about how if you want to be an influential engineer at your company you’ll need to be a better writer. Coming from the startup world I thought this would be a lot of technical writing. Lots of “we want to ship X, here’s the engineering plan for how to do that and scale it”. The reality is I write a lot of “customers asked for X, product thinks they would be served better by Y, and here’s how to ship Z which accomplishes X ∩ Y without busting the budget or accumulating too much technical debt, allowing us to ship it in 1 month instead of 6, before everyone quits or we get re-orged & the focus changes again.” It is the behind-the-scenes writing that gets you the budget to do what you need to do, long before you actually do the thing. Startups have a singular focus and can turn on a dime. Big cos are like large cruise ships, especially given that most of your focus for the next 6+ months have already been codified in OKRs and go to market agreements. There is no good or bad. Some people have a visceral hate for this kind of work and only want to write code. Some thrive. For my part I’m looking forward to slapping a big ACCEPTED on my most recent RFC and creating tickets to track the MVP I’m about to build.

@housecor If you write up an ADR, flip it to Copilot in Ask mode for evaluation, then use that ADR for Copilot in Agent mode you can get wildly successful results. In PR phase you can also batch feedback to fix up multiple things in one sweep. As always with AI output is as good as input

This is wild. Assign an issue to Copilot, and it will implement the change asynchronously and open a PR when complete. Reply in the PR to request changes. Watch the vid - It’s the same workflow as working with a human dev. Wow. 🔥

@Szut @VicVijayakumar I've got myself a MotionGrey standing desk. They advertise supporting people up to 7 feet tall. motiongrey.com/products/motio… I can attest that: - the table is strong enough for me to stand on - at full height I can almost stand under it They have a 4 legged one too.

@VicVijayakumar what speed? what desk do you use? mine wobbles like crazy on each step. I'll build a raised desk but I'm tall so that would be very high I have a hard time walking more than 2 hours... did that today, 6mi/10k at 3mph

i walk on a treadmill all day while i work. recently bought a weighted vest to slow down / reduce muscle loss. anyway am currently wearing the weighted vest while i walk. on a treadmill. hope this isn't just hype.

@housecor @james_mtc I believe this is the way. As much as I use dev and local environments, (along with load/UAT/DevOps envs) I think in a 'pure" fashion we only really need Prod, Preview/Ephemeral envs, and temporary custom sliced release envs to verify code/app integrity.

@james_mtc Great examples. A long-lived dev environment seems redundant if I have ephemeral environments per PR, agreed? Could 'staging' serve the purpose you described for 'dev'?

I'm curious - Who's doing development with just two environments? (dev and prod) Would love to hear your experience and approach. If you have more environments, why do you feel they're necessary?

@theo Can't both be true?

Your product isn’t losing because it’s behind on features. It’s losing because it sucks.

@adamwathan Allan key drill bit homedepot.ca/product/anvil-… Slap that into a drill, or even ratchet screw driver and Ikea builds speed up like crazy.

What have bought that’s made something in your life a million times easier that most people don’t seem to know about?

@ThePrimeagen @theodorvaryag @ThePrimeagen you're safe, you used a string.

@theodorvaryag false

booleans are evil stop using them

For everyone that has ever bitched about #node #npm dependency hell, I hope you find yourself in #pip #python dependency hell. This ecosystem is worse than live ftp editing WordPress without git.

@mattpocockuk You've made typescript approachable for many people, and demystified many concepts. Congrats on being Google's #1!

Madness

@VicVijayakumar I'm not so sure it's a universal context switch cost. Go from coding to pairing on a topic I discussed yesterday? Ez. Go from learning new code base to giving an interview? Hard. Go from DevOps infra code to product/marketing meeting, then back? FML.

so I find that extremely senior engineers are very good at context switching and don’t need to recuperate between calls. they also don’t complain about meetings (unless there’s no agenda), and are happy to jump on calls, pair program, respond to a dm, write some code, whatever.