>Rhythm. Waiting until the right moment preserves energy and avoids clutter. Act with intensity when the time comes to act. What does this mean ?
Don't swing 'til the ball gets there. If it can wait, it probably should wait.
Mastering Programming: An Outline
131–136 of 136 posts
Re: Mastering Programming: An Outline
#132Earlier quoted context omitted.
> If not why does Kent Beck? "Mastering" Programming, heh. He is also the person who (re-)originated test-driven development. And his day job for the last few years has been mentoring Facebook's new engineers. And you ignore that he answered your question in the first paragraph of the piece. You might agree or disagree with his explanation, but ignoring it just looks sloppy.
"From years of watching master programmers, I have observed certain common patterns in their workflows. From years of coaching skilled journeyman programmers, I have observed the absence of those patterns. I have seen what a difference introducing the patterns can make." Is this the paragraph? I fail to see how such self declarations of uber competence and self labeling as "master programmer" should be accepted by ot…
You are not so good with the reading. In that paragraph, he does not claim that he is a master. He claims that he has watched master programmers.
Re: Mastering Programming: An Outline
#133Earlier quoted context omitted.
"From years of watching master programmers, I have observed certain common patterns in their workflows. From years of coaching skilled journeyman programmers, I have observed the absence of those patterns. I have seen what a difference introducing the patterns can make." Is this the paragraph? I fail to see how such self declarations of uber competence and self labeling as "master programmer" should be accepted by ot…
You are not so good with the reading. In that paragraph, he does not claim that he is a master. He claims that he has watched master programmers.
He claims he coached 'skilled journeymen' programmers.
The 'master - journeyman-apprentice' pyramid jargon is part of the 'software craftsman' movement. In this structure, 'masters' train 'journeymen' who serve an 'appreniceship' and help them breakthrough into 'mastery. Lots of jargon from the old guild structures.
So Kent is implicitly (imo) claiming to be a 'master'. At the least he is claiming to better than "talented journeymen" engineers at FaceBook.
That said, I grant you he may be using the words without that implication. Not likely, but possible.
Whatever. All these agile/methodology guru types like to pass themselves off as skilled programmers without any supporting evidence and should be (imo) ignored totally when they pontificate about how others should program etc
YMMV. That's fine. Peace. Out.
Re: Mastering Programming: An Outline
#134Earlier quoted context omitted.
You are not so good with the reading. In that paragraph, he does not claim that he is a master. He claims that he has watched master programmers.
He claims he coached 'skilled journeymen' programmers. The 'master - journeyman-apprentice' pyramid jargon is part of the 'software craftsman' movement. In this structure, 'masters' train 'journeymen' who serve an 'appreniceship' and help them breakthrough into 'mastery. Lots of jargon from the old guild structures. So Kent is implicitly (imo) claiming to be a 'master'. At the least he is claiming to better than "tal…
He is claiming to be a coach. Coaches don't have to be master players to be good coaches. The rest is stuff you are making up because you have an axe to grind.
Which, fine, grind your axes. But maybe you could stick to ranting about what people have actually done and written rather than just barking about things you imagine. For somebody very concerned about the credibility of others, you aren't working very hard on your own.
Re: Mastering Programming: An Outline
#135Something that is helping me a lot recently is trying to know all there is to be known about the tools/concept that I am using and the problem that I am solving. Too often have I used tools I half understood to solve problem that I didn't define clearly enough.
There's a balance though because I learn a lot by DOING, I can only read/learn/think about something so much before it just gets fuzzy and I can't keep anymore in my head.
Re: Mastering Programming: An Outline
#136Something that is helping me a lot recently is trying to know all there is to be known about the tools/concept that I am using and the problem that I am solving. Too often have I used tools I half understood to solve problem that I didn't define clearly enough.
There's a balance though because I learn a lot by DOING, I can only read/learn/think about something so much before it just gets fuzzy and I can't keep anymore in my head.