Outlook, Teams, SharePoint and Viva Engage may look like separate services, but they share one provider. When that provider fails, how does your organization communicate?
Replacing servers instead of patching them sounds attractive, but immutable infrastructure doesn’t eliminate patch management. It moves the responsibility elsewhere.
GTA 6 might not be a cybersecurity threat, but collective distraction, sleep deprivation and rushed decisions could expose weaknesses in how we operate critical infrastructure.
From running Eggdrop IRC bots on SUSE Linux 6.2 to watching SUSE cut 10% of its workforce in the name of AI. Is this technological progress, or just another corporate restructuring?
A football table, unlimited holidays and free Friday drinks won’t compensate for a poor salary. What really matters when experienced IT professionals consider changing jobs?
After years of working remotely, corporate harmonisation is bringing mandatory office attendance back. But sitting in an office has never been a measure of productivity.
Put two Linux people in a room and one word is enough. Put a manager in that same room and suddenly you need an interpreter. The interruption is not the problem. The context switch is.
Return-to-office mandates are a systemic failure. Treating human infrastructure with the same flawed logic as bad server maintenance is why IT is burning out.
The Odido breach did not end when the systems were patched. It continued wherever abandoned domains, forgotten mailflows, and expired infrastructure were still trusted.
A phishing simulation showed that even when people know what to do, there is often no correct decision to make. Organisations respond by managing reactions instead of fixing the conditions that caused the problem.
When one person consistently carries operational recovery, troubleshooting and undocumented infrastructure knowledge, organisations mistake dependency for stability.