posted 21 years ago
Don't worry about the review. I played the numbers game, and got about 5 reviews out of 30 people.
I then got sidelined by personal issues: my new job, loss of my computer, other responsibilities, and the weight of the world. The reviews were supposed to go from Sept to Oct. No one did it by the deadline, so I pusshed it back to Nov. The day I was supposed to incorporate the feedback was the day I destroyed my laptop, and it took until the end of the year to get a new one. I kinda lost momemtum and haven't touched it in the last few weeks.
So tonight, since the dance club I go to was dead, I decided to come home early, and try to make the most of a lost night by being productive. Sadly, I've found my most productive hours (for school, work, book, whatever) are from about 10pm-2am Fri and Sat night.
As for where I'm going with this? We'll, I want to point out why all other methodologies suck, but that if people do exacvtly what I say, and buy my books, software, training, plush toys, anti-rust coating, etc, they can produce good software. :-)
Seriously, as you may know, my book is about what developing software is really entails. In some sense, the book is about software methodology. However, I stay methodology agnostic, instead describing the fact that they all do the same thing, just different ways. The point of the book is to illuminate what the steps are, not how to do them. Chapter 2 gives an overview of methodologies and lifecycles, because if you were punting class the day they covered it in college you're going to walk into a job and be lost. ("Don't we just write code until one day we're done writing code?"*)
Invest 5 minutes and look at the outline.
--Mark
*I've got a great sotyr about this in chapter 1. :-)
I'm getting old so I only need a few hours of sleep. What's your excuse?
