Adam's been making some of the best YouTube takedowns of corporate tomfoolery for a long time…glad to see him turn his talents towards an epic takedown of automobile culture! 😆

Yeah, I don't care for the those kinds of jokes. However, I care for tone policing even less. Maybe the occasional comment like "ok buddy, maybe that one went a bit far" is fine, but now we're having a entire thread about it and now I'm spending my time commenting on this instead of commenting on what is actually a Big Deal which is that cars in urban settings suck monkey balls.

(sorry monkeys!)

Test in screen readers and see how content is being announced.

Lists have certain semantics which are very useful. Definitely good in navigation (aka nav > ul > li).

Grids are also useful BTW—we don't have specific "grid" tags in HTML, but using ARIA attributes you can set up grids which might map onto div tags or even custom elements.

Personally, I'm much less concerned about ul/li than I am "div tag soup" which is a plague upon modern web development. Use div tags sparingly, and almost always see if you can reach for either (a) a more semantic HTML tag (e.g., key/val pairs should probably be dl/dt/dd tags, not list tags), or (b) custom elements…yes, authoring tags with one or more hyphens which are purely for developer comprehension and hanging CSS off of is perfectly fine—recommended in fact—and in some cases if you need some JS component logic as well, then boom you have web components.

Some things never change…

Not downvoting because I appreciate the effort…but ChatGPT is about as opposite from the ethos of open source as you can get imho. 😄

Ruby, absolutely. Still brings me joy with its expressiveness and flexibility.

I'm all for making fun of the Cybertruck, and anything from Felon Husk really, but I'd bet real money that thumbnail photo was doctored. I tried searching around for verified photos of rust but nothing substantial came up from a reputable source. Anyway, just wanted to point this out.

I'm a blogger and a web developer, so IMHO:

Blog-style sites have never been as cheap to run as right now. For small-to-midsize sites run mostly as static sites, it might even be close to free.

Virtually all cost is in the human labor, and the challenge of running a sustainable business model like subscriptions off of "words" which I think are valuable but getting audiences to agree is very hard.

But we might be seeing a turnaround here. I'm hopeful!

My daughter told me she was getting paper from the other room to draw on, and as she ran off I replied "Sounds ink-credible!"

Opt-out is bullshit, it's unethical. Unless people specifically give their consent to their content being used for training data, and are compensated if they wish to be compensated for that privilege, then it's just not morally defensible. Legally defensible? Sure, maybe so. But we don't like to support companies who are merely abiding by the letter of the law, we want them to abide by the spirit of the law and of treating their customers with respect and consideration. This is not that at all. 😕

"physically easy"

Sure, because our necks, backs, and hips are all feeling so great all the time with these long hours at the desk.

"pays well"

Some tech jobs are connected with living in places with high living expenses, not to mention some tech jobs aren't at Big Tech firms so the pay is lower. Struggling with finances doesn't magically disappear because you're good at code.

"people think you're smart"

lolololol said every person ever who isn't white man passing or perhaps presenting as one of the "privileged" minority classes.

Look, do I agree tech jobs on average are appealing compared to many other professions? Sure! But minimizing—verging on gaslighting—the very real harms people may suffer while working in tech is irresponsible. Our industry has a long way to go to provide real equality, equanimity, and stability.

Someone in your organization needs to be in charge of frontend fidelity. I don't mean an official job title, I just mean someone who has taken it upon themselves to have a "the buck stops here" mentality—better yet someone who is recognized by the rest of the team to have that priority.

If nobody else fits the bill, then that person is you. And by all means, make all the stink you want about these issues. Nobody should ever be touching global stylesheets that affect multiple components or screens throughout the system without there being subsequent review or issues filed in a very visible way. Ideally, those sorts of breaking changes would never make it through code review in the first place.