> I also still think there are a lot of bad use cases for repositories and service layers that people should avoid, but that’s a digression which should probably become its own post

As a huge proponent of the repository pattern, I'll be looking forward to this post.

As an aside, I have an article in my blog that has GIFs in it, and they're important for the content, but I'm not a frontend developer by any stretch of the imagination so I'm really at wit's end for how to make it so that the GIFs only play on mouse hover or something else. If anybody reading has some tips, I'd love to hear them. I'm using Zola static site generator, and all I've done is make minor HTML and CSS tweaks, so I really have no idea what I'm doing where it concerns frontend presentation.

All the code I've written since joining has used `typing.Protocol` over ABCs, simple dependency injection (i.e., no DI framework), no inheritance anywhere, and of course extensive type annotations... and our average test coverage has gone from around 6% to around 45%.

It's honestly baffling to see how insanely over-complicated most of the Python is that I see out in the wild, especially when you consider that like 90% of the apps out there are just CRUD apps.

There's actually a place where the original authors subclassed dict, and dynamically generate attributes of a "data class" such that it can be used with dotted attribute access syntax or dict access syntax but the `__slots__` attribute of these classes is also generated dynamically so you don't have any auto-complete when trying the dotted attribute access. It's genuinely insane lol.

> whenever I'm browsing in a container tab, I wish CMD-T opened a new container tab

Not exactly what you're looking for, but Temporary Containers (no longer maintained, fwiw) at least will open every new tab in a new temporary container that will be wiped after a configurable amount of time after closing.

Forgive my ignorance, but what's wrong with this one?

Sure... yes the bright orange is ugly, but it's not the ugliness that prevents you from getting shot, it's the bright unnatural color. Other hunters aren't thinking "oh that's really ugly, it must not be something I can shoot" they're thinking "bright orange means person, I should not fire my rifle in that direction".

> If it wasn't, it wouldn't grab my attention so well.

Are you saying that if you thought the bright orange was pretty it wouldn't occur to you not to fire your gun in its direction?

Ugliness is not the point of hi-vis vests lol, the point is to not get shot by other hunters.

FWIW, you'd also have the benefit of being able to unit test your logic.

My next car I got in 2021 was a 2007 Prius. It has a super thick A-pillar in a really terrible spot that makes turning left quite stressful. The turning radius is amazing and I love driving what these days is considered a "compact car", but I absolutely loathe the A-pillar. I am constantly dancing in my seat to see around it, and will check both ways 4 or 5 times before crossing roads from a side street because my field of view is so limited.

I've always mused about whether reducing vision for the sake of crash safety actually ends up resulting in more accidents. Is it better to try to prevent accidents by improving visibility or mitigate harm in the event of an accident (which seems more and more like an inevitability these days where I live where there's virtually zero traffic enforcement; I see red-light runners multiple times per day, and a section of our city highway with 55 mph speed limit has the entire traffic stream going 75)?

I could talk for days about the design of modern cars in the US...