Stackexchange

Content How it feels when you're 8 hours into what should have been a 30 minute job so you just sit there questioning the meaning of life.

Content Thief Murderer He didn't close the file after performing IO Operations

Content Coworker: so how did you solve the bug? Me: Ostrich algorithm From Wikipedia, the free encyclopedia In computer science, the ostrich algorithm is a strategy of ignoring potential problems on the basis that they may be exceedingly rare. It is named for the ostrich effect which is defined as "to stick one's head in the sand and pretend there is no problem". It is used when it is more cost-effective to allow the problem to occur than to attempt its prevention.

Content 6:12 4 Tweet Corey Quinn QuinnyPig In principle I like the idea of a 4-day work week, but l'm not sure a lot of engineers would be willing to increase their workloads by that much. 6:12 PM 6822 Twitter for iPhone I View Tweet activity 17 Who can see this Tweet? You and your Super Followers can see this Tweet

Ah yes, the classic "let me massively over-engineer this simple problem" approach. Nothing says "I'm a serious developer" like creating an entire utils file just to house that one sad, lonely function that converts a string to uppercase. It's like buying a mansion for your pet rock. Sure, your code structure might look impressive in the pull request, but we all know you're just trying to make those 3 lines of code feel important.

Content Tell me a joke Ok, here you go: Have you ever tried to eat a clock? 15:31 no OK