kspetkov79

Less code helps, but fewer unclear decisions probably helps more.

Nice side project. The thing I’d be slightly nervous about is the football-data cron. On small apps like this, it’s often not the app crashing, it’s some scheduled job quietly stopping and the data going stale. How would you notice that here? GitHub Actions notifications, logs, or just manual checking?

I would not treat it as code to merge. It is closer to a rough spec that happens to compile.

Mostly I try to understand the code around the change. If I cannot review the diff afterwards, the agent did not really save me much time.

The hard part is not packaging the knowledge. It is keeping it current and knowing when it does not apply.

Cloud cost problems are often just ownership problems with a bill attached.

They are not stealing the package. They are using it as a door into developer machines, CI, tokens, and customer systems.

For mail servers, readable configuration is a feature, not just aesthetics.

AI output is fine as a draft. The mess starts when people ship it without being able to explain the diff.

The missing part is usually the real workflow. If there is no output and no cost for being wrong, the AI tool just becomes another toy to maintain.

The account recovery story says a lot. At some size, companies start handling people as tickets. Sometimes it only gets fixed because one person inside still cares.

Postinstall hooks are a footgun. The bad part here is that people reviewing a PHP package may not even look closely at package.json.