Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I make web applications, mostly MVC, object oriented and database enabled. I always have trouble going back to project after a few months of release and work again. I don't even remember what I made on that project. How should I overcome this problem? I can't afford too much time consuming documentations and so many diagrams. Any quick way you guys practice to avoid this?

share|improve this question

closed as primarily opinion-based by gnat, Martijn Pieters, Kilian Foth, GlenH7, World Engineer Mar 6 '14 at 13:13

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

recommended reading: Why is asking a question on “best practice” a bad thing? – gnat Feb 21 '14 at 7:54
up vote 1 down vote accepted

lol I'm repeating myself, but simple sequence diagrams ( not only define the API methods from the service interactions, but is also a great way to get my head back into it coming back to it later.

Really simple, though. Just enough to understand the high points of client-server interaction.

Also, just a simple bullet point list, even in initial comments of:

  • client sends this
  • server sends that

is a simple way of capturing that. IMHO

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.