Comments on: Eric Shepherd’s field promotion http://www.dria.org/wordpress/archives/2006/10/06/441/ intrepid girl reporter Tue, 29 Nov 2011 14:54:22 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: funTomas http://www.dria.org/wordpress/archives/2006/10/06/441/comment-page-1/#comment-60058 funTomas Sat, 07 Oct 2006 11:44:42 +0000 http://www.dria.org/wordpress/archives/2006/10/06/441/#comment-60058 Well, documenting of any project is a MUST if the project is to be used by humans. Anyway, I completely agree with bodensatz. Sun had IMO quite on time realized this issue and created doc comments in Java. I just wonder what processes, technologies and paterns are in use by Mozilla Doc team.<br>Congrats Eric. Well, documenting of any project is a MUST if the project is to be used by humans. Anyway, I completely agree with bodensatz. Sun had IMO quite on time realized this issue and created doc comments in Java. I just wonder what processes, technologies and paterns are in use by Mozilla Doc team.
Congrats Eric.

]]> By: funTomas http://www.dria.org/wordpress/archives/2006/10/06/441/comment-page-1/#comment-14607 funTomas Sat, 07 Oct 2006 10:44:42 +0000 http://www.dria.org/wordpress/archives/2006/10/06/441/#comment-14607 Well, documenting of any project is a MUST if the project is to be used by humans. Anyway, I completely agree with bodensatz. Sun had IMO quite on time realized this issue and created doc comments in Java. I just wonder what processes, technologies and paterns are in use by Mozilla Doc team. Congrats Eric. Well, documenting of any project is a MUST if the project is to be used by humans. Anyway, I completely agree with bodensatz. Sun had IMO quite on time realized this issue and created doc comments in Java. I just wonder what processes, technologies and paterns are in use by Mozilla Doc team.
Congrats Eric.

]]> By: bodensatz http://www.dria.org/wordpress/archives/2006/10/06/441/comment-page-1/#comment-14604 bodensatz Fri, 06 Oct 2006 22:49:32 +0000 http://www.dria.org/wordpress/archives/2006/10/06/441/#comment-14604 I've got a lot of respect for someone who does documentation, especially "vital and high-quality" stuff. By far the hugest problem with FOSS these days is the lack of good documentation, especially for non-techies. I recall way back during my first stint as a UNIX Sys-Admin in 1991 at the university, when I was asked by someone in the Math Dept to install LaTex onto the server. I struggled with that sucker for a couple of months before I finally gave up. Problem was that the installation docs - what litter there were - assumed you were a hard-core LaTex user, and I didn't know a damned thing about it. Fortunately we have come a long way since then, and there are lots of great FOSS projects these days that do have good docs. Unfortunately there are still a lot which do not. I've always said at work that if you aren't spending at least 5% of your time documenting in detail what you do, then neither you nor your manager are doing your jobs. I document everything I do in a wiki as well. Congrats Eric! I’ve got a lot of respect for someone who does documentation, especially “vital and high-quality” stuff. By far the hugest problem with FOSS these days is the lack of good documentation, especially for non-techies. I recall way back during my first stint as a UNIX Sys-Admin in 1991 at the university, when I was asked by someone in the Math Dept to install LaTex onto the server. I struggled with that sucker for a couple of months before I finally gave up. Problem was that the installation docs – what litter there were – assumed you were a hard-core LaTex user, and I didn’t know a damned thing about it.

Fortunately we have come a long way since then, and there are lots of great FOSS projects these days that do have good docs. Unfortunately there are still a lot which do not.

I’ve always said at work that if you aren’t spending at least 5% of your time documenting in detail what you do, then neither you nor your manager are doing your jobs. I document everything I do in a wiki as well.

Congrats Eric!

]]>