Below is a funny song about coding which is sung to the tune of “Favorite Things”. It’s been around for ages, although I always thought the original version was a bit too short and unfocused. So, I’ve re-written it, because I’m a dork, and I’m posting it because I have nothing worthwhile to say today.
Pointers to pointers to printf()-like functions,
Unary minus and nested conjunctions,
Integers, booleans, characters, strings,
These are a few of my favorite things!
Encapsuled functions with routines embeded.
Parallel process to run multi-threaded.
Routines that lighten the processor load.
This is just some of my favorite code!
/* When the bug bites! When the core dumps!
when the code is bad.
I simply remember my favorite things,
and then I don't feel so mad. */
API reference and good indentation.
Pointers to strings that have null-termination.
Callbacks to functions of referencing strings.
These are a few of my favorite things.
malloc() and calloc() and database files.
Error-free coding that always compiles.
Arrays of structures and quick file sort.
These are my favorite things to import!
/* When the link fails! When the code bombs!
When it won't execute.
I simply compile my favorite things
and then I can go Re-boot! */
Batman v. Superman Wasn't All Bad
It's not a good movie, but it was made with good intentions and if you look closely you can find a few interesting ideas.
Silent Hill 2 Plot Analysis
A long-form analysis on one of the greatest horror games ever made.
The Opportunity Crunch
No, brutal, soul-sucking, marriage-destroying crunch mode in game development isn't a privilege or an opportunity. It's idiocy.
Video Compression Gone Wrong
How does image compression work, and why does it create those ugly spots all over some videos and not others?
Trusting the System
How do you know the rules of the game are what the game claims? More importantly, how do the DEVELOPERS know?