> we don't really know much about how fish live and their overall population

Absolutely yes. Orange roughy is a good example - it was caught by trawlers when they were massed in huge balls near the surface. Easy to get a big catch quickly. Turns out this was when they were spawning, so breeding cycle was being interrupted, which led to catastrophic declines very quickly.

The 'spec' frameworks are documentation as well, but can become contradictory as decisions about the app change over time.

> He has directed job candidates still working for Apple to bring “Actual parts” from Apple to their interviews for “show and tell” sessions in which he and his team at OpenAI can elicit still more Apple confidential information

And an infinite money-eating bonfire

- Meetup alert for meetups that match specific topics

- A daily journal that transforms entries into chibi-style cartoons

- A cashflow forecast our stupid accounting software can't do on its own

- DIY service monitoring for a ragged collection of docker containers, cron tasks, scripts and various others

Bic pens. Disposable razors. Whipped cream in a can.

Add LLM code to the list.

These tools don’t solve big design problems, but they do resolve all the little design decisions often left up to devs at implementation time.

It's still daunting posting in a second language, and LLMs are an attractive solution to that (depending on your definition of 'solution').

> Some people can really benefit from using LLMs to help them write. E.g. non-native speakers.

What are the plans for monetization?

Yes. Another way to describe it is the valuable part.

AI tools are great at delineating high and low value work.