Hilarious but true programming errors

Programming can be so easy at times. Until someone cares about testing.

I found this hilarious article on how developers make assumptions based on their own culture and mindset. These assumptions turn out to be totally wrong as soon as someone lays a bit more attention on them. But have we not all made one of these errors before?

It’s a fun article with a very true background.

Brand Purpose of commercial brands

Tom Fishburne, a marketing cartoonist I like, posted a cartoon and an article on Brand Purpose, stating that brand purposes can be successful but need to be considered properly. After all, commercial brands need to make money. (Non-profit brands are an exception.)

In order to create a meaningful brand purpose, this article shows what needs to be regarded.

Happy Easter!

Happy Easter! I hope you are enjoying your Easter holidays.

Now that we’re at it: Did anyone else notice that Easter Eggs in software became really rare? Ten years and longer ago, it seemed to be good practice to include an Easter Egg, undocumented feature, or funny functionality in any software. In today’s times, this is not the case any more.

There are probably a series of reasons:

  • Security concerns: Unknown features may include security holes.
  • QA concerns: Unknown features may not be allowed by Quality Assurance.
  • Audit acceptability concerns: Each feature needs to be documented in order to have the software audited or certified.

All these are valid reasons, so probably the era of Easter Eggs is over. Except during the Easter holidays.