This post is for the nerds only... At work I spend way too much of my life targeting selectors. DOM

Written: December 5, 2025

This post is for the nerds only...
At work I spend way too much of my life targeting selectors. DOM selectors are my spellbook. Knowing how to grab the exact element in the DOM is straight up blackmagic. There is the right way, and then there are the many, many cursed ways. It is a dark art.
Most of the time you get a nice set of classese, maybe even an exact id. Something you can grab onto like a handrail in a hurricane. But then there is React. React is madness!!! React bends the internet in ways I did not ask for, which makes bending it back to my will a little tricky.
#root > div.h-screen.w-screen.bg-bg-body.text-text-primary.overflow-hidden.font-verdana.relative.selection:bg-accent-primary.selection:text-black.flex.flex-col > div.fixed.inset-0.z-50.flex.items-center.justify-center.bg-black/80.backdrop-blur-sm.p-4.sm:p-8 > div > div.flex-1.flex.overflow-hidden > div.flex-1.bg-bg-canvas.overflow-hidden.flex.flex-col.relative > div > div > div > div:nth-child(3)
PROGRAMMING GLASS
If I want to force that element to behave differently, sure, this selector will work. It will work for about ten seconds. If you even breathe on the DOM the wrong way this thing will shatter. If I change a font color somewhere else on the page this selector will explode like a glass spiderweb.
OK nerds. That is my suffering for the day. Back to work.