alonsonic

This is a big giveaway because ai tends to overuse this same structure to "conclude"

If you read the article you would have seen that researches believe adjusting personality traits like neuroticism helps treat important mental health conditions more effectively than attacking the mental health condition directly.

Baker has one of the best movie adaptations, has been documented and reissued at nauseum and has worldwide acclaim and recognition. Sounds like mostly an inner-circle type of perspective.

They are purposely losing billions, this is a growth phase where all of the big AI companies are racing to grow their userbase, later down the line they will monetize that captured userbase.

This is very similar to Uber which lost money for 14 years before becoming profitable, but with significantly more upside.

Investors see the growth, user stickiness and potential for the tech; and are throwing money to burn to be part of the winning team, which will turn on the money switch on that userbase down the line.

The biggest companies and investors in the planet aren't all bad at business.

But there are a ton of LLM powered products in the market.

I have a friend in finance that uses LLM powered products for financial analysis, he works in a big bank. Just now anthropic released a product to compete in this space.

Another friend in real estate uses LLM powered lead qualifications products, he runs marketing campaigns and the AI handles the initial interaction via email or phone and then ranks the lead in their crm.

I have a few friends that run small businesses and use LLM powered assistants to manage all their email comms and agendas.

I've also talked with startups in legal and marketing doing very well.

Coding is the theme that's talked about the most in HN but there are a ton of startups and big companies creating value with LLMs

I'm confused with your second point. LLM companies are not making any money from current models? Openai generates 10b USD ARR and has 100M MAUs. Yes they are running at a loss right now but that's because they are racing to improve models. If they stopped today to focus on optimization of their current models to minimize operating cost and monetizing their massive user base you think they don't have a successful business model? People use this tools daily, this is inevitable.

Pretty can get in the way sometimes. I like your site, it's easy to ingest the information quickly. I might simplify the design of mine to make it more usable. There's a reason why hackernews is still looking like this!

I created an agent to scan niche independent cinemas and create a repository of everything playing in my city. I have an LLM heavy workflow to scrape, clean, classify and validate the data. It can handle any page I throw at it with ease. Very accurate as well, less than 5% errors right now.

Sounds like you asked Claude for a fix and it gave you a proper fix to your badly designed api endpoint. If it's an operation that's taking that long then yes, implementing it asynchronously is a good idea.

If what you wanted was a simple ductape quick fix I'm sure you could have asked for that and Claude would have recommended what you did, increasing the timeout window which I guess "fixes" the problem.

I think you're definitely engaged, but not so much with the moment itself more with the act of taking photos. It does make you focus on the subject, but in a very specific way. Even in how you described it, the main focus was on capturing the shot. It quite literally makes you look at things through a certain "lens".

You can see how that might be a bit of a problem when you're sharing the moment with others. You might end up being really focused on getting the photo and not as much on actually being present with them.

> Now we are building a machine so we don't have to do heavy thinking ourselves.

There are a lot of innovations that helped us not do heavy thinking ourselves. Think calculators. We will just move to a higher level of magnitud problem to solve, software development is a means to an end, instead of thinking hard about coding we should be thinking hard about the problem being solved. That will be the future of the craft.

It's ironic to see people say this type of things and not think about old software engineer practices that are now obsolete because overtime we have created more and more tools to simplify the craft. This is yet another step in that evolution. We are no longer using punch cards or writing assembly code, and we might not write actual code in the future anymore and just instruct ais to achieve goals. This is progress