I really should do a #introduction: hello! My name is Meredith. My handle comes from a book called The Bad Girl's Guide to the Open Road ("road tripping is the ultimate brain douche...") which I translated into personal branding for a bunch of blogging and podcasting in the early two-thousandsies and stuck. For what its worth, it's a consistently unclaimed name and I'm shameless enough to use it.
Professionally I'm a #frontend dev, or as I prefer to say, a stunningly average mid-career pixel programmer, and I think it's time for a promotion because right now the funnest thing I do is make feature prototypes. I try to promote #boringtech, #accessibility and #browserperformance, and at this point I'm just anti-react. If you want someone to come delete your code, hit me up!
Personally, I love #beer, #fountainpens and currently I'm falling in love with #videogames all over again thanks to my #SteamDeck , which I consider to be the best piece of hardware I've ever bought. #factorio #soulsborne #soulcalibur are my forever games.
I'm a lesbian, I'm thoroughly gaymarried, I live in Buffalo by choice, TERFs get fucked, trans liberation now, black lives matter, go unions, social democrat (yes I'd like a welfare state please), atheist, and I haven't hashtagged any of that because I don't particularly want to talk about any of it.
I'm serious, if you want nothing but html coming back at you from the server, please tell me because I have SO MANY QUESTIONS
Suggesting or greenlighting a new React-based project in 2023 is not a victimless act. It's the fast-track to team pain, P&L trouble, and user marginalisation.
Pay people to solve problems with HTML & CSS, not to make them with JS.
I am entirely on board the jamstack, progressive enhancement, browser performance, a11y-first, vanilla-everything pain train, and I've been pretty good at finding jobs for my 17 years as a web dev, but I'm having a terrible time finding jobs that actually do this stuff. I'm convinced I'm not searching the right keywords, but maybe that's not it.
Any suggestions, fediverse?
I was noodling around on the react.dev homepage today, taking screencaps for a presentation I'm putting together. I had dev tools open and I noticed something odd: every time I would hover over a link, something would get fetched over the network. "That's odd, and quickly adding up to megabytes of bandwidth", I thought.
So I looked at the fetches being fired, and it appears that the website is preloading the content of the page being linked when you hover over the link. Any link, every single time.
Let me say that another way: on react.dev, every onHover over a link costs the user between 5kb and 10kb of bandwidth every single time.
I feel like I'm losing my mind. Forget the fact that this website costs 2mb to download and takes 23 seconds to complete loading, how can charging the user and the app for every hover over a link be sustainable? How is this appropriate?
I've been handed a couple of full stack devs to help build my frontend project temporarily, and I'm finding that they're extremely weak in working with vanillaJS and regular html. I'm not surprised, exactly, but am I being unreasonable in expecting vanillaJS skills like this in the first place? Should I just plan for retraining people?
Backend developers are funny sometimes. I was talking last night with a guy on the other team. He kept insisting "this is a complex system, there are MILLIONS of entries in that db!" and he couldn't quite understand that I only care about looking at one at a time, or batches of 30 for the paginated list view, at most.
I'm not arguing that the backend isn't muscular and incredibly complex, because it is and as far as I'm concerned he's a wizard for making all that data dance efficiently. But I am front end, and all that is a black box behind an API to me and I like it that way.
Perspective will get you every time.
(Tbf he also thinks tables are incomprehensibly hard to write, so he is also kinda biased but still.)