nisabek

I'm not some evil spy trying to make everyone use AI... both the startup and the blogpost are an experiment, a work in progress that I'm sharing I don't think anyone would read my blog and be like "Oh, now I need a tool for my SRE to automate incident management" People are starved for real life examples, this is a real life example. of course I'm not objective. To be objective you'd need to make a large scale study among thousands of companies. I'm sorry I don't have resources for that... just trying to get other people's feedback

Could be (the overcomplicating part), I'm just not yet comfortable loosing the mental model of the final application. At least not in all types of tickets. Are you not seeing that?..

If I'm attentive during spec/plan creation I sort of build this "expectation" of what the actual PR will look like, the mental model of it. Then it's somewhat easier to review. But the mental load is brutal tbh, and still not sure if it's "worth it"

our team has this link pinned in slack - very useful, normal human language used to explain!

CMS: Hugo(because it supports markdown!) Hosting: S3 bucket + CloudFront + Route53 Deployment: Upon commit, upload to s3

check it out - https://blog.envimate.com

We created an integration of icinga2 notifications with slack, using native NotificationCommand and just one dependency: curl. The cool thing is, you have it as a debian distribution ready for you to use from your icinga2 instance.

You can find it on github: https://github.com/nisabek/icinga2-slack-notifications#insta...

And icinga2 exchange website https://exchange.icinga.com/richardhauswald/icinga2-slack-no...

We would love to get feedback from you!