They expect to use AI.

There's something about seeing the whole year on the page that I really like. Seeing the whole picture.

I downloaded the repo to grab all the pregenerated files. Putting them together is pretty cool as well, as one year flows into the next and the full pattern emerges.

The scale of it is mind boggling.

lgtm

Persisting a data schema that represents business events is a great idea. That’s more about Event Sourcing though and doing that can answer a ton of questions about the system without doing it in log messages.

Wide events as a strategy is expensive, even with sampling, and doesn’t address the fundamental problem - why do we log messages?

I was hoping the article would enumerate why we log messages. Nailing down those scenarios first will lead to a happy life.

Why do we log? - proof of life - is the system running? - what is the state (in memory) when an error occurred? - when did an error occur? - do I need to get up at 2 am and fix something? - what do I need to fix?

I feel like every team operating a system has their own reasons for logging.

Do these ad sites make money?

It adds up when you run several dozens, they run a whole ring of spam

- http://www.abinternet.es

- https://www.actualidadblog.com/

I’m always skeptical when I see (or say for that matter) phrases that start with “just”.

Cool.

Yes.

Make it do TDD. That'll slow it down.

Make it do scrum with sprint planning, retrospectives and sprint demos. A then another AI as product owner and scrum master. Ideally this AI has only a vague idea of what the product needs to or the technology but still has decision power. That should really slow it down.

This was done already, they're called "Agent networks" or whatever buzzword the dev decided to give their abomination :)