@x_cli@infosec.exchangeBon, bah j'ai trouvé pourquoi le player de @Castopod (ainsi qu'Apple Podcast en streaming) déconne et me fait des resets de lectures constamment : https://code.castopod.org/adaures/castopod/-/issues/446
Le ticket est ouvert depuis 7 mois sans réponse. Le déploiement de Castopod par docker intégrant nginx est peté...
Vivement la migration Š mon propre service !
@loleg@fosstodon.org"Code is, ultimately, characters on a screen, and software engineers do nothing but hammer that code into shapes that spark Joy and Money. The fear and dread comes from a culture where people feel bad that they can't work quickly enough in the terrible codebase, where they feel judged for slowing down to hammer the code into better shapes that sadly aren't on the Jira board, and where management looks down on people who practice craftsmanship."
-- Ludicity
@bert@recurse.sociali stayed up working on it 2 nights ago and then spent an hour yesterday putting the finishing touches on it (preserving old URLs, etc).
total time invested: 8 hours
lines of code written: 160 (74 Go and 86 shell)
new things learned: 2
satisfaction: priceless
@blakes7bot@botsin.space#Blakes7 Series B, Episode 05 - Pressure Point
TRAVIS: Now, Kasabi, listen to this: was the homing beacon to transmit in a code pattern?
KASABI: Yes. It was pulse, three long, two short, recurring. [Servalan prepares a final dose of the drug. Travis moves to stop her, but Servalan slaps him off and administers it to Kasabi.]
https://blake.torpidity.net/m/205/188 B7B1
@blakes7bot@mas.torpidity.netSeries B, Episode 04 - Horizon
AVON: What did it say - decode.
ZEN: It is in Federation code nine. Message reads, "Top priority signal to any Federation pursuit unit, from Kommissar, planet Horizon. Request assistance. Ruler of Horizon unreliable, am disposing of him. Rebel spaceship at grid reference ten by thirteen double-u zed. Request you destroy this spaceship at once. Also inform Federation Central Control of this action. Await confirmation."
@loleg@fosstodon.orgOne week to go with last places up for grabs! Join us at DINAcon 2024 next week in Bern to hear about:
💠 AI in Parliament: A Roadmap for the Parliamentary Library { Jacqueline Kucera }
🌸 How can large language models be used for sustainable procurement? { Marcel Gygli, Luca Rolshoven }
🌿 Source code sovereignty: local alternatives for an independent digital future { Tobias Brunner }
🧑⚖️ My workshop on open source contracts with Simon Schlauri
🌃
@x_cli@infosec.exchangeUnpopular 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
@loleg@fosstodon.orgAn in-depth review of the AsciiDoc workshop with #SimplexaCode at #CHopen #WorkshopTage 🔖 with lots of links on the design of impactful software documentation
@x_cli@infosec.exchangeL'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
@x_cli@infosec.exchangeQuestion about #Caddy: Does the acme_server db increase in size until disk saturation or is there a pruning mechanism somewhere to delete expired certificates?
I could not find any option regarding pruning, in the Caddyfile config, nor in the JSON config, and I failed to spot any in the source code...
I have a db file still containing certificates that are several months old. The db file was stored in a volume with very limited size and the db ended up filling it entirely (> 100MB) for 20 ACME clients. Chaos ensued.
#infosec #acme #devops
