Viewing profile — mehdig10

Hey, in the vast majority of push-based systems (think slack, shopify, or even custom entreprise ones) there are quite a lot of things you end up building (bufferization, errors, r…

Hey, in the vast majority of push-based systems (think slack, shopify, or even custom entreprise ones) there are quite a lot of things you end up building (bufferization, errors, r…

Thanks ! Since we're storing events in an intermediate collection and you consume them at your own rate, there is actually no need for this. They will just pile up until you can co…

Well yeah for a simple queue where messages live in memory and disappear once consumed there are plenty of technologies that work (rabbitmq, redis...). Here is the goal is not to j…

Hi HN! I built Basehook to automate common webhook patterns I've had to manually implement across multiple projects: buffering, smart deduplication, and payload inspection. The cor…

Uses an LLM to identify where tables actually start/end in Excel/CSV files, then extracts clean, typed data. Handles all the messy formatting (currency, percentages, different numb…

I've been building B2B SaaS for 10 years and noticed the same loop: support asks "what's happening with customer X?", eng drops everything to check Grafana, pastes a screenshot in …

yeah promql is a nightmare... don't know if datadog's better at that

yeah but in my experience it's either the information is very shallow (like status page) or too technical (like traces). i feel like non engineering parts of the org still want to …

Hey, We have a ton of logging/metrics in kibana/prometheus, so whenever there is an issue with some client data feed or whatever, support asks us to check what happened. Since the …

We built George because we loved handling day-to-day work in Slack, but wanted a little bit of structure without any of the overhead of a ticketing system. George is a lightweight …