I don't do front end work. I don't have the patience for it, it has changed every couple of years since I used Dreamweaver to teach middle school students how to create their portfolios ("Sancho, even I would not quest to learn swordcraft by studying the wounds." ~Don Quixote, sort of).
So, when I dare to venture where no backend infrastructure engineer dares to tread ("That code is a dev problem, the infra is working fine"), I have to rely on Claude to build it for me.
I don't know TypeScript, React, or even javascript in general, just enough to spot it and step over it, like a leisurely stroll through Rotterdam (if you know, you know...).
So, Claude whips me up a front end, and it's not only confusing, but it's ugly, like something out of The Worst Websites Ever Designed. Who even uses purple gradients unless you are selling, I don't know, eggplants? Ick!
Then the constant back and forth troubleshooting app routes and backend connections, reviewing the changes like it is yet another episode of Joyce's Ulysses, thick and confusing, and yet somehow it is supposed to be good to know, kind of like algebra.
Finally, I get a working prototype, and now I have to do accessibility compliance, input security, api security, seo optimization and collapsible UI troubleshooting. And I haven't even gotten to changing the background color.
I salute you, front end designers. You have come a long way from converting your print design and layout skills to the monitor screen and ever-changing front end technologies. It ain't just <html><header><title="My Page" /></header><body><h1>Put my magnificent content here</h1></body></html>
"I can't do that, the site volume can not be mounted from the sandbox. Do it on your WSL bash, here is the script."
Bite me, Claude.