Tomorrow is the day @DevOpsPorto gets back to in-person events.
@desfocado will moderate a panel that will include myself, @phcrva and @waldyrious around technical writing.
Joins us at Selina Navis CoWork.
https://t.co/LAcGhw19jK
Even a very low requests/second metric is way better than crowing about requests/week or requests/month.
Dear startups (and even non-startups) - you can still work on very interesting technical problems and be growing very fast, even if you’re not gigascale.
“We had x incidents this month.”
“How many were prevented?”
When leaders insist on incident frequency as a goal or metric, remind them the denominator is missing.
When it comes to incident write-ups, the bar is so low in tech (most are written to be *filed*, not to be actually *read*) that we’ve seen ones that don’t give the author’s name, the data they’re basing their write-up on, or even the # of people who responded to the event. (!)
@dj_jorjinho @reistiago re: mis-addressed emails, I think it’s a very common “Layer 8” type thing — specially so addresses with common names. I think @kintoandar also suffers from this.
You guys should try having an unpronounceable email address! Works like a charm
@niallm@luisbruno 'a.b' seems to be special syntax for Class C networks, 'a' being the first byte. It's discussed here: https://t.co/CouxmuGeHH (image via one of the links on that page.