A couple of things sparked my thinking:
- I’m working on simplifying and standardizing a lot of the ridiculously mundane and similar websites we create at my work
- My new roommate is taking some beginning ICS classes and we had a long ICS/design-related conversation recently
So I thought I’d help myself clear up my thinking about good design by just listing some of the basic principles I want to guide my work when I am designing a large-scale system.
- This piece I built here can be reused over there
- Building parts of the puzzle to be functional building blocks in various parts of the site not only reduces the amount of code you have to write, but reduces the amount of testing you need to do, and, if it’s visible to whoever’s using it, creates a comfortable level of consistency throughout your design
- I don’t want to know, as long as it works
- If you’re working through your general logic, you don’t want to have to see the painful details of implementation, so
- The base case should be easy
- I can get tricky without getting messy or hack-y
What else?
Post a Comment