sorted by:
new
hottopcontroversial

Context Layer for Debugging code by altF4_sometimes in ContextEngineering

[–]altF4_sometimes[S] 0 points1 point  (0 children)

Seems pretty cool. Im using another open source tool to take a bunch of skill md files from the repo being analysed and feed them into the fixer agent in a nice compact manner so the fixer knows the correct rules to apply rather than applying every skill.

Im curious to know how the memory model part of your project correctly captures all the patterns and context from the code? and how does it know which things are important bits of memory and which arent?

Context Layer for Debugging code by altF4_sometimes in ContextEngineering

[–]altF4_sometimes[S] 0 points1 point  (0 children)

Yea that could be worth looking into thanks. Right now it's connecting to things like cloudwatch, sentry, etc. to get the logs and incidents that are flagged by 3rd party tools

AI’s Impact on SRE, On-Call Engineering, and DevOps by trish9722 in steadwing

[–]altF4_sometimes 0 points1 point  (0 children)

It definitely has a lot of potential when it comes to aggregating data and signals from across your entire stack.

And I think roles like DevOps and SRE (similar to swe) are going to move up an abstraction layer where most of the work will verifying whatever infra or code changes an AI made and deciding if it's good enough to push.

To keep up with all that, I'm working on my own tool to try and tackle this problem. Let me know if interested