The Hidden Face Of Digital Infrastructure

Content Software developers don't spend 8-12 continuous hours at their desk pumping out code every single day. Sure knowing how to code is a necessity in their profession. However, there's requirements to understand. Meetings to attend. Actual human interaction that happens almost as frequently as when they're writing code depending on the company and framework. You have just described run of the mill mediocre coders. Those are a dime a dozen and are easily replaceable and not worth hiring at all based on Elon Musks standards. An elite coder would be someone like John Carmack who would literally spend all day and night coding for months to ship a game. He or she would know all the ins and out of the full stack including both software and hardware and networking. They would build state of the art technology in months when experts thought it would be impossible. And in the end they would ship game after game after game with a team of 6. In this case, replace game with twitter features.

Content Git: keeps an easily accessible version of your entire code history Developer: comments out unused code but keeps it just in case Git:

Content Andy Ryan ltsAndyRyan Me: I'm an expert at identifying birds Her: OK, what about those ones flying over that tree? Me: Yup, they're all birds 8:43 AM Nov 22, 2018 Twitter Web Client

Content Carla Notarobot CarlaNotarobot Astronauts use Linux because you can't open Windows in space 8:57 AM Jan 26, 2021 Twitter Web App 1.9K Retweets 242 Ouote Tweets 10.8K Likes 17

Ah, the classic Scooby-Doo unmasking format but with a cybersecurity twist! Your CPU's pegged at 100% and you're thinking it's just normal load... until you pull off the mask and—surprise!—it's actually a sophisticated state-sponsored backdoor quietly mining crypto or exfiltrating your data. That xz exploit in a nutshell. Eight months of silent operation before anyone noticed. Just another Tuesday in infosec where the real villains aren't wearing monster costumes, they're wearing nation-state budgets.

Content Srigi srigi "Latency Numbers Every Programmer Should Know" It is hard for humans to get the picture until you translate it to "human numbers". 1 CPU cycle Level 1 cache access Level 2 cache access Level 3 cache access Main memory access Solid-state disk O Rotational disk IO Internet: SF to NYC Internet: SF to UK Internet: SF to Australia OS virtualization reboot SCSI command time-out Hardware virtualization reboot Physical system reboot 0.3 ns 1 s 0.9 ns 35 2.8 ns 9 s 12.9 ns 43 s 120 ns 6 min 50-150 us 2-6 days 1-10 ms 1-12 months 40 ms 81 Ms 4 years 8 years 183 ms 19 years 4 s 30 s 40 s 423 years 3000 years 4000 years 5 m 32 millenia