i uh spend a lot of time thinking about whether various surprising software design choices are

a) intrinsic to the problem domain ("it turns out it DOES make sense!”)
b) made sense historically ("this made sense in 1992, but it didn't age well”)
c) just a typo/mistake (the "Referer" header)
d) related to budget/time constraints (“well, prototyping with shell scripts is fast!”)
e) cultural/organizational (“well, Google is the main funder for this project, and…”)
f) something else

If you are a #webdev type person and lately the web has felt kinda dry and not fun anymore, consider building a static site from scratch with no build steps, node, or vite.

Instead sit down in front of a code editor and hand code some HTML, CSS, and JS on your own. Fire up the @MDN web docs in a window, turn off all the builders and makers and pre processors and winds of tail and frameworks, and just try to build something cool, quirky, half-broken half-made, animated, and wholly your own. It will really help you get back in touch with why you wanted to be a web developer in the first place.

Today Blender turns 30! 🎂 Happy birthday and thanks to everyone for being part of this amazing community!

Here’s to the next 30 years! #b3d

https://www.youtube.com/watch?v=3fdTIV85l98

My entire career as a programmer so far has just been learning the ideals of the Grug Brained Developer the hard way:

https://grugbrain.dev

The best programmers I know all subscribe to the tenents of the Grug Brained Developer, whether they know it or not. Be like Grug.