VSphere Is Still Pretty Great, But...

Content PING 3y Bear in mind, it could simply be a books licensing corporate acquisition, like Microsoft acquiring Mojang. 11 perthguppy 3y That's what Microsoft has said this acquisition is. GitHub will operate independently and their ceo will be replaced with the former Xamrin CEO while the former GitHub CEO is becoming a Microsoft fellow under the SVP for cloud cyanydeez 3y and then a code helper will appear in vscode in a few years a seriptiously borrow peoples code to 'help' you 43

Content I Am Devloper iamdevloper 8h Bored? Figure out how you'd explain Docker to someone from the 1920s. 116 17 517 3.202 Q Jace ShitfaceJace In risposta a iamdevloper You can roast a pork and bake a cake in the same oven without either tasting like the other. v

The perfect alibi. Your manager wants you to work, but GitHub is down, which means you literally cannot push code, pull requests are impossible, and your entire CI/CD pipeline is about as useful as a screen door on a submarine. The boss storms in demanding productivity, and you just casually deflect with "Github down" like it's a get-out-of-jail-free card. Manager immediately backs off with "OH. CARRY ON." because even they know that without GitHub, the entire dev team is basically on paid vacation. It's the one excuse that requires zero explanation. No need to justify why you're not coding—everyone in tech knows that when GitHub goes down, the modern software development ecosystem grinds to a halt. You could be working on local branches, sure, but let's be real: nobody's doing that. We're all just refreshing the GitHub status page and browsing Reddit until the green checkmarks return.

Content Teacher: we installed a program to moritor you during tests, so dont try to cheat!! Me with a VM: 3:34 I am above the law

The classic "too afraid to ask" situation but with a DevOps twist. This is that developer who's been nodding along in meetings for months while everyone discusses CI/CD pipelines, infrastructure as code, and Kubernetes clusters. Meanwhile, they're secretly googling "what does DevOps actually do" under their desk. It's like watching your coworkers enthusiastically discuss quantum physics while you're still trying to figure out how magnets work. The deployment pipeline is breaking? Just smile and say "must be a config issue" while internally screaming.

OMG, the LITERAL DEFINITION of Docker Compose in its most chaotic form! 😂 A truck with a van INSIDE it which has a CAR inside IT! It's like those Russian nesting dolls but for vehicles and with WAY more existential dread! This is EXACTLY what happens when you run that magical docker-compose up command - containers within containers within containers until your CPU starts sobbing uncontrollably. DevOps engineers looking at this be like "yep, that's my production environment on a Tuesday." The nested transportation nightmare is giving me PTSD flashbacks to that time I tried to debug my containerized microservices and found myself 17 layers deep questioning all my life choices!