5,132 karma · joined April 5, 2019
A year or two ago, I ditched doom and rolled my own emacs config, having gained the necessary knowledge and confidence to do so from my years with doom.
Both doom and spacemacs exist to make the (relatively) strange nature of emacs more welcoming to users of other IDEs. I’m not sure I would have stuck with it without them, so I’m not sure the hard way is always better.
However, we felt the benefit was worth the cost, overall, especially because we used the same flakes and therefore versions across all dev and deployed envs, and we didn’t have to deal with the hassle and performance issues of running all the dev services in docker containers.
The actual job was working on a python server for the acquired company, and it’s not like there wasn’t more work to do, but we were not allowed to go outside the bounds of the work that had been allocated for a sprint, which was always conservative in order to allow for more accurate overall plans. It’s certain that it was different in other departments or areas or acquired companies, but that at least was my experience.
All that is to say, I would not be remotely surprised if Cisco has more employees than they strictly need. But, this email from the CEO is comically out of touch. “We’re doing great, better than we’ve ever done, so we’re going to fire thousands of you” is a chef’s kiss encapsulation of American corporate culture.
I’ll add to it that structured concurrency patterns in async Rust can be legitimately awesome and very fun, once you’ve bounced off the traits in the futures crate enough times to use it in anger. The type system can be annoying, but as usual, it’s almost always technically right, and once you understand the ownership flow required for your nifty chain of future combinators, is not too too bad.
Edit: although I do think university focus is important for subjects that are less about job skills and more about knowledge synthesis, such as most sciences, critical analysis, and so on, if you intend to not just do a job but contribute to the overall knowledge base of the field.
Not having that, I developed the knowledge myself through trial and error, but we would have saved a lot of time, money, and stress doing it right the first time.
In general, I think this kind of “architect bad” take underestimates the cost and the stress of being responsible for a system that ultimately isn’t a great fit for the domain, and needing to balance hacking another fix onto it vs migrating to what now know is the right thing.
However, a) I think the compiler telling me everywhere I need to fix it is great, and b) even before LLMs, using compile mode with emacs and setting up a macro to jump to next clippy warning, jump to code, fix, and then repeating in batches of like 20-50 could often make it go quite fast.
Firefox/Mozilla tries literally anything to expand their feature set, customer base, or revenue stream? They need to stop spending money on that and instead spend money on the free product of theirs that I care about, in exactly the way I want.
Google surveilles the entire world, spends huge amounts on lobbying, degrades their own websites on other browsers? Not a peep, usually.
For my part, I pay mozilla for their VPN service, which I’m sure many here would decry as useless spending that should be going to firefox instead.
Here’s a thought: consider the potentially analogous case of performance-enhancing drugs for athletes. The drugs unambiguously make them better at their jobs, but the drugs have severe long-term health costs and wreak havoc on the fairness of the playing field. It’s easy to see why an athlete might choose not to use them, even when others are.
Of course, those negative factors alone are not enough to dissuade people en masse who want to get a leg up on their competitors, so the use of performance-enhancing drugs must be further restricted by institutional bans.
The firm expectations and lack of patience I have for any failings in most of my tools would be totally inappropriate to apply to another human being, and yet here I am asked to interact with this tool as though it were a person. The only options are either to treat the tool in a way that feels "wrong," or to be "kind" to the tool, and I think you see people going both ways.
I worry that, if I get used to being impatient and short with the AI, some of that will bleed into my textual interactions with other people.
Great to see people wanting to get involved with the project, though. That’s the beauty of open source: if it aggravates you, you can fix it.
Rigidity is a trade off: it can make initial development slower but refactors significantly easier, just as an example.
I don’t think any of your examples show it to be niche. It operates well in most of the space where C++ is a good option, and a bit beyond that (embedded, firmware, but also higher level things where you want performance but don’t want to worry about memory safety).