But maybe this changes in the age of LLMs. A deterministic check to let LLMs verify the correctness of an API could improve the success rate of large scale refactors or performance optimizations.
Exciting!
1,575 karma · joined April 15, 2020
But maybe this changes in the age of LLMs. A deterministic check to let LLMs verify the correctness of an API could improve the success rate of large scale refactors or performance optimizations.
Exciting!
If you want to keep a secret, you must also hide it from yourself.
How can you tell?
It’s also popular enough that there is an abundance of high quality learning resources for beginners.
No other language threads that needle as well as C.
This is exactly what makes it great for teaching. Students don’t need to know actual arch or hardware details. They just need to grasp the core concepts of what is happening on the hardware.
For that purpose the ideal teaching language is lower level than python, javascript, Ocaml, etc without diving into nitty gritty arch specifics.
C is the undisputed champion in that domain.
Lifetimes are a compiler safety abstraction and mostly unrelated with how the computer runs your program.
Learning a language like C helps to understand why lifetime annotations are needed and how the compiler uses them.
Those that don’t need low level details can spend their professional career in languages like python and JavaScript while still have a sense of what lies beneath the abstraction.
For those that do want or need to go deeper, C is an excellent jumping off point into ASM and arch specifics.
Most modern languages have ways to automate parts of memory management, and rightfully so. But you should at least be somewhat aware of what is going on under the hood.
It’s still an abstraction, but at least being aware of memory management, copying vs referencing, etc are hugely important concepts that ML languages can hide.
Does the same hold for going from 5 days to 7 days or 8 hours to 16 hours?
A reasonable person should agree at some point adding more time will make people less productive due to lack of breaks, rest, etc.
Is it obvious where the line is? if so, where?
Technically any asset transferred to the next generation is “generational wealth”.
But in the context of a startup sale, when you say generational wealth almost nobody assumes you mean the ability to pass a few thousand down.
The common understanding is that you have enough money that future generations do not need to worry about money, assuming they maintain an average or slightly above average lifestyle and use the money responsibly.
Done?
Basically the bar is higher than "something you can pass down". It is enough that the next generation does not need to worry about making money either.
Common definition is somewhere between 1.5 to 5 million per child.
Including robotaxis, tesla semi-trucks, hyperloop, optimus, roadster 2.0, cheap whole home batteries, true FSD, Mars landing, nueralink, and more I'm sure.
It is difficult for me to get excited about a decades long, ambitious project when the follow through rate is <10%.
Twitter used to be an easy and free way to distribute updates publicly. That has changed, but the inertia is still there and there isn't a good low friction alternative.
Sounds really neat, but "incredibly ambitious announcement" from an Elon Musk company is starting to wear thin.
Is this real, or will it join the graveyard of other incredibly ambitious projects that were eventually abandoned to focus on the next incredibly ambitious project.
> Unfortunately everyone still uses the Nazi app
If your local town government for example only posts city updates to twitter, your options are to make a twitter account, use something like nitter, or miss out on updates.
post-training is like writing a wrapper around the binary. It is closer to building on top of than truly modifying, in that you can tailor things to your needs slightly but cannot make fundamental changes to the underlying thing.
Everything is a trade off.
I’m not a fan of limiting access to models, but the other extreme (no limits or guardrails) is at least as bad if not worse.
Not using retries is optimizing for the astronomically rare case, which is better mitigated by other means