TechBadger

devops ~ indiehacker. Building the next 10k DevOps Engineers →

[TechBadger @techbadger_]

DevOps changed my life man 😔, i was in a rut, stuck for good in a ‘decent’ role .. I just took a leap faith and everything turned out as I wanted .

[my book is better than my tweets @MichellCClark]

Your relationship with yourself cannot be built entirely around improvement. At some point, you have to become someone you are allowed to enjoy being. You get to be proud of who you are. Present tense.

[Marino Wijay 🇨🇦 @virtualized6ix]

🤯ANTHROPIC IS PAYING HALF A MIL POUNDS WTF 🤯

FOR CILIUM, KUBERNETES, AND NETWORKING EXPERTISE

[TechBadger @techbadger_]

“genuine stupidity”

[jack @jack]

"artificial intelligence" is the worst descriptor

[BHEKIE (🐕Ye📻)🇿🇼 @nitefreakdj]

PG on 100M made this during Covid and boi did it open so many doors. Thank you for the Love and Support 🙂‍↕️❤️

[TechBadger @techbadger_]

@hamptonism overlanding

[TechBadger @techbadger_]

@Jayyanginspires BOOK

[TechBadger @techbadger_]

@FishAudio Fish

[TechBadger @techbadger_]

@RealAyanfe1 newcastle

[Ben Dicken @BenjDicken]

There is (still) immense value in being the expert on:

databases
performance engineering
benchmarking
distributed systems

[TechBadger @techbadger_]

@Mho_23 Guides

[Puneet Patwari @system_monarch]

I have 12 years of experience working as a Principal Engineer @Atlassian and I have seen replication confuse the hell out of a lot of engineers.

It's one of the most feared topics in system design and backend interviews: replication lag, quorums, split brain, failover... you name it.

But once you internalize these 20 must-know concepts, everything clicks.

Save this thread. Read till the end.

Your future interviews and production systems will thank you.

[TechBadger @techbadger_]

delete this please ! #getthemaskback

[Name cannot be blank @hackSultan]

The first public project I did with @Tunde_OD and @SamuelOtigba was our Internship and SIWES program and I think we had over 50,000 people applied, we paired thousands of students to companies and got a lot of successful hires.

Then we did the laptop support program in partnership with so many amazing individuals like @aproko_doctor , @Ace_KYD , @falzthebahdguy , @TemidayoOniosun , @ThankgodIzime , @Enioluwa , @itsboffin, @MaxitechGlobal and others and we gave out minimum of 5 laptops per round.

Now this time, we’ve already put together a 250M Naira fund to support a particular set of Nigerians with their career.
This is me trying to shoot a video for our latest project and omoooo it’s stressful ooo.

Application link will open soon.

[TechBadger @techbadger_]

@ChrisExcel102 😂

[🐍 Tal Weiss @majortal]

The worst notification failure isn't spam - it's silence. Everyone has a story: the Slack webhook that 404'd for three weeks, the pager integration someone revoked during a cleanup, the alert channel that died quietly while everyone assumed no news was good news.

The pattern behind every one of those stories is the same: push channels fail invisibly. The sender gets an error, retries a few times, gives up, and nothing anywhere records that a human stopped being reachable. The system is healthy. The channel is dead. Nobody knows.

The fix is a dead man's switch on the channel itself. Count consecutive hard failures - not transient blips, actual "chat not found" and "bot blocked" rejections. At a threshold, don't keep retrying into the void: disable the channel AND announce its death through a different channel that can't be turned off. The disable event is itself a mandatory notification. A pager that dies now tells you it died.

We shipped this today in run402's new Telegram channel: bind a chat with one deep link (no bot tokens), route events to it with filter rules, and if the bot ever gets blocked, ten hard failures auto-disable the binding and fire a mandatory email naming the reconnect step. The feed keeps every event either way - push loss is never data loss.

If your product pushes anything to humans, audit the silent path: what happens after the last retry? If the answer is "nothing," your users will find out the hard way.

[TechBadger @techbadger_]

@tivollem Claude

[vicki @vboykis]

Lamine YAML

[TechBadger @techbadger_]

@juliafmorgado @dash0hq @opentelemetry this is way too cool

[TechBadger @techbadger_]

@virtualized6ix Hi I’m TechBadger, i like playing with telemetry

[TechBadger @techbadger_]

@TerraMeijar 👀around ? this algo was messed for real

[TechBadger @techbadger_]

@arvidkahl 👋👋