From 31b9e516b07bc2377367bfc06de91d0a5c336d5b Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Thu, 22 Aug 2013 22:48:52 +0200 Subject: add readme MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- README | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 README (limited to 'README') diff --git a/README b/README new file mode 100644 index 0000000..5855491 --- /dev/null +++ b/README @@ -0,0 +1,25 @@ +In lack of good git documentation and manuals, I started by own. + +It seems to be lack of well written manuals, and Git's online +documention itself is atrocious. Will I do not except the writers +to have taking any course in pedagogy or didactics, or even any +practical experience, I at least exept the writters to try to +keep those aspects in mind, but that does not seem to be the case. + +Documentation should first introduct the concept, then the +implementation; that is, first how to get started, than what +they are doing. In other words, first how to create a Git +repository and the absolute essantials, than introduce Git +itself. Not first taking about what Git is, readers want to +read the chapters in their order, if they do not have anything +specific in mind. + +Documentation should then give you breif documentation of everthing +you need to know in the order of imporantance, then, iterator be +more advanced. + +But one of the most important part is not to start with dangerous +commands just because it is easier to be lazy them. Try to do it +right from the beginning, otherwise the wrong way will stick in +the reader's memory. + -- cgit v1.2.3-70-g09d2