Tootfinder

> A User's Guide to Jabber/XMPP
by *contrapunctus*
https://contrapunctus.codeberg.page/xmpp.html
> I read it and its really complete and informational
Hackernews discussion -

#Blakes7 Series A, Episode 05 - The Web
BLAKE: I don't give a damn about your power cells. There's a friend of mine out there.
[He turns and runs for the main entrance of the complex. Geela and Novara intercept him near the exit.] NOVARA/GEELA: [Simultaneously] We will help.]
https://blake.torpidity.net/m/105/455 B7B1

Wonderful bloopers from Curb Your Enthusiasm, VEEP, How I Met Your Mother, Always Sunny in Philadelphia, Everybody Loves Raymond, The Office, Seinfeld...
"Funniest TV Show Bloopers Compilation"
https://youtube.com/watch?v=DYWDYcgnGK8&si=gAi52uF…

Series A, Episode 08 - Duel
VILA: That's not what I meant.
AVON: No, he was calling me a machine, but since he undoubtedly defines himself as a human being, I shall choose to accept that as more of a compliment than anything else.
https://blake.torpidity.net/m/108/38 B7B6

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