Poor Kids

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 Did somebody say 'communism'? github SOCIAL CODING BUILD SOFTWARE BETTER TOGETHER

Content BirdSong 6 57m Java "Perl - The only language that looks the same before and after RSA encryption" 5

Content Al will take my job natic Al will take my job GEN

Ah, the infamous bug report form that gets progressively more hostile as developers lose their will to live. The eternal cycle: User submits ticket with "it doesn't work" as the only description. Developer politely asks for details. User ignores all fields and resubmits "still doesn't work." Developer's blood pressure rises. Form evolves to include increasingly desperate pleas culminating in that final checkbox that might as well say "I solemnly swear I'm not a complete idiot." Ten years in tech and I've never seen a properly filled bug report in the wild. They're like unicorns - mythical creatures that would solve problems in minutes instead of days. But hey, who needs sanity when you can have the thrill of debugging blind?

Content How IT people see each other DEVELOPERS DESIGNERS PROJECT MANAGERS QA SYSADMINS SEEN BY DEVELOPERS SEEN BY DESIGNERS SEEN BY PROJECT MANAGERS SEEN BY QA SEEN BY SYSADMINS