You approved that UI PR without seeing itThe PR is called "Tweak card spacing + dark mode fixes." It's +184 −97 across six files. You read it. p-4 became p-6. bg-white became bg-background. A card component got split in two, which honestly nOct 4 · 5 min readcrossui.hashnode.dev
Your sx prop is already a data structure, and almost no tool treats it that wayLast week I wrote about why shadcn is hard to edit visually, and somewhere in the middle I made a claim in passing: shadcn's styling is a string, MUI's sx is data, and those two need different editorsSep 27 · 13 min readcrossui.hashnode.dev
shadcn/ui says the code is yours. So why can't anything edit it?shadcn/ui's whole pitch is that it isn't a dependency. You run the CLI, the component lands in components/ui/button.tsx, and it's yours. No package to upgrade, no wrapper to fight, no !important war wSep 21 · 12 min readcrossui.hashnode.dev
Every React instructor has drawn this box diagram. Let's go furtherYou finish teaching props. You drew the box diagram, you gave examples. And they got it — you ask a question in class, they answer it fine. Next week, in the homework, the same student asks: "how do ISep 14 · 11 min readcrossui.hashnode.dev
Vibe coding made writing cheap. It made reading expensive. A junior I know shipped a change last month. Cursor wrote it. He ran it. Looked fine. Opened the PR. Senior sent it back in five minutes: "this touches three things we don't have tests for." He had noSep 7 · 10 min readcrossui.hashnode.dev
