375 karma · joined September 16, 2023
In short, if you want a person with Language A experience, but Language B is close enough, my software will provide the signal that the candidate is good enough for a closer look.
Example: PHP and Go devs are likely to have similar approaches to how software should be built. Ruby and Go, perhaps not so much.
There’s more nuance to it, but this is the idea.
The short description: you have an initial idea of the state (an estimate) and you take sensory input (literally from sensors like thermometers, cameras, potentiometers, etc.) and solve constraint equations that both refine the estimate of the system as well as tell the system what to do to achieve some objective. The objective could be something like prevention of an inverted pendulum attached to an electric motor from falling over.
My vimrc was set up over the years a bit at a time based on my needs. After several years, I did an overhaul based on what I truly need and don’t need from experience. I rarely change anything in it these days. Maybe a few lines if I start using a new language.
With that stated, most of my vim use is still understanding buffers and motions, which takes no configuration.
Are you arguing that people should not be able to take the initiative to move themselves from one place to another of their own volition? (driving)
There’s also scotty and servant for web server stuff.
There’s Esqueleto and Persistent for doing postgreSQL database queries.
And so on.
I barely touch my config except to add a line or two here or there when I want to add functionality for some new-to-me use case. Everything just fits like a glove and I can focus on solving my actual problems.
It is worth the effort to set this up once and for all.
Also, why have you done an “alacritty” vs “alacritty+tmux” benchmark yet have not done a “kitty+tmux” benchmark on this same table? That’s a big omission. The entire conversation is about the effects of adding a multiplexer on top of a terminal.
Because people also want a faster horse, not a car.
The iPad has been developing its own identity and language as a product category. Yes, it takes a while to iterate on the features. But Apple clearly sees the iPad as a chance to develop a language for how to interact with a tabula rasa. The easy thing would be to just slap a desktop OS on it. How do we get any better as a species if we do that? The iPad does need something, yes. It does not need a desktop OS.
“A manifold is a topological space that is locally Euclidean (i.e., around every point, there is a neighborhood that is topologically the same as the open unit ball in R^n)”
At this point, either you know what all of those words mean or you don’t. If you do, great! You’re done. If not, you either keep digging deeper into the various terms or you start seriously considering reading one or more of the curated reference books listed at the end of each entry.
Over time you develop the “mathematical maturity” that you don’t need to do a deep dive into the books and can mostly just use the reference.
They commonly keep employees using the simplest heuristics that someone at some point in the past developed which worked then, so why break it? And they push this mediocrity throughout the entire organization and industry. Then they swap out one failed CEO for the same person with a different name like a pair of gloves, wondering what ever happened as there was nothing more that could be done. Meanwhile their ageist management policies block out the insights of the young, all but ensuring that no new ideas are brought into the mix—all until it’s time for another bailout.