Documentation on Miro's World

Recreate txt base graph generator

Tue, 09 Sep 2014 11:22:48 +0800

Graphviz
#

This time using brew

➜  DPS  brew install graphviz
==> Downloading https://downloads.sf.net/project/machomebrew/Bottles/graphviz-2.38.0.mavericks.bottle.tar.gz
######################################################################## 100.0%
==> Pouring graphviz-2.38.0.mavericks.bottle.tar.gz
🍺  /usr/local/Cellar/graphviz/2.38.0: 469 files, 68M
➜  DPS  dot -V
dot - graphviz version 2.38.0 (20140413.2041)
➜  DPS

Schema Spy
#

From http://sourceforge.net/projects/schemaspy/files/schemaspy/SchemaSpy%205.0.0/

To /opt/diagram

Run:

diagram java -jar ./schemaSpy_5.0.0.jar -cp .:/Users/miro/lib/jdbc/mysql-connector-java-5.1.26-bin.jar -t mysql -o library -host localhost -u training -db training_dev01 -p training

MSDN Documentation - the follow up

Fri, 15 Jun 2007 20:01:02 -0400

Judging by the number of hits, Joel (and myself) are not the only people who would like to see nicer, better and faster MSDN documentation. As a very nice surprise, some of the feedback came directly from the people than actually can do something about it - like Darren Parker from Microsoft and Anand Raman from the Sandcastle project. Rob Relyea suggested and interesting looking tool based on XAML.

Thanks everybody - it is always nice to find out that even really big companies listen to the developers and want to address the problems. It almost feels like OpenSource experience where (it was few years back) we have encountered an issue in one of many Java templating libraries, posted to discussion group a question and few hours + several emails later had patch for the bug from the library creator :-). But back to the topic.

MSDN Documentation - the worst in class ?

Thu, 14 Jun 2007 22:41:36 -0400

Did it ever happened to you that you were using some tool day after day - and never realized it's pretty big deficiencies ? Until somebody, coming from different background pointed out what everything is wrong with the tool ? Before that moment of revelation, the issues were just inconvenience, but right after that they became real annoyance ?

Exactly this happened to me last week and the credit for pointing out what is wrong with MSDN documentation (and the "standard" .NET documentation format in general) goes to Joel :-)