replace the meat and dairy industry with b e a n s
he/him but also any
Recovering software developer, computers resenter
I like playing the bass guitar, painting, and some other things I’m not very good at
Mastodon @sjolsen@tech.lgbt
replace the meat and dairy industry with b e a n s
Based on the reporting two things seem clear to me: (1) the commercial value of Reddit is fundamentally a question of selling data access; and (2) the major subreddits will be made to continue operations come Hell or high water.
When (not if) Reddit circumvents the blackout by force, the obvious next move is to poison the well—make the data worthless by drowning it in noise (AI-generated, if you’ve a flair for the poetic). I doubt that will happen since (a) it would require coordination among a substantially larger and more dispersed userbase than the moderators and (b) it’s something of a nuclear option, but it’s an interesting idea.
Friendship ended with font gatekeeping and dogpiling, accessibility is my new best friend
Based on my own experience and years of spectating flamewars I figure somewhere between 40-80% of any programmer’s aesthetic preference is familiarity. I use Liberation Mono (probably because it was the default on some ancient version of CentOS or something) and I doubt it’d be anyone’s first choice, but every now and then I’ll come across something with its own defaults and it just bugs me.
On topic, the most obvious difference between Intel One and Iosevka is the radically different aspect ratio.
At my last job, doing firmware for datacenter devices, almost never. JTAG debugging can be useful if you can figure out how to reproduce the problem on the bench, but (a) it’s really only useful if the relevant question is “what is the state of the system” and (b) it often isn’t possible outside of the lab. My experience with firmware is that most bugs end up being solved by poring over the code or datasheets/errata and having a good long think (which is exactly as effective as it sounds – one of the reasons I left that job). The cases I’ve encountered where a debugger would be genuinely useful are almost always more practically served by printf debugging.
Profilers aren’t really a thing when you have kilobytes of RAM. It can be done but you’re building all the infrastructure by hand (the same is true of debugger support for things like threads). Just like printf debugging, it’s generally more practical to instrument the interesting bits manually.