If it gives you any consolation, I’m also a fan of em dashes and don’t assume LLM output when seeing them. But there are other telltale signs of LLM writing. At least when the LLM is not instructed to hide those maybe?
The “default” LLM style is so grating to me, in a condescending corpospeak kind of way.
I’ve seen this AI written article circulating around already and I must say it’s a terrible article.
It boils down to system A having none of the information required for a proper fix (and botching every step onwards) vs system B having all of the information (and not deploying idiotic stuff).
If the point is that with event sourcing you cannot forget to record info that will be fundamental in the future simply because you didn’t understand it was important when the system was written, then this article does absolutely nothing to show this.
Otherwise this article is just showing how easy it is to fix a bug when you have all the necessary data to fix a bug.
If it gives you any consolation, I’m also a fan of em dashes and don’t assume LLM output when seeing them. But there are other telltale signs of LLM writing. At least when the LLM is not instructed to hide those maybe?
The “default” LLM style is so grating to me, in a condescending corpospeak kind of way.
I’ve seen this AI written article circulating around already and I must say it’s a terrible article.
It boils down to system A having none of the information required for a proper fix (and botching every step onwards) vs system B having all of the information (and not deploying idiotic stuff).
If the point is that with event sourcing you cannot forget to record info that will be fundamental in the future simply because you didn’t understand it was important when the system was written, then this article does absolutely nothing to show this.
Otherwise this article is just showing how easy it is to fix a bug when you have all the necessary data to fix a bug.