I'm actually writing Fusedocs as we speak, at the same time I'm teaching a guy I'm working with about Fusedocs. He's in return teaching another guy at his office about fusedocs. My guess is that it'll take 2 years before the world realizes how utterly powerful Fusedocs are. At some point NO one will code without them, or some type of variation on the concept.
Fusedocs are difficult to jump into because they are backwards from how the professors teach you to document code in college. Let me tell you a little college story. When I taking the lab section of CS205 or 208 or 309 I forget, I would constantly get reamed by my professors for not fully documenting my code. I got into yelling matches with them about how documenting my code was totally useless. They would say "You'll thank me when you have to make changes to this code in a year and you have documentation to read" So just to get back at them I put stupid comments in there, because I thought I was being funny. They didn't get my joke but I suddenly got better grades, imagine that! Here's an example of a stupid comment in CF: <!--- loop over query ---> <cfloop query="somequery"> That comment will do nothing for you in a year. That was years ago and I have yet to thank that professor. It took a long time until I understood the *real* problem with how they teach software documentation in college. Hal opened my eyes with his concept of fusedocs. They're teaching it backwards in school, for that matter, the software industry has been doing it backwards for 50 years. In college they teach "code the software THEN write the documentation". Fusedocs say "Write the documentation THEN Code the documentation". The reason this is SO SO SO SO SO powerful is that you figure out what the application should do before you spend time coding it. When building a house, a builder doesn't say "hmmm i wonder if we should use a 2X4 or a 2X10, oh well I'll just guess and hope it holds". NO WAY! The architect designs the house and it gets approved by a structural engineer to decide if the materials will hold. In this day and age houses rarely fall over by accident. So, are people using fusedocs? Yes. Are enough people using them? No. I'm going to try and hold a hands on session at this year's conference about Fusedocs. I think they are far too important for people to ignore. Steve Nelson > Wally Randall wrote: > > I would like to raise an heretical issue. WHO USES FUSEDOCS? At various > user group meetings I have discussed the use of Fusebox. Everyone seems to be > using the coding methodology by NO ONE is using FUSEDOCS! The coders are > structuring their code with Fusebox but not taking the time to use the design > methods inherent in the development of FUSEDOCS. > > This has certainly been true in the last two large Fusebox projects I have > been involved in. The developers do not want to spend 'coding time' > developing Fusedocs and the managers have no interest in spending development > time engaged in that level of planning detail. > > How are various developers planning their sites if they are not using > FUSEDOCS? > > > __________________________________________________________________ > Wallace Randall > ICQ#: 157983785 > Current ICQ status: [Image] > > + More ways to contact me > __________________________________________________________________ > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
