
@Sempf @cR0w I have updates and they are NOT what I was anticipating my guys.
One guy laughed at me and said he was going to go ask his agent what it thought about that.
Another one said, "You clearly do not understand AI" which I feel is window-throwing adjacent.
And then they started talking about nuances in AI and I left.
@Sempf In a meeting a couple of weeks ago my boss announced we were all going to become versed in "AI Ops." None of us specifically knew WTF that meant, so he described it to us.
When I asked, "So it's basically just automation?" he had to blink a few times and recover before admitting that yeah, that's about it.
@DaveMWilburn @Sempf
Not if you put an AI agent inside your cron job, which was discussed at this morning's meeting.
We can't do it for tax filing because that needs to be deterministic or people can go to jail, but insurance underwriting? We can do that with AI. With human judgment it's already nondeterministic, donchaknow.
@Sempf Overwhelmingly, I continue to find all use cases in line with one of @cR0w 's big points - none of this so far is innovation, just recreating deterministic automations.
There are exceptions...but the thing these companies are trying to solve for on both sides isn't security, but paying people for their knowledge, experience, and outputs.
@ericdaryl @jackryder @neurovagrant @Sempf @cR0w
I liked "answer shaped text" but the signal one is more technically accurate.
Also "mansplaining as a service"
@ericdaryl @jackryder @neurovagrant @Sempf @cR0w
stealing that one. :)
Someone more clever than me told me that was called learning! :)
@Sempf "Setting up a Cron Job is difficult as is reading them" - clearly defined problem that can be solved.
"Cron Jobs can't be set to the scheduling patern I actually want" - clearly defined problem that can be solved, albeit with a lot more effort.
"We should use AI to schedule things!" - ?????????????
@Sempf systemd never "shot my dog". The systemd timers is the first time I've really found something that impacted my life, to dislike. But then the systemd-cron #debian package was right there, so it's not as though an "out" to this problem wasn't provided for me.
To all the #systemd haters - look, #MXlinux has a nice balance where systemd is not the default, but then gives an easy path to using systemd, should it prove to be necessary (and in my case, yes it is). Hating systemd is no hill to die on, I say.