Popular posts

Looks like a poster from he 90s... https://t.co/VarIQFESFv

I may wake up 'one day', go to my Instagram account and either delete it, make it private or remove Instagram from my posting checklist.

I do QA, but I attend UI/UX, design, dev, product events, whenever I can.

Think about it this way: would you rather spend a little extra time now, getting to the bottom of an issue, or waste countless hours down the road, fixing the same problem over and over again?

Sure, it can be time-consuming, but it's absolutely essential. Because without root cause analysis, you're just putting a band-aid on a broken leg. And that's not a sustainable solution.

Root cause analysis is all about digging deep and uncovering the underlying cause of a problem. It's about peeling back the layers and understanding what went wrong so that you can fix it properly and prevent it from happening again in the future.

But here's the thing: without understanding the root cause of the issue, you're just treating the symptoms. And that's a recipe for disaster.

Picture this: you've been working on a project for weeks, and everything seems to be going well. Suddenly, a major issue arises, throwing everything into disarray. Panic sets in, and you start scrambling to fix the problem.

There are some topics that I am extremely passionate about that I've refrained from engaging with them in informal setups. If I am to engage with them, it has to be in a formal setup. The list grows though, albeit in slow-mo.

Did @NotionHQ change its note's font/typeface to Helvetica?

I should assume that @thegodkooper has watched >50% of these shows. https://t.co/vYewiI7ewn

Does @PodcastleAI have live streaming?

Looks like footballers have to randomly select where they will play their penalties, and never have a preferred placement for their shots. https://t.co/ICXGReyMzz

Mbappe should have hit that pass from Dembele without an extra touch.

Zombie APIs are a real problem.