| Quick links to the five "must read" posts that William highlighted: > FFF #243 - New GUI tileset: Showing off their GUI design document. A MUST READ, if only for a good example of a comprehensive design style that fits the game theme perfectly. (https://factorio.com/blog/post/fff-243) > FFF #176 - Belts optimization for 0.15 : Incredible analysis of transport belts and optimizing their performance. A MUST READ. (https://factorio.com/blog/post/fff-176) > FFF #204 - Another day, another optimisation : Solid technical writeup on how a prefetching optimization patch works across a number of resource-heavy factory builds. A MUST READ. (https://factorio.com/blog/post/fff-204) > FFF #296 - All kinds of bugs : The snippet at the bottom is a perfect encapsulation of their attitude towards problem solving. It’s such a simple concept, just going a little farther, that can take tremendous discipline and focus. A MUST READ. (https://factorio.com/blog/post/fff-296) > FFF #356 - Blueprint library for real : Michal “kovarex” Kovařík, one of the two cofounders, talks about falling out of the development process, losing his sense of purpose, and how playing Factorio with his son brought him back. Reading this one, even through the sometimes-broken English, is inspirational and a wonderful look at how things fall apart and come back together. Like I mentioned in the intro, this is one of those rare, special offerings that is technical in nature but deeply personal and human-centric in form. A MUST READ. (https://factorio.com/blog/post/fff-356) |
> So, I still repeat the phrase: "Crashing on dereferencing null? Just add a null check!" as a reminder to myself and others to always look deeper into why and never stop at the basic symptom of a problem.
I feel this is a very important rule that people often forget - most anytime your "safety" code triggers, something went wrong somewhere else and it can be worth tracking it down.