You went out daydrinking on May 1st, well deserved!
No alerts. No downtime. You know why? Because someone from your team: Wrote the tests. Tuned the alert thresholds. Fixed the flaky deploy. You don't avoid incidents by luck. You avoid them with solid observability.
@GergelyOrosz If you have dedicates QA you create Silos and excuses because you remove the "skin in the game" that product management and developers have.
I'd never run a team with dedicated QA again
#buildinpublic
๐๐๐ We got a lot of customer feedback on missing features for managing schedules, escalations and rotations.
๐๐๐ It's shipped now - with probably the industry-best UX!
https://t.co/gF9qZfzrY6
@alper@rushiv@GergelyOrosz Hey Alper,
I was actually asking myself the same question and was quite annoyed by their outrageous pricing model.
So I decided to build my own competitor: https://t.co/JQTbsYLrGg
If you like, give it a try! ๐
@arnauddsj Building native apps is very slow - at least for me.
I wanted to create the best integration and UX for each platform so I decided to build https://t.co/O4pzXecXPG in Swift and Kotlin.
Not sure if it was the right decision.
Also, SwiftUI seems still very unstable currently.
๐ค It's super simple to connect #site24x7 with https://t.co/O4pzXecXPG.
๐ฅฐ A quick integration guide is now available as a blog post:
https://t.co/ZcBo2nP6ly
#buildinpublic
๐คWho has heard of the barber paradox? https://t.co/lmJdQtptBh
I got lot of feedback from #HackerNews adressing the importance of the reliability of https://t.co/O4pzXedvFe!
โ Added public status page: https://t.co/hKTHihlJvj
โ Kudos to #buildinginpublic