I can't help but be amused that a week ago I posted a rant about wikis (see http://codersbuffet.blogspot.com/2012/01/wikis-suck.html ), and then this topic comes up.
My views? Use the git docs. They work. They got hampered by my real life requirements over the past 6 months. I'm finally settling back into working again, and am focusing more on Hiring Pond (the main application to be developed throughout the book), and then the book itself. Having the code done/tested will help me produce a higher quality end result on the book. Don't use wiki. I know they're popular. I know people like them. I just don't agree with them, and wish I could figure out the solution. If i ever *do* figure out a documentation tool that addresses my issues, I'll work on it. Still trying, though. -- Michael J. Pedersen My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen Google Talk: [email protected] -- Twitter: pedersentg -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
