A taxonomy of what we mean when we talk about "resource-constrained" might be helpful for those seeking to gain this knowledge. Limited CPU, RAM, etc are the obvious contenders - but then there's also "resource-constrained" as in "I'm the solo dev of this project and have 5 hours in a good week to work on it", or "this runs in a weird place without Internet that I only get access to twice a year". I've been in all of these situations, sometimes multiple at the same time, and they've been great forcing functions to find new paths towards simplicity.