This Really Happened

Content tihorner 18h wait you can actually download more ram if you set up google drive as swap space 29 17 203 772 tihorner perfect tjatj-x1c7 Filesystem ludev tmpfs Itmpfs Itmpfs Itmpfs devnvmeOn1p2 devnvmeon1p1 Itmpfs gdrive: swap tjatj-x1c7 df -h devmapper vgmint-root 915G Size Used Avail Use Mounted on 7.7G 0 7.7G 0 dev 1.6G 1.9M 1.6G 1 run 38G 831G 5 7.7G 159M 7.5G 3 devshm 5. OM 4.0K 5.OM 1 runlock 7.7G 0 7.7G 0 sysfscgroup 705M 409M 246M 63 boot 511M 31M 481M 6 bootefi 1.6G 80K 1.6G 1 runuser1000 1.0P 471G 1.0P 1 hometjgdrive 10:14 PM - Dec 14, 2021 Twitter Web App

Cloud migration in a nutshell: Backend service owners clutching their precious code like a hairless cat hoarding gold coins, while completely ignoring those pesky validation steps scattered on the table. "But it works on my machine!" they hiss, as the DevOps team sighs for the 47th time today. The validation steps might as well be invisible—just like documentation and proper error handling. Who needs testing when you've got blind faith and a prayer to the server gods?

Content grey jena tweetsbyweber Dear recruiters, if you are looking for: - Java, Python, PHP - React, Angular - PostgreSQL, Redis, MongoDB - AWS, S3, EC2, ECS, EKS - nix system administration - Git and Cl with TDD - Docker, Kubernetes That's not a Full Stack Developer That's an entire IT department

Content Every data scientist has a tab open to Stack Overflow definitive collection of coding Ensure vour company stavs on course 96 Explore technical topics and other disciDlines acIOss lU OSA

The bell curve of architecture wisdom strikes again! On the left, we have the blissfully ignorant junior dev who's happy with a monolith because they don't know any better. In the middle, the insufferable mid-level architect screaming about microservices like they've discovered fire. And on the right, the battle-scarred senior who's been through enough distributed system nightmares to circle back to "just use a damn monolith." Nothing like spending six months untangling a hairball of 47 microservices communicating through a message queue that nobody understands anymore just to realize it could've been three functions in one repo.

Content Always has been Wait it's all computers? ProarammerHumor.io