re: What are the unwritten rules of development? VIEW POST


I use the following system to triage work: I have a mental coordinate system, where the X axis goes from low impact to high impact and the Y axis goes from low complexity to high complexity. This gives us four quadrants:

  1. High complexity, high impact: this is generally why you're writing a piece of code in the first place, i.e. what makes your application worth writing. Deserving of the highest attention, comprehensive tests etc.
  2. Low complexity, hight impact: the low hanging fruit. Do as much of that as you can, whenever you can.
  3. Low complexity, low impact: You barely should find yourself doing work in this quadrant. It gives a false sense of productivity (due to the low complexity you can get a lot of stuff done), but doesn't really push the project forward.
  4. High complexity, low impact: I've you find yourself here, find something else to do.
code of conduct - report abuse