LLMs are like doctors who’ll write the prescription you hint at.
Posts by Maximilian Kaske
New short from our first podcast with @mxkaske.dev
omg I‘m visualizing it
The reason why openstatus is remote
dont crash
The first @openstatus.dev podcast is here 🔥
youtu.be/AjXrXlOYAoM
Took us only 3 years. 🚀
screenshot of max and me recording a podcast with riverside
We are trying something new wiht @mxkaske.dev
first @openstatus.dev podcast soon 🚀
“last 7d errors on api” ✨
natural language filters for data tables powered by @vercel.com ai gateway
→ logs.run/i
openstatus new cli
Just pushed a new version of @openstatus.dev CLI
follow clig.dev guidelines
😭
Stop hand-coding data tables.
We've refactored the code base to make it easier. Including a shadcn registry and an agent SKILL[.]md.
→ logs.run/docs
It's not a library. It's a playbook.
If you're ever looking for status page components, we've published a @shadcn.com component registry built specifically for that.
If you have a website and not using @openstatus.dev speed check you're missing out 🤯
I was able to improve the performance in some regions by up to 150x 🤯
They have an AI skill you can install to let agents check the performance in multiple regions at once.
Link ⬇️
that’s the way
my life in a nutshell rn
yes
time to market it
Status pages started simple @openstatus.dev: a page showed the uptime of a monitor. That assumption shaped our entire data model - and eventually became our biggest limitation.
Not anymore.
openstatus.dev/blog/status-...
shipper and sipper
A component form card listing the current status page components. An open dropdown suggests you can connect monitor and static components while third-party components are yet disabled.
its been a long way - we are going to improve the status page experience with page components
do no mistakes
💯
Noticing the same esp for frontend code.
Different story for backend, which can also be more unit tested so ai is less prone.
💯
most people are forced to use it 😂