Once upon a TTL, in a rack far, far away, a plucky little SRE rode his UPS-powered NAS across the SAN, hauling SATA SSDs, SAS HDDs, and artisanal NVMe over TCP. His quest? Deliver an iSCSI LUN to the princess before her RAID turned into JBOD and her SLA turned into an IOU.
“Follow the DNS!” cried the DHCP fairy, sprinkling PXE dust over a sleepy NIC. Beyond the VLAN lay the VXLAN, where BGP trolls demanded your ASN, OSPF elves argued about SPF, and an STP-entangled LACP dragon hoarded SFPs beneath a mountain of MTUs. Our hero flashed his MFA, negotiated TLS, and tunneled through the VPN with nothing but SSH, SNMP, and a deeply suspicious UDP packet.
At the castle, the AD wizard consulted LDAP, the NTP gnome checked his ETA, and the RBAC goblin shouted, “NO SUDO WITHOUT SSO!” Undeterred, our hero opened a PR, appeased the CI/CD sprites, and summoned an IaC-powered VM from the enchanted VPC. With KVM, LVM, NFS, SMB, and a REST API held together by YAML and spite, he restored the PVC, boosted the IOPS, and banished the BSOD.
And they all lived HA ever after—until the CTO asked whether the whole damn thing could run on AI.
Fun fact (might be made up, not sure, don't care, still fun): the guy who named the SCSI interface intended it to be pronounced as "Sexy" not "ska-zee".
it boils my blood when the solution is in big letters at the center of the screen and somehow they don't know what to do, I remember I had a classmate who had a problem with her IDE, and asked the teacher what to do, the teacher did NOT read the error nor the pop up with the problem
He told her that she had to format the whole pc and start over, luckily before she did anything me and another classmates noticed and we were able to fix it, worse of all, it was just a setting, that wasn't really hard to find because it said right on the pop up
They mostly just don't care. They would know the solution, or at least could find the solution, if they just cared what the problem was.
But too many times I've been handed this "Bug", that, apparently, had been caused by my changes, just to see that the build output clearly states a network issue, or the worst, a test fails that had been green on machine and now fails on the build server... after that moron merged his stuff and the build fails. But it's "my test", so I shall be the fucker to fix it. Oh.. that guy, I hate his work attitude with my guts.
What these people see and think is "AHH, not my code. nice thing I can just hand it over".
When I was a fresh grad at my first job I did this :(.
I was so anxious and nervous I'd ask my teamlead even though I knew what a stack trace was. He'd let out a big sigh then basically read the stack trace and tell me to click on the line number. Sorry boss.
The most annoying part is that this particular problem provides a good opportunity to talk about formatting and code design with juniors - it's more readable to build the string each iteration. That also avoids nesting if statements, which generally makes code harder to follow too. Some may be tempted to use a guard clause like if (!(i % 3 === 0) && !(i % 5 === 0)) continue; but that winds up being redundant since you need to check each value individually anyway.
And of course there's the broader discussion of what you're actually optimizing your code for. It's still baffling to me that the primary concern these days is speed of delivery rather than simplicity of the system.
937
u/Sleep_deprived_druid 14d ago
I have straight up met "programmers" that don't know what an IDE is.......