prompt-engineering VS keep

An agent is a style of prompt that lets LLMs act as reasoning engines. It's also known as the ReAct pattern (which engineers are avoiding using for namespace collision reasions).

You can read a good intro example here: https://github.com/brexhq/prompt-engineering#react

Well, if developers get replaced by AI, then who are the managers going to manage :). I personally don't think AI is just going to replace us. The way we work will continue to change as new AI tools come out. I'm taking time to tinker with new tools and seeing how others do as well (e.g., I found Brex's tips and tricks for working with LLMs very insightful: https://github.com/brexhq/prompt-engineering).

I recognize there's plenty of catnip here when it comes to calling this "engineering" or not, however, whatever you want to call it (prompt fiddling?), the techniques are crucial if you want to achieve reasonably consistent output from current-state LLMs. As models improve concerns about context window limitations will be reduced and it will be easier to discern user intent.

These are good straight-to-the-point guides:

- Prompt Engineering by BrexHQ: https://github.com/brexhq/prompt-engineering

- OpenAI guidance: https://help.openai.com/en/articles/6654000-best-practices-f...

- https://devblogs.microsoft.com/dotnet/gpt-prompt-engineering...

- (great examples): https://www.deeplearning.ai/short-courses/chatgpt-prompt-eng...

tl;dr:

Brex's Prompt Engineering Guide (https://github.com/brexhq/prompt-engineering)

I enjoyed talking to Tal, CEO and co-founder at Keep. It started as a CLI tool and, over time, became an alert aggregation tool.

Keep

Missing any provider/feature? just open an issue at https://github.com/keephq/keep and we will add it ASAP (and of course contributions are welcome!)

st2 reminds me a lot of what we're building at https://github.com/keephq/keep (i maintain this oss), there are a few concepts that i really love but the video in the repo really gives me a 90s feelin'

i can't really seem to understand, there's an "enterprise" (with ldap, etc.) version but couldn't find any pricing info

Nope, fully open source - https://github.com/keephq/keep

hey there! we had the exact same problem so we built https://github.com/keephq/keep. it's cool to see that we have very similar syntax (you can see workflows examples here - https://github.com/keephq/keep/tree/main/examples/workflows)

Yo HN!

I've followed https://github.com/Yelp/elastalert which was archived and then forked by https://github.com/jertel/elastalert2 for quite a while, and I'm pretty ambiguous about it. On one hand, it looks like these projects got some good traction, but on the other hand, they feel pretty abandoned these days. I've also tried to reach out to the maintainers and am still waiting for an answer.

Anyway - if you use any of these projects, I'll be more than happy to talk (just drop a comment or send an email to [email protected])

The context is, I'm building Keep (https://github.com/keephq/keep), and I thought these projects could work pretty cool together. So, I'm trying to understand if they are still being used.

hey! would be cool to chat about what you've build. we are currently building Keep (https://github.com/keephq/keep) where you can define alerts as YAML's. would be cool to learn from you.