alt Hacker NewsI think you need to open your mind to the possibilities? For example:
- scanning logs for errors and
- opening issues which are then auto-triaged and
- PRs are opened for them and auto-reviewed and
- merged (and deployed).
This workflow alone is immensely powerful, and takes alot of burden off the team.
Replies
> This workflow alone is immensely powerful, and takes alot of burden off the team.
ITSM those unsupervised workflows are essentially an attempt at purported productivity in the near term at the expense of meaningful incremental long term burden for teams.
The only ostensible benefit is in the eyes of the AI-psychotic tinkerer, who knows no better, or in those of the clout-chasing developer farming likes on their LinkedIn posts.
None of these are things I want or need in the product I maintain with a team, there's really no point to any of this unless you run a vibe coded SaaS (?)
> scanning logs for errors
famously a good job for a tool that takes 10-50k logs to run out of context and forget what it's doing.
A company at the scale to benefit from this almost certainly has some kind of development sandbox environment and/or periodic job runner that's integrated into its environment and maintained by a team, not random Mac Minis.