Refactoring: The Circular Saw Of Doom

Content Adam the Automator adbertram Does "fixed shit" count as a good Git commit message? Asking for a friend. 21319, 5:02 PM

Content jaredpalmer.eth jaredpalmer TODO: fix later 21:28 14 Jan 22 . Twitter for iPhone

The tech world's circle of hate continues! First, we collectively decided Vibecoding was the enemy - you know, that annoying "just vibe with the code" approach where documentation is optional and chaos is encouraged. But wait! Look at that 3251 error code getting violently stabbed in the last panel - that's tomorrow's villain waiting to be despised. Every six months we need something new to blame for our suffering. Remember when we hated jQuery? Then MongoDB? Then microservices? Then blockchain? The cycle never ends because it's easier to hate the latest framework than admit we're building increasingly complex solutions to problems we created with our previous "revolutionary" approach.

Content GOB printi Look what they need to mama mimic a fraction of our power

The eternal battle of Python dependency management summed up in one religious allegory. The devil tempts you with the convenience of globally installed packages - just one "pip install" away from corrupting your entire system. Meanwhile, Python Jesus advocates for the righteous path of virtual environments, keeping your dependencies organized and your soul clean. 105,889 globally installed packages is basically a deal with the devil that future you will have to exorcise during your next migration. The path to salvation is just a "python -m venv" away.

Content 8 points 11 hours ago but if you have a bank or similiar and need 99.99 uptime no matter what happend, then an IBM mainframe is a very good choise. And IBm have a massive support organisation if you pay for it, they fix anything anytime of the day. permalink source embed save save-RES parent report give award reply hide child comments -2 points 11 hours ago (last edited 11 hours ago) You could also just hire a regular devops team with college-taught skills and have them build your redundancy on readily and widely available hardware backed by open source technology, which won't get you vendor-locked like the poor souls in the banking world You should avoid it choosing proprietary IBM technology at all cost. It's almost always a very bad choice. The only good reason for doing so is if you're already prisoner from having chosen IBM proprietary technology in the past and your team existing structure is already constructed around it. permalink source embed save save-RES parent report give award reply hide child comments 12 points 10 hours ago I'll take "who's never worked in a company with more than 6 people" for 100 permalink source embed save save-RES parent report give award reply hide child comments -3 points 1Pours ago My ass Every company under the sun is doing running and then monitoring their systems using an open source stack. Docker. Ansible. Jenkins. Nagios. Monit. Prometheus. K8. Grafana. Or a system backed by it. You've either only worked in very niche bubbles of the tech world or you don't know what you're talking about nermalnk source emhed save cave-RE narent renort give award renly hide child comments 13 points 8 hours ago Clearly you're not working in any serious company if they're relying on open source software. Dermalink source embed save save-RES parent report give award reply hide child comments ProarammerHumor.io