If you just extrapolate what has already been possible and bet on the pace of growth of AI algorithms and techniques, robotaxi is almost a certainity and humanoid robots a possibility.

Therein lies the problem with gold, which is why a decoupled currency was required. A natural resource such as gold or bitcoin, appreciates as the economy grows, which in turn slows the economy down. With a printable currency, a country can control inflation or depreciate past value to create agony for people who have to continuously work to create more value. That is what forces nation-building and what capitalism helps with.

Dollar worked. And it won't be replaced with a fixed resource such as gold or bitcoins. But as the article mentions, it may not remain unique. That will be very interesting though, since the world has never experienced those dynamics before.

Here's a better solution option that is easier to implement; even adults can benefit, and I think it solves some of the problems:

1. Have an easy option to turn off feeds and enforce for non-adults. This would apply not just to meta, twitter, but also to Youtube, LinkedIn, etc.

2. Disable like display. The like counts are what hooks people and gives the dopamine kick. Add the ability to hide it and not show for under 18 easily.

3. Social and news sites should not be allowed to send notifications, period. Not on phones or browsers, at least not for those under 18.

Something along these lines would improve social media for everyone, not just kids. Parents' mental health affects kids the same. So blocking it just for kids only goes so far.

Comments URL: https://news.ycombinator.com/item?id=40310617

Points: 2

# Comments: 0

Rather than finding patterns in historical numbers, LLM can help quantify the current world in ways not possible before. This opens up a new world of finding new secrets.

Today we all benefit from OpenAI, but its the for-profit Open AI that made it possible. How else would they spend billions on compute and take those large risks, on whose money?

The problem is internal tools are less then 1% of what an actual multi-tenant product would be. So the skills to build an internal tool, don't always map to the rest of the 99%.

Given the answer to that is yes, the job may or may not work out well, that risk remains the same. The decision to leave that startup again should not be based on friendship but on personal situations and aspirations.

I personally feel its better to be working with friends than with strangers. The hierarchy equation is simply a matter of circumstances.

I have worked in older organizations, and the culture there is that the most productive workers spend relatively more time on their work chairs. That is the only way managers have traditionally known to get work done from their teams.

An open office is a natural way to ensure everyone is working, at least in how those organizations measure productivity.

If these companies move to a closed office, they will have to change how they measure productivity, and their culture may not allow that.

There was a post recently about a diabetic patient not able to afford the daily medicines. Most chronic problems require chronic medicines and regular consultation which can be solved.

One issue someone might raise is the quality of doctors. I have heard tons of cases from friend I know where the doctors have messed up here. It is mostly about reviews and trust, and applies globally, and can be an individual preference.

When building systems for scale where the databases may grow large, foreign keys can cause many issues -

- ORM features around foreign keys can easily bring your system down when joining large tables with incorrect/missing indexes during heavy loads

- As the table grows, not having foreign keys makes it simple in taking out large tables into big-data solutions in the future

- The schemas and relations are sometimes hard to understand during the initial phases of application development. Not having those relations makes changing schemas simpler and faster.

- Sharding tables is much simpler when there are no foreign keys

- It helps to add some of the reference logic in the application rather than the database. Databases are the bottlenecks when it comes to IOPS and scaling. The more processing you move to your application server, the better scalability you can achieve.

I am trying to get a perspective on the trend of remote here. I mean how is this going to affect Silicon Valley since this is different than the dot-com boom/bust? The story for the bay area (or tech hubs) in the past was that the VCs, executives, and talent all were here and innovation/creativity required being in the room together. All that seems to have changed post-COVID, especially for Silicon Valley.