Put It Back Now

Ah, the joys of operating system documentation, where perfectly innocent process management terminology sounds like instructions for a serial killer. In Unix/Linux, "child processes" are just programs spawned by parent processes, and "killing" them is simply terminating them with commands like kill -9 . Nothing says "experienced developer" like casually telling your coworker you're "killing orphaned children" and "dumping core" while the new intern slowly backs away in horror. This is why programmers shouldn't write their own employee handbooks.

Content The Future Programmer TheProgrammerMe Someone literally bought a domain to do this guthib.com You spelled it wrong.

Content spacedogetwit: el.. . 2h No comp Sci degree? Here's what the industry has to say about that O 1 17 spacedogetwit: el... 2h Get absolutely fucked my dude. You think we're just handing out jobs to people who watch YouTube videos? 17 spacedogetwit: el... 2h What's that? You have an extensive set of open source projects you've worked on? If other people won't pay you to work why should I?

Ah, the classic file system loophole that no cloud provider wants you to know about! Why pay for extra storage when you can just cram all your data into the filename itself? Sure, changing the actual filename doesn't affect file size - that would be too easy. But encoding your entire database as a series of increasingly monstrous filenames? Pure evil genius. Somewhere, a filesystem engineer is having heart palpitations just thinking about this. And yes, there's probably that one developer who's actually tried this in production. We don't talk about them anymore.

Content WHEN ALINUXVIRUS FINALTY INFECTS A COMPUTER: CALLED MY MOM, TOLD HER I MADE IT

Content TOSS STDS You know CSS? Can you ever really know CSS?