Should they be writing quicksort in assembly as a first step? I think its legitimate in this case given that Jev is likely using the same tools as the example. Showing how easily the core is created using those tools helps to dispel some of the mystery and hype.
Example why its legit:
I just invented a new "Regression Estimate Validator" aka Rev. It takes hundreds of input dimensions, then outputs an interpretable score. Its very fast and statistically robust. Response: Ok but you could just use `pytorch.nn.Linear(d_in, 1)`? True, it is equivalent, but that's concealing millions of lines of hand-tuned math libs, CUDA, python, and other stuff.
The fact that there are many lines of code underpinning the target functionality doesn't make it any harder to use, and doesn't increase the value of the sales pitch for the "new shiny thing" using those few lines of code.
However, I do sympathize with your frustration that people can just say "its 1 line of code" when that line is "invoke API" which is really millions of lines / databases, etc. as a way to dismiss legitimate work without understanding its implications.
this is a good point. Similar to minimum wage, if the value of a young hire is zero, then working for free to gain experience is probably necessary (otherwise no one will hire).
We have other structural issues in society that make this difficult now. For example the fact that without a large pay check, few young people will be able to live near the place where jobs are available, afford essentials, and will have no health care.
But yes, if we returned to a culture of "children live with parents until married" and "apprentice at a company until your work is valuable", and companies returned to "hire what you actually need, then invest heavily in employee growth for the long term", and reducing churn of employees (so that employees and employers have incentive to do this), then it might be possible.
So how do you solve the problem of the company investing in their employees to make them more valuable and then the employees go to another company to get paid more (because that company does not spend on developing employing employees) or the employees leave to start their own company to compete with their original employer?
It's moot, because it will never happen. The apprentice system worked because they could perform actual useful work, if only sweeping the floor and such. An apprentice would only slow me down. A Keurig and a Roomba would be far more useful.
"Stealing" changes definitions every few years now, most recently with the mainstream suddenly deciding RIAA and news publishers are no longer the scum of the Earth but their new best friends, and reversing previous definition to now include IP transgression as theft, just so they can say AI companies are stealing shit.
Yes, but the quote about art has nothing to do with that.
The quote says that many artists borrow, meaning everyone still knows who did the original work and the artist is just riffing on it. But great artists transform the work so completely that it becomes theirs.
1. The next generation has been groomed by Buffet Himself, passing on as much knowledge as he can, but of course, this successor didn't create the fortune, doesn't appreciate it as much, and doesn't have as strong of judgement. However, he is surrounded by the old guard and wise mentors. But as those wither away, he is unable to determine who the worthy successors in his circle should be, slowly the inner circle begins to weaken too.
2. The next successor gets an even less effective set of principles from the first, only knowing off-hand how the money was made in the first place, they are a manager only. They also have no idea how the original people were selected or what makes a good inner circle. Soon it devolves into yes-men and people who seem superficially qualified to manage things.
3. The next successor has little no skills, other than showing up to meetings and going with what advisors say. Because the decision making of the original Buffet mentality has been so diluted, they only know superficial / surface understanding, akin to anyone who read the short books on the subject. They don't know how to do the deep diligence that made BH great. The inner circle is all sycophants, climbers, and clingers. Bad investments, debacles, and poor judgment create losses. Investors begin to panic sell, soon the BH stock crashes in value, losing 90% of the fortune.
And so on... Not hard to see how its like handing off a complex but successful open source project to your progeny instead of the most qualified developers. Pretty soon, its just an unmaintainable mess. They don't understand why things are the way they are, maybe they aren't as good a programmer as great grandpa. They definitely don't know how to hire and keep the best talent that originally built the thing. Pretty soon complexity budget and community good will are exhausted, people move to something newer and more dynamic.
It probably will happen over time as entropy does its thing, but the structure is different than what you describe.
For one, Howard is not the successor, Greg Abel is. Howard is a Stewart of culture, but he is not the leader.
He also isn’t inheriting Buffetts fortune so the generational rot won’t be the same.
Next, both Greg and Howard have been at Berkshire for decades, and however is next up will likely be similar. So there is time to pass on the values.
Laslty, Berkshire is a decentralized company. The company itself has less than 50 employees. All of the companies they own have their own leadership structures and cultures, and Berkshire does not burden itself in managing it. This makes the successor problem a lot easier
the same way every legal rule is enforced / checked: people look and if it seems iffy they examine/complain, and if a problem is found people get fined/jail.
Yeah could get interesting. Things like legal, programming, math, etc. are going to be relatively cheap / free. Meanwhile something like natural resources, building things, yardwork, etc. may go up in value. Or perhaps we end up with a relatively "spiky" economy since 90% of people are just doing physical jobs (the only human jobs with value), and the AI owner class of course gains all the value from intellectual products (with value diminishing towards cost of electricity). Thinking as human value may be roughly as valuable as it ever was (which is to say nearly non-existant other than the ability to solve an immediate physical problem). Might also be that physical strength and stamina are the highest value mating traits, since they will be able to protect and provide. Physically weak intellectual types will have little value since they can't out-think the machines, and they also can't provide for a family by doing valuable physical tasks. IQ overall begins to drop as mating favors intelligence less and less, as it can actually be an impedance to being productive.
For a short time in history, the ability to obsessively focus on intellectually interesting abstract concepts was highly lucrative, but just as quickly we returned to the laws of nature: those who can lift and move succeed, those who can only think are automated out of existance.
We go from a species increasingly seeing themselves as "brains with bodies" to "amazing bodies with weak brains". The limitation of robots and AI in the physical realm, power hungry, mobility limited are contrasted with human values: energy efficient, highly mobile and dexterous, extremely good strength/speed/size ratios. The brain on the other hand, while energy efficient, is completely outclassed and seen as we see our swimming/jumping abilities: a novelty for sports, but nothing we seriously consider a defining human trait.
The smartest humans can fill weekends with novelty pursuits like building circuits, games, programs, etc. But they are about as useful as whittling and hobby woodcraft, something to pass time, but ultimately of no economic value.
actually this is likely just as performant as the "Ugly but fast" code from the famous talk. After all, this is just branching on GetType() == typeof(Dog) which is presumably boiling down to an integer comparison. This roughly the same as the following C code:
void speak_generic(void* animal, int type_id) {
if (type_id == DOG) {
dog_speak((Dog*)animal);
} else {
dispatch_speak_vtable(animal);
}
}
Advantage 1:
You don't have to maintain this logic (its automatic), so you won't get weird cases if you forget to update all your switches everywhere, and/or you get weird fallthrough logic and footgun yourself in C.
Advantage 2:
You still get the flexibility of the vtable if you need it (for the case the type is chosen at runtime at not known). But for 90% of cases, its just as fast as the ugly C code.
Disadvantage 1: Losing a smug sense of superiority because you eschew abstractions and prefer writing verbose error-prone switch statements over clean easy to understand code.
Disadvantage 2: Writing performant code can no longer be gate kept behind archaic practices, now everyone can just use `var animal = new Dog()` and be done with it.
its because prior to that (2000 Bush era), congress and president had a plan to payoff debt and had a balanced budget plan in place to avoid over spending.
reply