Is "decentralizedwashing" a term yet? See recent #bluesky discussions like: https://social.wildeboer.net/@jwildeboer/113487613965056474
From #AnnafromUkraine @AnnafromUkraine@youtube.com
RUSSIA'S ECONOMIC COLLAPSE IS COMING SOON. Vlog 832: War in Ukraine
Western analysts believe that the russian economy is on the brink of disaster despite official reports of low inflation and economic growth. In the 2025 budget, #russia
Series B, Episode 04 - Horizon
BLAKE: They don't.
GUARD: You. [Signals to Selma] Come with me.
https://blake.torpidity.net/m/204/475 B7B5
L'infrastructure immuable ! Mais qu'est-ce que c'est que ce truc ? Et pourquoi c'est mieux qu'#Ansible ?
Envie d'en savoir plus sur l'un des futurs de l'Infrastructure as Code (#iac) et l'impact positif en sécurité que cela peut apporter ?
J'ai sorti un épisode de podcast Š ce sujet : #infosec #devops
Series B, Episode 05 - Pressure Point
AVON: [Completes his dash with Gan catching him. Places his hand on Blake's arm.] Thank you.
BLAKE: [To Vila] How long?
https://blake.torpidity.net/m/205/449 B7B5
Unpopular opinion on software development
Yesterday, I came across CI cultists.
They were preaching one should merge in main multiple times a day.
Quite frankly, I associate this behaviour to lab rats compulsively clicking the button to get gratifications (please don't do that to rats).
I think developers should refrain from becoming merge junkies. Code review is essential for good code quality. Automated tests suck at detecting logical errors, security vulnerabilities, and even decent code coverage.
Also, I believe pair programming is absolutely not a strategy to allow continuous integration. Everybody involved in the development process is drunk on their own bullshit reasons they made up to justify their poor design. Either the code review should be done by someone else, or the developers should sober up for a fortnight before code reviewing their own code.
PS: I am a software developer. I get drunk on my own bullshit as well.
#software #development #ci #codereview