Are you still accepting suggestions?
15 views
Skip to first unread message
David
Jun 30, 2011, 8:56:25 AM6/30/11
to Mikado Method
Sorry, I have only now started learning about the Mikado Method, which
I hope to be very useful to me. I see that a few of the immediate
comments I had have already been dealt with here, so will skip them,
but one bigger point:
A good deal of the content of the Preface is really a first chapter.
The Preface should be skippable and still one will understand what the
point of the book is by reading the first chapter. If you don't read
the current Preface, your experience of the first chapter will be
confusing, to say the least. I'd reorganize so that the Preface is
really a Preface - it won't explain the book in more than the most
general terms, but will guide the reader (as it does now) as to what
to read and how to read it. The first chapter will contain much of the
current explanation of what the book is about found in the Preface.
Think of it as literary refactoring!
A more minor point: page iii, para 1: (consider the use of the serial
comma throughout the book; this frequently makes series much clearer
and more understandable - its avoidance is an old-style hangover of
the days of newspaper journalism, where space was at a premium) ...
future problems are encountered, solved<added>,</added> and sometimes
avoided entirely.
I'm reading changeset: 893:d6ebe0752d43.
As for my background, I am an 11-year Java developer with a lot of
agile, refactoring, and design pattern experience, and have served in
the past for about 5 years as an editor in a publishing house in the
US. (So I might know a thing or two about writing....)
I will continue reading and comment as I see points to be made if you
are still accepting comments.
Warmly,
David Sills
I hope to be very useful to me. I see that a few of the immediate
comments I had have already been dealt with here, so will skip them,
but one bigger point:
A good deal of the content of the Preface is really a first chapter.
The Preface should be skippable and still one will understand what the
point of the book is by reading the first chapter. If you don't read
the current Preface, your experience of the first chapter will be
confusing, to say the least. I'd reorganize so that the Preface is
really a Preface - it won't explain the book in more than the most
general terms, but will guide the reader (as it does now) as to what
to read and how to read it. The first chapter will contain much of the
current explanation of what the book is about found in the Preface.
Think of it as literary refactoring!
A more minor point: page iii, para 1: (consider the use of the serial
comma throughout the book; this frequently makes series much clearer
and more understandable - its avoidance is an old-style hangover of
the days of newspaper journalism, where space was at a premium) ...
future problems are encountered, solved<added>,</added> and sometimes
avoided entirely.
I'm reading changeset: 893:d6ebe0752d43.
As for my background, I am an 11-year Java developer with a lot of
agile, refactoring, and design pattern experience, and have served in
the past for about 5 years as an editor in a publishing house in the
US. (So I might know a thing or two about writing....)
I will continue reading and comment as I see points to be made if you
are still accepting comments.
Warmly,
David Sills
Ola Ellnestam
Jun 30, 2011, 9:15:32 AM6/30/11
to mikado...@googlegroups.com
Hi David,
Thanks a lot for your input, we really appreciate it and we still want it.
We will start looking at the preface/first chapter immediately and see
how we can improve the reading experience.
Keep posting your findings and we will try to keep up ;-)
Cheers,
Ola
--
---------------------------------------------------------
Ola Ellnestam
Agical AB
V�sterl�nggatan 79, 2 tr
111 29 Stockholm, SWEDEN
Mobile: +46-708-754000
E-mail: ola.el...@agical.se
Blog: http://ellnestam.wordpress.com
Twitter: ellnestam
Reply all
Reply to author
Forward
0 new messages