Recent submissions

Comment · 1 year ago
Thank you...reading from you guys has been great so far
Comment · 1 year ago
Love this...meaning simply reusing a quick fix is definitely not ideal to help identify root causes...LLMs have come a long way and I feel with adequate tooling and context(the rich ticket data you mentioned), they could really be a great solution or at least provide even better context to developers
Comment · 1 year ago
Thanks tracker...very insightful
Comment · 1 year ago
Okay, thanks a lot, didn't see it like this
Comment · 1 year ago
Thanks...thinking about using AI to learn about what is actually "important" to the developper or team...tracking the alerts that actually lead to manual interventions or important repo changes...this way, we could always automatically send alerts to tiers...just thinking
Comment · 1 year ago
So it's really a manual and iterative process....means there should be room for something to be done
Comment · 1 year ago
I wasn't building one exactly for me, but I believe not all devs have a team available to monitor the deployments for them...and sometimes centralized observability could really be a plus and ease the life for a developper....just being able to vizualise the state of your multiple vps deployments from your single pc without logging into you provider accounts should count for something I belive....this is without any form of anomaly detection or extra advice about your deployment state...I wanna believe this is useful but again the critique is welcome

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton