My guess is either someone raised this internally and was told it was fine, or knew but didn't bother raising it since they knew they’d be blown off.

Does reading to a toddler count? If it does, I'm bringing up the mean to say the least.

I think we should get double credit for every reading of Goodnight Moon.

I assume you know, by now, that everyone poops

I have never been more certain.

Does that last long? Commercial damascus is typically acid etched which seems like it would last better, but it wears off eventually too.

[edit] oh, I guess coffee is acidic, so maybe it’s not that different. I was thinking of using it as a stain at first

I am 10+ years into my career. I don’t think mgmt / entrepreneurship feels like the only sustainable path. But I believe I may become a manager of a 5-10 Claudes.

What are your Claudes going to be building and who is going to fund it?

Put on my gravestone “I Was An Internet Cowboy”

Is that like a rhinestone cowboy?

This seems to be a major source of confusion in these conversations. People do not seem to agree on the definition of vibe coding. A lot of debates seem to be between people who are using the term because it sounds cool and people who have defined it specifically to only include irresponsible tool use, then they get into a debate about if the person was being irresponsible or not. It’s not useful to have that debate based on the label rather than the particulars.

The original use of the word "vibe code" was very clear.

You don't even look at the diffs. You just yolo the code.

https://x.com/i/status/1886192184808149383

That's a fair point.

“They don’t pay you to be perfect, they pay you to be yourself.” -Ted Lasso

Keep meaning to watch that series

Devs are where projects meet the constraints of reality and people always want to kill the messenger.

Devs are where the project meets reality in general, and this is what I always try to explain to people. And it's the same with construction, by the way. Pictures and blueprints are nice but sooner or later you're going to need someone digging around in the dirt.

No high paid manager wants to learn that their visionary thinking was just the last iteration of the underpants gnome meme. Some things sound good at first but unfortunately are not that easy to actually do

I agree that the primary feature of CSS is what people don't want from it anymore. If you're building your app with components (web components, react, etc), those become the unit of reuse. You don't need CSS to offer an additional unit of reuse, it only complicates things at that point.

This is a great point. Style reuse was the dream of CSS, but we have all mostly settled that that's too fine grained for anything beyond a simple website. It's much easier to build, share, reuse a bunch of components.

This is technically true, but misses the point. Tailwind classes are fine grained utility classes, the fact that they are CSS classes at all is pretty much an implementation detail.

Compare tailwind classes to bootstrap classes and you'll see what I mean.

A useful thing you can do is make your html linter error if a link has target=blank without rel=noreferrer

EG https://html-eslint.org/docs/rules/no-target-blank/