Just random rules that I think are good to follow.
This probably only makes sense to me.
- When planning, always try to include the next deepest thing.
- Listed out tasks? Estimate length of tasks. <- Estimated lengths of tasks? Make a comprehensive timeline.
- Estimated the timeline? List out risk factors that could jeopardise this (external dependencies).
- It’s never a bad idea to make a diagram.
- When making a diagram, liberally include entities. Even ones tangentially related (within reason).
- Say good stuff before bad stuff, and don’t say “but”.
- e.g. “This is really useful information. When you said XYZ, should this be ABC instead?” NOT “This is really useful but when you said XYZ, should this be ABC instead?” AND NOT “When you said XYZ, should this be ABC instead? This is really useful information by the way.”
- Clarify everything explicitly.
- Don’t settle for unclear expectations.
- Try to make yourself have to do less work.
- while not sacrificing the quality of deliverables.
- Always look for easier ways to do something.
- while not sacrificing the quality of deliverables.
- Getting feedback early is probably the single most useful habit you can form.
- Complicated tests will never be fun.
- Verbally summarise meetings at the end to gain clarity.
- When something new is introduced, or something changes, ask “who else should know about this?”