That feeling when you fix your own problem using a blog post that you wrote 6 years ago

If Internet marketers became book publishers they'd center all the text in their books for aesthetics

Behold, the ugliest block styling code I've ever written. Don't ask me to explain what it does I don't remember and I can never change it

As the content web begins its inevitable decline, it's unbelievable that WordPress was the best we were able to do as an industry

The last 8 months been the least exciting of the 8 years I've been in a programmer. The whole space has become a mono-conversation about AI

We used to have debates. Imperative vs declarative. Functional vs OOP. BEM vs Tailwind. Now its just "AI, good or evil?" or "Here's how to use AI effectively!"

Jonathan Blow says we don't even expect software to work. Just today:

- I made an IKEA purchase that never rendered a confirmation screen
- Downloading my Xfinity invoices showed a loading screen then did nothing
- I can't access my security system payment portal

We don't expect software to work.

First night of using Cursor complete. The speed wins I got by by AI written boilerplate were lost when I tried to vibe code a feature.

I like that you can turn tab completion off, but I'm finding its autocomplete recommendations more useful than Copilot's. Using this will make me a worse developer.

Cursor night 1:

Truly impressive software. I kept slapping accept all, and I get mostly working software that I'm afraid to touch because I didn't write it, and it has way more CSS than is actually necessary but I don't know what does what

The things that make CSS tricky:

- Global styling that has to be overwritten everywhere (overwrites = cascade)
- Over-specified selectors (cascade, ids, elements)

You can avoid these tricky bits by styling by class names, and using :where() to remove specificity when you need the cascade.

Peak UI

In what grade did you peak & what’s the worst configuration language you’ve touched this week?

A company's automated chatbot just successfully helped me troubleshoot a problem. This was a first for me.

5 years ago, these chatbots were gatekeepers to keep customers away from human support staff. Now they're actually useful.

2025 is a milestone year for AI, and I don't know what happens next.

CUT MY LIST IN TWO PIECES

THAT’S HOW YOU START QUICKSORT

CSS specificity remains an issue in 2025, but we have better tools than ever to avoid it. Even ignoring Tailwind, the :where() pseudo-class solves cascade specificity issues in content areas

Still the best solution remains avoiding the cascade wherever possible and avoiding ID & element selectors

Chaos: CSS with Allman style braces