Am I just the luckiest person on the planet or are posts like this just skewing reality/making a problem out to be bigger than it is?
I've had very, very few issues with hardware on Linux. Even fairly niche hardware. I've easily had 10x the issues, if not more, on windows/mac.
Omarchy is compromised as far as anyone is concerned you cannot release a list of the billionaires funding your project and say it's "for the people". It's Oligarchy Linux.
@MikePFrank Working on it from the type-theoretic side! (hint: there's a use case for forward-only gradient calc with computed back-prop that's both wildly faster and higher precision) https://t.co/QEK1ZAAkqk
"Aren't we reading the code now? Just imagine the tech debt you're buying! It is pure slop now!"
You guys clearly have privileged jobs then.
You haven't seen the codebases I've seen and all of those were previous to AI 😂
Have you ever seen a 50mb angular spa 😏?
@LuizaJarovsky Don't conflate the mechanics and the value of intelligent systems with the toxic product that the hyperscaler-adjacent extraction specialists are pimping out to the world.
@LuizaJarovsky Manifestly not true. It's just that the ones that *do* know are systematically marginalized to the point of being de-platformed. Meanwhile all of the coke-snorting, over-gesticulating, Hyde Park humping miscreants suck all of the air from in front of any microphone they can find.
@TaliaRinger I tend to think of it as poorly written Agatha Christie fanfic, authored by a high-schooler. (not that there's anything wrong with that - if that's the actual target)
The first thing I do after writing code is look at the LSP markup. I have no idea why people don't spend time with a type checker. There's no need to debug or run console logs if the compiler can tell you if your concurrency satisfies wait-for edges before you build. #cleflang
"The first thing I do after writing code is set a breakpoint and step through the function."
I do that often too. I always run File Pilot from the debugger. In fact I spend a lot of time in the debugger. I'm not exactly sure why people flex about working with prints only. It's like diagnosing a car by listening to the engine instead of opening the hood.
Also this is 100% true: "Well, your head is a faulty interpreter."
@Aaronontheweb Well, it *can* depending on whether there's a swarm of pendants descending on your meeting with questions that are thinly veiled mini-lectures... 😆
Great interview that eventually delves into stochastic programming, Bayesian inference and building language tools that express principles to update priors for computational integrity. https://t.co/vgLfVZZRYr