anthonySs
expected way more from a refresh tbh
same thing happened with crypto - the underlying technology is cool but the community is what makes it so hated
would love to know your actual day to day use case for what you built
i just got an m5 max with 128gb of ram specifically to run local llms
OpenUI: Open-source control center for AI agents
Will be using this a ton in the future
Show HN: SimKit – TS framework for testing and running AI agent simulations
Hi HN, I’m Anthony from Fallom & we built SimKit (https://github.com/Fallomai/simkit ), an open-source TypeScript framework for running and testing AI agents in simulations. It’s MIT licensed.SimKit gives you a simple tick-based loop where agents can act, state evolves, and you can track everything deterministically with seeded randomness. It has built-in OpenTelemetry so you can see...
Fallom – Coding interviews that let you use AI
So we were recently watching a YT video about devs cheating on coding interviews that said it's estimated that nearly 50% of developers use some kind of AI assistance to cheat on tests.It sort of makes sense, it's like the calculator all over again... we want to gauge how well a candidate actually understands what's happening, but it's also unrealistic to not let them use the tools they'd be...
Show HN: Instant context when paged on-call
We created a tool that saves time for on-call engineers.Basically as soon as you get paged in Slack by Jira or Pagerduty, we respond with:- Past similar issues that might provide context - Relevant solutions from your company's confluence runbooks - POCs from other teams who may be involved in the issue - The ability to one-click create a war room - Instant setup. Just invite Pandem to the...
Pandem.dev - Make on-call less shitty
The wife and I are both devs, and we both agreed that being on-call is probably the worst part of the job.
We decided to build something to try and make on-call issues a bit faster to deal with.
Basically Pandem.dev is a tool that you add to your company's Slack channel and it responds with useful information whenever an on-call ping comes in.
We basically index all previous incidents and when any new on-call tickets come in from Pagerduty, it'll respond with a list of related past issues.
We're also working on allowing the model to be trained on your on-call runbooks and docs, so it can suggest solutions and starting steps to diagnose or debug whenever a new issue comes up.
Let me know what you think, any feedback is appreciated!