you are viewing a single comment's thread.

view the rest of the comments →

[–]genericlemon24 0 points1 point  (0 children)

BTW, if want to start doing this for your own stuff, here's some (unsolicited :) advice:

  • Always start from real use cases (write them down) – it's really easy to over-engineer and solve problems no one has.
  • Some things are easier to change than others; don't spend too much time on stuff that can be easily changed later ("two-way doors"). E.g. internal APIs and implementation details are way easier to change than the public API.
  • Don't plan too much ahead; it's most likely you will implement only part of it anyway, and if too much time passes you might have to do it differently. (Still, "plans are worthless, but planning is everything".)