Here's the thing, I tend to believe that sufficiently intelligent and original people will always have something to offer others; its irrelevant if you imagine the others as the current consumer public, our corporate overlords, or the ai owners of the future.
There may be people who have nothing to offer others, once technology advances, but I dont think that anyone in current top % role would find themselves there.
Awkward headline, since its not really much of a milestone. The first couple in a region are interesting, hitting significant proportions a year is interesting, a cumulative (relatively) small number is not that interesting.
I have in the past, but three things put me off doing so now;
Pages where I can spot inconsistencies are often controversial, with long dense discussion pages, edits here are almost impossible beyond trivial details. I dont mind fixing trivia, but not if the actual improvement I think I can make is rejected.
There is a bit of a deletionist crusade to keep some topics small, for example, Ive had interesting trivia about a cameras development process simply deleted. Maybe it is truly for the better, but it is not really that easy to add to the meat of the project, without someone else's approval.
Third, the begging banners really feel a bit gross; I know the size of the endowment, and how long it would be able to sustain the project (forever essentially)... It really feels like the foundation is using the Wikipedia brand to funnel money to irrelevant pet causes. This really puts me off contributing.
Why should an individual landlord have to subsidize an individual tenant? Its a scale of social interaction that doesnt make any sense.
This can have lots of issues. Imagine something like a good school zone changing, an event that may not be accounted for by the index. Insurance and taxes are determined by current value, that is partially determined by market rent, but the landlord cant adjust.
This also hurts a specific landlord when it comes time to sell, making a tenanted property potentially less valuable (and reducing the incentive to take on a tenant at all). This does not impact the general property value mind, as the tenant only benefits and creates this problem if the index is below the market.
If you want a fair balance, "its mine as long as I pay market rent" is pretty good. "its mine as long as I pay indexed rent" is not great, as it removes the financial benefit of capital investment from the landlord.
Its not really about building your own thing, its about identity... You are what you do.
If you dont understand the impact what you are doing has once its out of sight, how can you understand yourself as part of society?
Contracting is simpler in a way, "I made a tool for Steve so that he can better do his job" is an easy to understand story, and doing that 10 times a year makes your connections to the world fairly clear (Not to mention it builds on itself, as more people know you as someone who can make things for them).
Big corporate jobs, especially highly distributed remote ones, can make it nearly impossible to clearly draw a line like that. The narrow context of "I improved a tool that the Widget team uses to support the Tools team who build visualizations for the Documentation team" thirty layers down before you get to a thing customers touch. In person becomes important, because it lets you better understand the context of your work as "Part of the institution that makes fighter jets".
Burn out is hard to manage; its something that happens in the cruisy 20-something hour a week job as well as the 80+ hour pressure cooker. Probably not to the same degree sure, but its not the only thing going on here.
Its a whole lot more sustainable if you can build an identity around "here is my team, we are building {___}", and its a lot easier to get there if you meet in person frequently.
Genuinely clear objectives can also be a great asset here; but I find that clarity doesnt scale. When Ive been a contractor working on projects measured in weeks or months with small teams, full remote is easy. At corporate gigs where the thing you are doing might be several abstraction layers from a customer; its harder to answer "why are we doing this?". In the second case being able to share in person is important; because its not just the work its the context and other people doing it thats grounding.
That motivation brings efficiency; at least for myself.
The distinction that i think is important to make when talking about "the bitter lesson" is that improving the compute and training infrastructure and tricks in the abstract wins over intelligent model and system design.
Its more about the information about the specific problem you are solving having less impact than techniques that target the compute. So in this case, breaking down how to parse a PDF in stages for your domain is involving specific expert knowledge of the domain, but training with attention is about efficient use of compute in general; with no domain expertise.
We have global commerce; you are not only working on the creation part of something new, but also competing with similarly skilled people working with different more advantageous start conditions.
Nobody is talking about the difference between 1 and 2 billion, they are talking about the difference between 50 and 100 thousand, while competing.
There may be people who have nothing to offer others, once technology advances, but I dont think that anyone in current top % role would find themselves there.