It's Honest Work If You're Honestly Wired

Content Stu Fleming StuFlemingNZ "Hi, I've found a fault with the English language and I need an entomologist" "An etymologist you mean?" "No. It's a bug, not a feature" 2:58 PM 17 Jun 17 ProdrammerHumor.io

Content If you ever feel useless, just remember this code catch (error) throw error;

Content sion Matrix Type I error (false positive) You're pregnant Type Il error (false negative) You're not pregnant

The eternal side project dilemma: two buttons labeled "spend days debugging broken code" or "trash it all and restart from scratch." And there you are, sweating profusely, halfway through the project, calculating if those 47 Stack Overflow solutions you've duct-taped together are worth salvaging. The real genius of side projects isn't finishing them—it's the impressive collection of half-completed Git repositories you'll accumulate. Your GitHub is basically a digital graveyard of "I'll get back to this someday" promises.

Content Cycles in family tree software Asked 12 years, 7 months ago Modified 8 years, 5 months ago Viewed 286k times 1590 votes Locked. This question and its answers are locked because the question is off-topic but has historical significance. It is not currently accepting new answers or interactions. I am the developer of some family tree software (written in C and Qt). I had no problems until one of my customers mailed me a bug report. The problem is that the customer has two children with their own daughter, and, as a result, he can't use my software because of errors. Those errors are the result of my various assertions and invariants about the family graph being processed (for example, after walking a cycle, the program states that X can't be both father and grandfather of Y). How can I resolve those errors without removing all data assertions? C graph cycle assertions family-tree

MongoDB trying to convince you it's built for every app while JavaScript is silently converting its marketing message to [object Object] is the perfect metaphor for web development. Nothing says "I'm ready for production" like your database advertisement turning into the infamous toString() failure that haunts every JS developer's nightmares. If your marketing can't escape type coercion issues, maybe your database isn't really built for "every" app after all...