All Modern Digital Infrastructure

Content What are the 7 deadly sins of programming? John Purcell, Creator of CaveOfProgramming.com Answered OCt 30 : Upvoted by Hasis A Munaimin, IOl participant 43, 44. 45, ACM. ICPC World Finalist 2016 and Jessica Su, CS PhD student at Stanford 1. Using spaces instead of tabs. You should always, always use tabs, not spaces. 2. Using tabs instead of spaces. You should always, always, use spaces. 3. Not using auto-formatting. Forget all that tabsspaces rubbish, what's wrong with you - auto-format your code and then people won't have to look at your weird ideas about brackets and spaces. 4. Using IDEs, which have features such as auto-formatting and nicely- coloured buttons. All code should be written in vi or Emacs, thus ensuring the purity of the programming experience. 5. Not using IDEs. No-one wants to pay for all the time it's going to take you to type things that you could have done at the click of a button, or scroll up and down using some ridiculous key combination invoked using LISP. 6. Failing to learn C and C. It's really important to learn the two absolute essential languages. You think Java is just as good? Fine, write me a real-time control system for racing cars in Java and I'll believe you. 7. Learning C or C when you could be using something modern like Java instead. Admit it - all your schedules involving C or C overrun by five years. And even then the software turns out to have critical flaws that Java would not even have allowed vou to create. 8. Overrunning the end of an array. 124.8k Views 3.448 Upvotes

You know your infrastructure is in great hands when Cloudflare goes down more often than your college roommate's commitment to leg day. The kid pointing at the 500 error is every developer frantically refreshing isitdownrightnow.com, while the teacher represents your boss who's seen this exact presentation seven weeks in a row. "It's not our code, it's Cloudflare!" becomes the most overused excuse in standup meetings. Plot twist: sometimes it actually IS Cloudflare, and you get to feel vindicated for approximately 3 minutes before realizing half the internet is down with you.

This meme perfectly captures the chaotic reality of network protocols for programmers! 😂 The joke here is that when someone says "Please follow protocol," they're asking you to follow a set of rules or procedures. But for programmers, the word "protocol" triggers an existential crisis because there are so many different networking protocols to choose from! The image shows a menacing character (from what appears to be an anime) with various protocol names floating around - TCP, UDP, HTTP, MQTT, Bluetooth, etc. - representing the overwhelming number of communication protocols programmers need to deal with. It's like asking "which restaurant should we go to?" and getting bombarded with every restaurant in a 50-mile radius. The meme perfectly captures that moment of "Wait, which protocol are you talking about? I know like 20 different ones!" Every programmer who's had to work with networking or IoT has felt this pain - staring into the abyss of protocols and wondering which one is the right choice for their specific use case. And just when you think you've mastered them all, a new one appears!

Remember when you bought software and it just... worked? No phoning home, no "verify your license," no mandatory updates that brick your workflow. Now your $2000 Adobe subscription needs to check in with the mothership before letting you edit a PNG. Your smart fridge won't dispense ice without WiFi. Your car's heated seats are locked behind a monthly paywall. The shift from ownership to perpetual rental is real. You're not buying products anymore—you're leasing access to features that physically exist in hardware you paid for, but are artificially gated by DRM and always-online requirements. It's the SaaS-ification of everything, where companies realized they can extract infinite revenue from finite purchases. The kicker? When their servers go down or they decide to discontinue the service, your "purchase" evaporates into the cloud. You don't own your games, your music, your tools—you're just renting them until the company decides otherwise. Welcome to the future, where everything is a service and nothing truly belongs to you.

Content Zack Whittaker zackwhittaker For fuck sakes, IBM. Why would you host your status page on your own cloud? X 504 Gateway Time-out cloud.ibm.comstatus X 504 Gateway Time-out nginx

In a world where everything is becoming "as a Service" (SaaS, PaaS, IaaS), someone finally created the most useful service of all: rejection automation. This person's hoodie proudly declares their business model - saying "No" so you don't have to! For just $4.99/month, they'll decline all your meeting invites, reject pull requests with insufficient tests, and automatically respond "Have you checked Stack Overflow?" to all questions. The enterprise tier includes custom rejection templates and a "Maybe Later" option that recursively schedules itself to infinity. The irony? Their API documentation consists of a single endpoint that always returns 403 Forbidden.