But now they move around even more heavy stuff with machines.

I think something similar might happen to our brains. Maybe we won't be able to work ourselfs through every detail of a mathematical proof, of a software program, or a treatsie on philosophy. But we'll abe able to accomplish intellectual work that only really smart poeple could accomplish. I think this is what counts: outcome.

I couldn't conclude it.

It's just a diagram that shows the economic relationship between companies. If they'd all merge into MegaAI, these flows would just be departments supporting each other on different AI projects.

It's not suitable to prove a bubble.

I think a bubble is nothing else than a sudden change in expected value. Currently, the market expects that AI is very valuable because of actual practical value. In this expectation there's also future improvements which might or might not come.

We might see a crash if we realize that this technology reached its limits. Then, we'll all look poorer on paper in the reverse way that we look richer on paper now than 12 months ago. However, I don't think anything serious will happen if such a crash would occur. It's not that people take loans to bet on these stocks.

(Even the 2008 housing bubble could be seen as a temporary market correction when looking at the long-term real estate prices. Housing is much more expensive today than on the peak of that bubble.)

I guess you got something: Users are not sensitive to these changes, or that any effect is too small to detect with your current sample size/test setup.

In a startup scenario, I'd quickly move on and possibly ship all developed options if good enough.

Also, running A/B tests might not be the most appropriate method in such a scenario. What about user-centric UX research methods?

My alternative to the menu bar would be a search bar that allowed me to search in a Google style everything related to that program: functions, features, shortcuts, and documentation.

File | Edit | View | etc. is not the right choice for every program.

My solution is extreme time boxing. Every Sunday, I sit down and time box the next week. Work and personal stuff goes into the same calendar. I've learned to keep enough slack to not get stressed out. I also know how much unplanned time I need to coordinate with co-workers.

It's kind of absurd that less freedom when to do things, gives me more happiness.

In the beginning I thought that this cannot work because sometimes you just need uninterrupted time to finish something. However, such uninterrupted long spans don't exist anyways for many people. There are stand-ups at work, you have appointments with some of your team members and at 5pm you need to pick up your kids.

[1] https://github.com/mo42/inven

Actual code is still the important part of a business. However, how this code is developed will drastically change (some people actually work already with Cursor etc.). Imagine: If you want a new feature, you update the spec., ask an LLM for the code and some tests, test the code personally and ship it.

I guess no one would hand over the control of committing and deployment to an AI. But for coding yes.

My impression is rather that the price of goods is based on how much people appreciate it. To me it better explains reality with the absurd prices for some stuff.

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

Points: 3

# Comments: 0

Badly-designed boats just don't return.

Ill-designed protection of cities means they'll be conquered.

Scientific ideas that do not corroborate, will be discarded.

etc.

Our current approach to AI doesn't have this mechanism. In the past, humanity just implemented ideas: a city was built according to some weird idea and lasted centuries. So the original idea would spread and be refined by further generations. I guess we need to bring such a mechanism into the loop.

I'm wondering when people will apply this to other areas like the real world. Would it learn the game engine of the universe (ie physics)?

For prose, replace all common adjectives by more specific or descriptive one, or even remove them too and describe properties. For example: The F-35 passed by my house. When I heard its sound, the jet had already disappeared at the horizon. (This describes super-sonic speed without an adjective or an overly precise speed number.)

Edit: past perfect based on comment

Are there any blog series about the details of query planning, optimization etc?

Nowadays, it's it's obviously different. To come up with something innovative, you need to develop something for a longer time so that it's better than everything that's already out there.

[1] https://users.sussex.ac.uk/~ezequiel/AS/lectures/AdaptiveSys...