This page is automatically generated and thus is always up-to-date. All items under each heading are ordered alphabetically by title, ascending.
Blog Posts
- I’ve decided to link to my new (much more active) site after all. Enjoy! 😎
- An expressive system for specifying constraints in code makes reasoning about software much easier.
- Arrogance and humility are equally bad. One should view both others and oneself exactly in proportion to reality, without distortion.
- Breaking my silence on Unified Logic: Fighting back against spam, slander, and spite.
- Contrary to popular opinion, implementation inheritance is not a conceptually correct representation of an “is a” relationship in programming.
- Game Dev Tip #1: How to make changes to gameplay without screwing up existing balance
- Game Dev Tip #10: A game without sound will often feel hollow, even if it is otherwise good
- Game Dev Tip #2: Good art means so much more than just graphical fidelity
- Game Dev Tip #3: Make your game immortal using the power of PCG and random generation
- Game Dev Tip #4: Breathe life into your game with custom shaders and special effects
- Game Dev Tip #5: Make your game fun as soon as possible, or else it may never be
- Game Dev Tip #6: A much faster way of finding the best values to use for parameters
- Game Dev Tip #7: Most game designers should learn at least some computer programming
- Game Dev Tip #8: The more you try to rush the slower you will usually accomplish your goal
- Game Dev Tip #9: Learn how to be creative at will instead of just waiting for inspiration
- I mostly use a different (undisclosed) anonymous/pseudonymous website now.
- I’ve decided to bring back my personal website, but different this time.
- I’ve published a new revised version of my book Unified Logic!
- Igor’s C++ Grimoire: A hidden gem of C++ reference material that not enough people know about
- Lack of proper attention to aspect ratio in game settings
- More academics should self-publish commercially, outside the control of exploitive journal monopolies.
- Most programmers know that “magic numbers” tend to degrade code quality, but are they aware that hard-coding types (i.e. “magic typing”) often does too?
- New posts to this site will be slow for a while, but all is well.
- Programming languages should provide at least two separate switch statement keywords, one for fall through and one for no fall through, instead of forcing one or the other.
- The “single return” (aka “only return once”) style that many programmers use is almost always inferior to a “return early, return often” style.
- Too much fixation on fence-post issues inhibits creativity.