The Mikado Method book
Daniel Brolund
At:
http://www.agical.com/mikmeth/mikadomethod.pdf
our draft book about the Mikado Method is available for public review.
The book has gone through some rounds of feedback, and now we hope to
get even more!
The goal of the book is to quickly provide an understanding of the
Mikado Method, and then build on that as the book progresses. While
doing so we touch on other topics that are related to refactoring.
As is stated on the very first "draft page" of the book, we would
especially like feedback on:
* Overall chapter and section structure
* Pedagogic ordering
* Things you don’t understand or that are insufficiently explained
* Things that are missing
* Things that shouldn’t be in there for one or another reason
We hope that you will find the book useful and we look forward to any
questions or opinions you might have!
Thanks!
Daniel & Ola
--
---------------------------------------------------------
Daniel Brolund
Agical AB - www.agical.com
work: daniel....@agical.com
phone: +46708754002
blog:http://danielbrolund.wordpress.com
twitter: @danielbrolund
private: daniel....@gmail.com
Joakim Ohlrogge
that the new algorithm is actually a different one. It makes more
sense that way to make two different projects. For instance the new
algorithm could be the HAL-algorithm that just shifts all character
values one step to the left so that IBM becomes HAL. As it is now the
algorithm is not different, it just has different parameters.
/J
> private: daniel.brol...@gmail.com
Joakim Ohlrogge
that the new algorithm is actually a different one. It makes more
sense that way to make two different projects. For instance the new
algorithm could be the HAL-algorithm that just shifts all character
values one step to the left so that IBM becomes HAL. As it is now the
algorithm is not different, it just has different parameters.
/J
On Aug 4, 2:22 pm, Daniel Brolund <daniel.brol...@agical.com> wrote:
> private: daniel.brol...@gmail.com
Daniel Brolund
Cheers
Daniel
Joakim Ohlrogge
section in chapter one assumes no prior knowledge of the mikado method
(start explaining it pretty much from scratch) where each section
should assume knowledge in gained in previous sections. The preface
felt long and repetitive to me. I think the preface is the kind of
section that needs to be snappy and get you from 0 to chapter one with
as little detour as possible. Perhaps it should just set the stage for
section 1 in chapter one? It feels a bit now like the different
sections in the preface were written individually at different times
and then put together to a preface in a later "integration-phase" so
to speak...
I like the chapter explanations for different types of readers though
I'm not exactly sure what the developer in an emergency situation and
a developer in trouble. Perhaps a developer in an emergency situation
is a becoming developer in trouble? I think I lack the next step
there: A developer trying to stay out of trouble. But I think those
are pretty much the same person at different times... perhaps just add
subsections:
Developers
If you're in an emergency...
If you're in trouble and want to get out of it...
When you're out of troubles way and want to stay out of trouble...
Jocke NittyPicky Ohlrogge
> private: daniel.brol...@gmail.com
Daniel Brolund
be reduced a bit.
The "developer in an emergency" is one that only wants a minimum
amount of information to get started, perhaps to make a refactoring
before a looming deadline.
As you say, he is likely to become a "developer in trouble". Good idea
to add "developer staying out of trouble".
Cheers
Daniel
> --
> You received this message because you are subscribed to the Google Groups "Mikado Method" group.
> To post to this group, send email to mikado...@googlegroups.com.
> To unsubscribe from this group, send email to mikado-metho...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mikado-method?hl=en.
>
>
--
---------------------------------------------------------
Daniel Brolund
Agical AB - www.agical.com
work: daniel....@agical.com
phone: +46708754002
blog:http://danielbrolund.wordpress.com
twitter: @danielbrolund
private: daniel....@gmail.com
Alan Baljeu
Chapter 1. If you made it the first chapter you'd have to change it
slightly to get a little more specific on how it works in coding, but
I find the Pick-Up Sticks metaphor really helps to get the mind
engaged.
Daniel Brolund
We had it as the first chapter before, but wanted to get to the core
rules of Mikado first, sort of to align with the Dreyfus Novice level.
http://en.wikipedia.org/wiki/Dreyfus_model_of_skill_acquisition
The thing might be that you're not exactly a novice... ;-)
The second chapter would the be an example, and then we build with
more history, background, stories and metaphors as you go along.
Maybe we would get brains going if we explained the pick-up sticks
metaphor in the beginning of the first chapter where we talk about
dependencies?
Any other takers on this?
Cheers
Daniel
Joakim Ohlrogge
now. However, I'm rereading it now and in some ways the way the
chapter is written it feels like it was intended to come before the
first two chapters, if chapter 3 should remain chapter 3 it should be
looked at to understand why it feels like that. I guess because it was
originally meant to build anticipation for what to learn but a quick
run through of the essentials have already been made. I still prefer
it this way but since others have indicated otherwise maybe it should
be reconsidered. I can think of some options:
* Leave it as it is. I Like it, Possibly after some sort of poll
* Break chapter 3 into two parts and present part 1 as the beginning
of chapter one.
* Add a reading instruction at the beginning of chapter 1:
"We wanted to get down and dirty as soon as possible by showing you
what the mikado-method is all about and how it works. That is what
this and the next chapter is all about. If you prefer to get some more
background and information about the origins of the Mikado Method
before you get your hands dirty; feel free to skip to chapter 3 and
come back here when you've read it"
* Move chapter 3 before chapter 1, Possibly after some sort of poll
There are probably other ways to deal with it too.
/J
On Sep 8, 4:31 pm, Daniel Brolund <daniel.brol...@agical.com> wrote:
> Interesting.
>
> We had it as the first chapter before, but wanted to get to the core
>
> The second chapter would the be an example, and then we build with
> more history, background, stories and metaphors as you go along.
>
> Maybe we would get brains going if we explained the pick-up sticks
> metaphor in the beginning of the first chapter where we talk about
> dependencies?
>
> Any other takers on this?
>
> Cheers
> Daniel
>
> > It seems to me that Chapter 3 is a better introduction to Mikado than
> > Chapter 1. If you made it the first chapter you'd have to change it
> > slightly to get a little more specific on how it works in coding, but
> > I find the Pick-Up Sticks metaphor really helps to get the mind
> > engaged.
>
> > --
> > You received this message because you are subscribed to the Google Groups "Mikado Method" group.
> > To post to this group, send email to mikado...@googlegroups.com.
> > To unsubscribe from this group, send email to mikado-metho...@googlegroups.com.
> --
> ---------------------------------------------------------
> Daniel Brolund
> Agical AB -www.agical.com
>
> private: daniel.brol...@gmail.com
Daniel Brolund
those are good suggestions. We'll have to think a bit about it.
Cheers
Daniel
> For more options, visit this group at http://groups.google.com/group/mikado-method?hl=en.
>
>
--
---------------------------------------------------------
Daniel Brolund
Agical AB - www.agical.com
work: daniel....@agical.com
phone: +46708754002
blog:http://danielbrolund.wordpress.com
twitter: @danielbrolund
private: daniel....@gmail.com