I was working on my website and saw the following quote come up in my quote list. I didn't know what waterfall programming meant, so I did a search for the quote. I find it interesting that my site (when it was still using Postnuke) came up in the Google results. Made me happy. But the article I found is an interesting read. The quote was actually part of a reader response to the article.
Part of the reason so many companies continue to develop software using variations of waterfall is the misconception that the analysis phase of waterfall completes the design and the rest of the process is just non-creative execution of programming skills.
The article is "Iterative vs. waterfall software development: Why don't companies get it?" by Bill Walton.
It discusses four methodologies for programming. I think I use the third one most often in my work, except that I rarely have a partner to work with.
- The iterative and incremental approaches involve a number of short cycles in which steps such as requirements gathering, coding, testing and deployment, are conducted to produce small parts of the final project. The software system grows incrementally, and user feedback can be used throughout the process.
- The waterfall philosophy is a strictly sequential approach in which a project is completed in a series of steps, such as analysis, design, coding, testing and deployment. Each step, such as requirements gathering, is undertaken only once and must be completed and verified before the next phase.
- Extreme programming is a software development approach built around rapid iterations, an emphasis on code writing and working closely with end users to achieve business results. The 12 basic practices of XP include continual testing and the idea that programmers should work in pairs. (See Computerworld QuickStudy.)
- Project Management Institute methodology involves recommended best practices that use a cycle of processes -- initiating, planning, executing, controlling and closing -- to manage a project's scope, time, costs, risks and so on.
"The Last Few Inches" by Chad Dickerson
I'm trying to track down the source of the problem. According to the documentation I have, they are logon type 7, which is an "Unlock" attempt, like from the console. I don't think that's entirely accurate though because the server is behind me. I think perhaps it might be from terminal services. I'd like to disable that, but I currently don't have a monitor on that system. We'll see what happens.
When I tried before from the work directory of the port, it kept failing at one spot that didn't seem to have anything to do directly with the ISAM option. Something about gen_lex_hash not being found, even though it was there, ready to be compiled. I just don't feel like doing that kind of troubleshooting right now.
It looks like it may be working, but it's still compiling at this point.
Update: Half an hour later, we have a working MySQL.
But I finally put my contacts back in this morning and my eyes don't like me. They finally adjusted to the glasses and I've gone and switched on them again.
It's going to be a long day.
It was a pain to install because it required modifying a lot of core code (not huge modifications, just on several files). The biggest problem I have with those types of modifications is that when I update versions, I have to redo it all. This is the reason I'm trying to make the fn-comments modification I'm doing hold most of it's code in a seperate file.
My next goal is to find where to modify the Meta keywords in PHP-Nuke. It's not that it's going to be hard. I just haven't done it yet.
The whole episode seems like it's a message of Technology vs. Divinity. I may have to watch it again in a day or so to decide if I liked it or not.
On the bright side of everything, it looks like Sam is rejoining the team next episode (according to the preview).



