-
@GalaxyKate i think my number one hot tip is to talk to people about why they want a feature and what they hope it will do, even beyond the things they have written down as requirements. it makes you much better at guessing what kind of extensibility the system will need.Permalink Look on archive.org
❤️ 8 Favorites Mood +7 🙂
-
@GalaxyKate a very practical tip: instead of adding another boolean field to combine with the first one, turn it into an enum instead and explicitly list out the states the thing can be in.Permalink Look on archive.org
-
@GalaxyKate also, that most architecture questions are about where the state lives, and what thing should own it. there are lots of different answers here, but some good rules of thumb are: - as few places as possible - as close as where it's used as possible - explicit, rather than implicitLook on archive.org