This is really interesting to me. It could imply that an ugly theorem is less valuable. What if a theorem is ugly but useful vs a beautiful but esoteric one?
266 karma · joined December 26, 2013
https://qubyte.codes https://github.com/qubyte
[ my public key: https://keybase.io/qubyte; my proof: https://keybase.io/qubyte/sigs/5hKm04_8qQK3B1sEV90Y-_qQgx50PlZWjT1hXvMUol8 ]
I was wearing an old trade shirt which had a Kurzgesagt sort of look to it. When I bought a print to the till it was in his eyeshot and caught his interest, so he came over for a chat! He's such a nice guy. He asked me what I do, and the next thing I know we're talking about tech stuff, and how he builds his site and shop. A true renaissance man.
Unfortunately, nearly two decades on, smaller weird visual artefacts are now just daily life and I seem to be very sensitive to glare (and I break into a cold sweat pretty often because that's how an aura looks when it starts). I only get a few migraines a year, but they seem to have rearranged the furniture in my brain a bit.
I got through a kilo of kimchi a week this way when I was a depressed 20-something living in a share-house abroad.
Going since late 2015. I post long form (/blog) and short form (/notes), mostly on programming, maths, (bad) generative art experiments, notes as I learn Japanese, and of course about the blog itself since I spend more time on the custom static site generator than I do on writing actual posts.
There are a few gotchas. The browser won't use the import map to result an entry point in a script tag for example. Content security policy is a painful one too for static sites like mine (the import map counts as a script, so you have to hash the map and put that in the CSP header).
https://qubyte.codes/blog/progressively-enhanced-caching-of-...
It’s built with my own static site generator (my favourite thing to tinker with). I author posts in my own flavour of markdown. Page templates are good ol’ handlebars. It’s built with indieweb ideals in mind with micropub and webmentions implemented using netlify build plugins and functions.
No.
The problem is that crunch culture selects for people in a position to put in that time. What of people with more complex home and personal lives (most people)? What about having a family? What if you're a carer? What if you have medical needs? What if your cultural or religious practices place limitations on when you can work?
You'll wind up with little diversity, which leads to terrible culture and poorly designed products.
From the consumer side I really enjoy using it. Queries can avoid lots of network chatter and mutations embrace procedural thinking (REST has answers CRUD, but not everything a server needs to do is resource based).
However, as a server dev I really don't like it. It puts much more power into the consumer's hands without providing good visibility into the database queries it's making behind the scenes and how heavy those might be.
As I see it, it trades client side complexity for some loss of control over database queries. I often see it sold as the former without mentioning the latter.
I blog about things which interest me (mostly JS and creative code related), but also take Japanese language notes as I learn. Also part of the 250KB club!
It's built with my own hand-rolled static site generator, and I'm pretty proud of it's capabilities now. I've got a bunch of indieweb features integrated into it. I have no sense of style though!