Agreed with other commenters that nothing was likely actually broadcast, but if it was it would definitely be highly illegal and you’d have feds knocking down your door pretty quickly. They don’t joke around with illegal transmissions like that.
Sorry I was unclear, I mean 50s or 70s air travel compared to present day air travel. (Which on reconsideration might not be particularly relevant haha)
Bicameralism appeared very, very early on. There’s a well known case of a missing pig in 1642’s Boston (with a population of less than 2000 at the time) that finally solidified splitting the assembly into two chambers, and that debate has been going on for a while at the time already https://www.americanantiquarian.org/sites/default/files/proc...
This seems to assume unusual optimism or foresight, most people don’t invest their life savings 100% into stocks and don’t hold on to 100% of their company vests through ups and downs. You might as well say “assuming he put all his money in NVDA…”
It's a back-of-the-envelope calculation not a precise one. It doesn't take foresight to invest in SP500. DCAing (dollar-cost averaging) into an index fund is actually the recommended savings strategy with a short-term cash balance of 6 months-2 years of cash savings depending on your plans (sabbatical etc.), especially when one is decades away from retirement age.
I only included meta because he works/worked at meta and it's not unusual for people to just leave their rsus in their accounts after they vested. I agree though that one shouldn't pick stocks that happened to explode (e.g. nvda).
There are several unrealistic assumptions I did make:
* Presumably when someone starts, they earn less than in recent years. He probably wasn't making huge amounts his first few years. Amounts invested in earlier years are smaller but have more time to compound and amounts invested in recent years are larger but have had less time to compound.
* Returns aren't constant.
* I pulled the $2 million/yr out of thin air. It could be $1 million/yr or even $10 million/yr. I have no idea what the overall head of a project like PyTorch would make.
* Everyone's expenses are different. In and around NYC, one can live on $80k/year, $120-150k/year as well as as on $1 million/yr. I assumed zero since I wanted a nice even $1 million/yr savings. Maybe it was $500k/yr of savings in which case all the numbers should be halved.
In any case, I can't see how one wouldn't end up with at least $10 million in a position like this with 10 years at meta. Unless one buys a $5 million unit in Manhattan and is burdened by a high mortgage.
Ha! Endorphins are "endogenous opioid peptides produced by the pituitary and hypothalamus glands that function as the body's natural painkillers and mood regulators".
"They are part of the endogenous opioid system", so either way was talking about literal highs.
The endocannabinoid system (I hope that I have the spelling correct) is a relatively recent discovery (1980s on), and is quite fascinating on how integral to the human body it is
I’m like that more often than not. Words and language always seemed like a “translation layer” to express myself to other people, not something essential that needs to happen in my head. Especially when thinking deeply about some technical problem there’s no language involved, just abstract shapes and seeing things “in my mind’s eye”.
We might just be rehashing that silly internet meme about “shape rotators”, but there could be a correlation here where people whose minds work this way are more dismissive of LLMs.
Steelmanning the "we must force tool usage" position: it's possible that a tool does increase productivity, but there's either a steep learning curve (productivity only improves after sustained usage) or network effects (most people must use it for anyone to benefit).
No opinion on whether or not this applies to the current moment. But maybe someone should try forcing Dvorak layout on everyone or something like that for a competitive edge!
I once had a boss who saw me use Vim and was really impressed with how quickly I could jump around files and make precision edits. He tried getting the other devs (not many, < 5) to use Vim too but it didn't quite pan out.
I would guess that interest, passion, and motivation all play a role here. It's kind of like programming itself. If you sit people down and make them program for awhile, some will get good at it and some won't.
> I would guess that interest, passion, and motivation all play a role here.
And, to use less pointed language, people’s brains are wired differently. What works for one doesn’t necessarily work for another, even with similar interest, passion, and motivation.
I worked with a developer that copied and pasted A LOT and would keep his fingers on the old copy and paste buttons (Ctrl-Ins, etc.). I've even seen him copy and paste single letters. He's one of the most productive developers I've ever worked with.
I was using emacs for a while, but when I switched to vim, something about the different modes just really meshed with how I thought about what I was doing, and I enjoyed it way more and stuck to it for a couple of decades.
I see people that I'd say are more proficient with their emacs, VS Code, etc setups than I am with my vim setup, so I don't think there's anything special about vim other than "it works for me".
I've had plenty of interest, passion and motivation during my career. But never, ever, directed at learning something like vim, even if it's going to make me more productive.
I'd rather learn almost any other of the myriad of topics related with software development that the quirks of an opinionated editor. I especially hate memorising shortcuts and commands.
Your old boss probably would have been a bit chastened if he knew said devs would then be spending their hours learning how to exit Vim instead of programming
There was a time where I'd change to a different terminal and do sudo killall -9 to get out vim.
And that time when I changed vim to a symlink to emacs on a shared login server and sat back and enjoyed the carnage. (I did change it back relatively quickly)
Coding agents seem to be in the fun paradox of "it's so easy to use, anyone can code!" and "using it productively is a deep skill, and we have to force people to use it so they learn"
But it’s both, isn’t it? It’s so easy to use, anyone without any coding experience whatsoever can produce a somewhat working prototype. It’s hard to use well, most experienced developers will end up with net negative productivity without learning what works and what doesn’t.
Programming isn’t a government desk job. The interface between programmer and company should be the output only, they can’t force a programmer to use w/e bs they think is good at the time
exactly, i mean can attach a research agent to each file or commit to validate and confirm the values, which would just give validity to internet information I guess.
If you're a utility, you may not like that solar and batteries are driving down electricity costs and reducing grid expenses. But even with the thumbs against the scale, we are seeing the most nameplate deployment (see caveats in my parallel reply) in decades, and will likely set a record, because of solar, batteries, and wind in that order:
reply