the wiki approach can solve many problems, with suitable extensions

• I've been a wiki user and evangelist since 1996
  • the first public wiki was March 1995 https://en.wikipedia.org/wiki/Ward_Cunningham
• I think that the wiki approach can solve many problems, with suitable extensions
• I have evangelized wikis at every company I've ever worked for, inside every project. I have used far too many different wiki engines.
• I have written quite a bit of useful code in and for wikis
  • e.g. architecture specs
    • self organizing better than the random collection of pages that so many wiki turn onto
      • infers a tree structure from links, but allows user to override
    • with a built in spreadsheet++ to collect area and power and performance estimates from the wiki
      • not really a spreadsheet, but a wiki that contains formulated that auto updates like it spreadsheet
      • without being shackled to the rows and columns mentality of standard spreadsheets
    • automatically creating printable manuals, of course, from the wiki pages
    • automatically creating performance and benchmark studies, linking to descriptions of the microarchitecture features