Difference: ProgrammingBookmarks (1 vs. 54)

Revision 5403 Apr 2017 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 43 to 43
 RFC's - are the documents that describe internet protocols. There are many ways to get them; among them are raw and cooked.

Binary Arithmetic Considered Harmful - It's not commonly understood that binary numbers are imprecise to the right of the decimal point. http://www-106.ibm.com/developerworks/java/library/j-jtp0114/ is a good intro to floating point and its problems. Although Java-centric, it has a good introduction to the topic and good references.

Changed:
<
<
Also: http://blog.reverberate.org/2014/09/what-every-computer-programmer-should.html
>
>
Also: http://blog.reverberate.org/2014/09/what-every-computer-programmer-should.html
Also: http://0.30000000000000004.com/
  Financial Calculations - http://quantlib.org/ is an open-source C++ library for sophisticated financial calculations.

Revision 5317 Sep 2014 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 42 to 42
  RFC's - are the documents that describe internet protocols. There are many ways to get them; among them are raw and cooked.
Changed:
<
<
Binary Arithmetic Considered Harmful - It's not commonly understood that binary numbers are imprecise to the right of the decimal point. http://www-106.ibm.com/developerworks/java/library/j-jtp0114/ is a good intro to floating point and its problems. Although Java-centric, it has a good introduction to the topic and good references.
>
>
Binary Arithmetic Considered Harmful - It's not commonly understood that binary numbers are imprecise to the right of the decimal point. http://www-106.ibm.com/developerworks/java/library/j-jtp0114/ is a good intro to floating point and its problems. Although Java-centric, it has a good introduction to the topic and good references.
Also: http://blog.reverberate.org/2014/09/what-every-computer-programmer-should.html
  Financial Calculations - http://quantlib.org/ is an open-source C++ library for sophisticated financial calculations.

Revision 5202 Jun 2014 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 70 to 70
 Somewhat related is the question of what really motivates creative people. Turns out it's not money: http://www.youtube.com/watch?v=rrkrvAUbU9Y
Well-researched presentation about software management (team size, hours, etc): http://www.lostgarden.com/2008/09/rules-of-productivity-presentation.html
Even very short interruptions have a surprisingly large impact on error rates: http://www.futurity.org/top-stories/3-second-distraction-doubles-work-errors/
Added:
>
>
http://www.newyorker.com/online/blogs/currency/2014/01/the-open-office-trap.html - open plan offices are less productive than offices with doors
  Developer Support Handbook - http://www.developer-support-handbook.org/intro.html
In this handbook, I mostly cover the first aspect of providing an API: support. It is probably the least glamorous aspect, but on the other hand, it is vital. You can have the best API in the world, but if people post in your forums and the response is just crickets chirping, then the developers will not stick around for very long. On the other hand, if you treat your developers well, then they will (for free) provide you with valuable insights about ways to improve your API, and they will evangelize your API for you.

Revision 5114 Jan 2013 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 69 to 69
 This is related to Demarco and Lister's discussion of "flow" in Peopleware. Here's Joel Spolsky's review of Peopleware: http://www.amazon.com/review/RYVTUPDAUANZW
Somewhat related is the question of what really motivates creative people. Turns out it's not money: http://www.youtube.com/watch?v=rrkrvAUbU9Y
Well-researched presentation about software management (team size, hours, etc): http://www.lostgarden.com/2008/09/rules-of-productivity-presentation.html
Added:
>
>
Even very short interruptions have a surprisingly large impact on error rates: http://www.futurity.org/top-stories/3-second-distraction-doubles-work-errors/
  Developer Support Handbook - http://www.developer-support-handbook.org/intro.html
In this handbook, I mostly cover the first aspect of providing an API: support. It is probably the least glamorous aspect, but on the other hand, it is vital. You can have the best API in the world, but if people post in your forums and the response is just crickets chirping, then the developers will not stick around for very long. On the other hand, if you treat your developers well, then they will (for free) provide you with valuable insights about ways to improve your API, and they will evangelize your API for you.

Revision 5021 Nov 2012 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 22 to 22
  mercurial is changeset-oriented system. It's supposedly the leading candidate to become the next-gen Linux SCM if Linus decides to switch away from git. http://www.selenic.com/mercurial/
Added:
>
>
Writing good commit messages - http://news.ycombinator.com/item?id=4270890
 

Misc

Revision 4926 Jul 2012 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 77 to 77
  Design Principles - from the UK Government design group: https://www.gov.uk/designprinciples
from Dieter Rams, a famous industrial designer: http://www.vitsoe.com/en/gb/about/dieterrams/gooddesign/ \ No newline at end of file
Added:
>
>
Guess Gender by First Name - code (and database) to guess a person's gender from their first name: http://www.autohotkey.com/community/viewtopic.php?t=22000
 \ No newline at end of file

Revision 4805 Jul 2012 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 74 to 74
 How to Design a Good API and Why it Matters - Uses Java examples but it's generally good advice for any language: http://lcsd05.cs.tamu.edu/slides/keynote.pdf

Hashing - http://programmers.stackexchange.com/questions/49550/which-hashing-algorithm-is-best-for-uniqueness-and-speed \ No newline at end of file

Added:
>
>
Design Principles - from the UK Government design group: https://www.gov.uk/designprinciples
from Dieter Rams, a famous industrial designer: http://www.vitsoe.com/en/gb/about/dieterrams/gooddesign/
 \ No newline at end of file

Revision 4730 May 2012 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 72 to 72
 Developer Support Handbook - http://www.developer-support-handbook.org/intro.html
In this handbook, I mostly cover the first aspect of providing an API: support. It is probably the least glamorous aspect, but on the other hand, it is vital. You can have the best API in the world, but if people post in your forums and the response is just crickets chirping, then the developers will not stick around for very long. On the other hand, if you treat your developers well, then they will (for free) provide you with valuable insights about ways to improve your API, and they will evangelize your API for you.

How to Design a Good API and Why it Matters - Uses Java examples but it's generally good advice for any language: http://lcsd05.cs.tamu.edu/slides/keynote.pdf \ No newline at end of file

Added:
>
>
Hashing - http://programmers.stackexchange.com/questions/49550/which-hashing-algorithm-is-best-for-uniqueness-and-speed
 \ No newline at end of file

Revision 4623 Apr 2012 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 70 to 70
 Well-researched presentation about software management (team size, hours, etc): http://www.lostgarden.com/2008/09/rules-of-productivity-presentation.html

Developer Support Handbook - http://www.developer-support-handbook.org/intro.html

In this handbook, I mostly cover the first aspect of providing an API: support. It is probably the least glamorous aspect, but on the other hand, it is vital. You can have the best API in the world, but if people post in your forums and the response is just crickets chirping, then the developers will not stick around for very long. On the other hand, if you treat your developers well, then they will (for free) provide you with valuable insights about ways to improve your API, and they will evangelize your API for you.
\ No newline at end of file
Added:
>
>
How to Design a Good API and Why it Matters - Uses Java examples but it's generally good advice for any language: http://lcsd05.cs.tamu.edu/slides/keynote.pdf
 \ No newline at end of file

Revision 4518 Jul 2011 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 31 to 31
  Software Architecture - is an extremely nebulous term in the context of software. Everyone agrees that it's important, but nobody really agrees on what it is. This site is a useful resource, though. http://www.bredemeyer.com/
Added:
>
>
The Architecture of Open Source Applications - http://www.aosabook.org/en/index.html
 Extreme Programming - is a recent fad methodology, and I've pretty much hated the various programming fads that preceded it (TQM, ISO9000, CMM, etc). XP has some very good features, though, some of which I've incorporated into my day-to-day work. One is a strong belief in unit testing, which has definitely paid off for me. Another is working closely with the customer and setting very small, visible goals that you can easily track. Worth an hour or two at their web site: http://www.extremeprogramming.org/

How To Ask Questions The Smart Way - Eric Raymond has written many interesting papers about programming in general, and especially Open Source. This one is great - it explains how someone can ask questions of programmers in a way that's most likely to generate a successful response. If you're a user then you should read it; if you're a programmer then you'll probably find it handy to point people to: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Revision 4429 Mar 2011 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 66 to 66
 This is related to Demarco and Lister's discussion of "flow" in Peopleware. Here's Joel Spolsky's review of Peopleware: http://www.amazon.com/review/RYVTUPDAUANZW
Somewhat related is the question of what really motivates creative people. Turns out it's not money: http://www.youtube.com/watch?v=rrkrvAUbU9Y
Well-researched presentation about software management (team size, hours, etc): http://www.lostgarden.com/2008/09/rules-of-productivity-presentation.html
\ No newline at end of file
Added:
>
>
Developer Support Handbook - http://www.developer-support-handbook.org/intro.html
In this handbook, I mostly cover the first aspect of providing an API: support. It is probably the least glamorous aspect, but on the other hand, it is vital. You can have the best API in the world, but if people post in your forums and the response is just crickets chirping, then the developers will not stick around for very long. On the other hand, if you treat your developers well, then they will (for free) provide you with valuable insights about ways to improve your API, and they will evangelize your API for you.
 \ No newline at end of file

Revision 4316 Mar 2011 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 10 to 10
  git is a distributed revision control system. http://git.or.cz/
Changed:
<
<
http://news.ycombinator.com/item?id=2179123 - excellent intro to version control and git
http://progit.org/book/ - git book (online and available in print)
http://www-cs-students.stanford.edu/~blynn/gitmagic/ - the best "gentle introduction" to git that I've found.
http://jointheconversation.org/2008/06/02/railsconf-git-talk/ - excellent introductory screencast. about an hour long, but well worth it
http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.
http://www.sanityinc.com/articles/partial-emacs-git-svn-mode - some tips for emacs and git-svn
http://www.newartisans.com/blog_files/git.from.bottom.up.php - git from the bottom up
http://www.eqqon.com/index.php/Collaborative_Github_Workflow

If you're trying to use a non-default ssh key with git (e.g. for github) then this will help: http://help.github.com/multiple-keys/

You can store your "dotfiles" in git, too, which is especially great now that we do so much work inside virtual machines. There seem to be two schools of thought:

I'm trying the first approach. It seems less complex.

Setting up a new machine looks like:

$ cd
$ git init .
$ git remote add caboteria ssh://user@host/path_to_repo/dotfiles.git
$ git fetch caboteria mitre:caboteria/mitre
$ git checkout -fb mitre caboteria/mitre

http://vcs-home.madduck.net/ - turns out there's a group of people that talk about how they've done this.

>
>
GitNotes
  CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

Revision 4214 Mar 2011 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 90 to 90
  Maker's Schedule - a very interesting article about how "makers" and managers view time differently: http://paulgraham.com/makersschedule.html
This is related to Demarco and Lister's discussion of "flow" in Peopleware. Here's Joel Spolsky's review of Peopleware: http://www.amazon.com/review/RYVTUPDAUANZW
Deleted:
<
<
Somewhat related is the question of what really motivates creative people. Turns out it's not money: http://www.youtube.com/watch?v=rrkrvAUbU9Y
 \ No newline at end of file
Added:
>
>
Somewhat related is the question of what really motivates creative people. Turns out it's not money: http://www.youtube.com/watch?v=rrkrvAUbU9Y
Well-researched presentation about software management (team size, hours, etc): http://www.lostgarden.com/2008/09/rules-of-productivity-presentation.html

Revision 4106 Feb 2011 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 10 to 10
  git is a distributed revision control system. http://git.or.cz/
Added:
>
>
http://news.ycombinator.com/item?id=2179123 - excellent intro to version control and git
 http://progit.org/book/ - git book (online and available in print)
http://www-cs-students.stanford.edu/~blynn/gitmagic/ - the best "gentle introduction" to git that I've found.
http://jointheconversation.org/2008/06/02/railsconf-git-talk/ - excellent introductory screencast. about an hour long, but well worth it

Revision 4017 Jan 2011 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 88 to 88
 A fun rant about how "unicode" is not the same thing as "utf-8": http://enjoydoingitwrong.wordpress.com/2009/06/22/unicode-is-not-utf/

Maker's Schedule - a very interesting article about how "makers" and managers view time differently: http://paulgraham.com/makersschedule.html

Deleted:
<
<
This is related to Demarco and Lister's discussion of "flow" in Peopleware. Here's Joel Spolsky's review of Peopleware: http://www.amazon.com/review/RYVTUPDAUANZW
 \ No newline at end of file
Added:
>
>
This is related to Demarco and Lister's discussion of "flow" in Peopleware. Here's Joel Spolsky's review of Peopleware: http://www.amazon.com/review/RYVTUPDAUANZW
Somewhat related is the question of what really motivates creative people. Turns out it's not money: http://www.youtube.com/watch?v=rrkrvAUbU9Y
 \ No newline at end of file

Revision 3919 Nov 2010 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 35 to 35
 $ git checkout -fb mitre caboteria/mitre
Added:
>
>
http://vcs-home.madduck.net/ - turns out there's a group of people that talk about how they've done this.
 CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool! (You can make TortoiseCVS play nicely with Cygwin if you tell TortoiseCVS to use your Cygwin home directory as its home. That way you can check out a directory tree using TortoiseCVS and then do cvs operations in Cygwin without having to login again. right click->CVS->Preferences... then click on the "Quirky" tab)

Revision 3819 Nov 2010 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 24 to 24
 
Added:
>
>
I'm trying the first approach. It seems less complex.

Setting up a new machine looks like:

$ cd
$ git init .
$ git remote add caboteria ssh://user@host/path_to_repo/dotfiles.git
$ git fetch caboteria mitre:caboteria/mitre
$ git checkout -fb mitre caboteria/mitre
 CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool! (You can make TortoiseCVS play nicely with Cygwin if you tell TortoiseCVS to use your Cygwin home directory as its home. That way you can check out a directory tree using TortoiseCVS and then do cvs operations in Cygwin without having to login again. right click->CVS->Preferences... then click on the "Quirky" tab)

Revision 3719 Nov 2010 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 20 to 20
  If you're trying to use a non-default ssh key with git (e.g. for github) then this will help: http://help.github.com/multiple-keys/
Added:
>
>
You can store your "dotfiles" in git, too, which is especially great now that we do so much work inside virtual machines. There seem to be two schools of thought:
 CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool! (You can make TortoiseCVS play nicely with Cygwin if you tell TortoiseCVS to use your Cygwin home directory as its home. That way you can check out a directory tree using TortoiseCVS and then do cvs operations in Cygwin without having to login again. right click->CVS->Preferences... then click on the "Quirky" tab)

Revision 3627 Oct 2010 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 18 to 18
 http://www.newartisans.com/blog_files/git.from.bottom.up.php - git from the bottom up
http://www.eqqon.com/index.php/Collaborative_Github_Workflow
Added:
>
>
If you're trying to use a non-default ssh key with git (e.g. for github) then this will help: http://help.github.com/multiple-keys/
 CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool! (You can make TortoiseCVS play nicely with Cygwin if you tell TortoiseCVS to use your Cygwin home directory as its home. That way you can check out a directory tree using TortoiseCVS and then do cvs operations in Cygwin without having to login again. right click->CVS->Preferences... then click on the "Quirky" tab)

Revision 3505 Oct 2010 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 10 to 10
  git is a distributed revision control system. http://git.or.cz/
Changed:
<
<
http://progit.org/book/ - git book (online and available in print)
>
>
http://progit.org/book/ - git book (online and available in print)
 http://www-cs-students.stanford.edu/~blynn/gitmagic/ - the best "gentle introduction" to git that I've found.
http://jointheconversation.org/2008/06/02/railsconf-git-talk/ - excellent introductory screencast. about an hour long, but well worth it
http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.
http://www.sanityinc.com/articles/partial-emacs-git-svn-mode - some tips for emacs and git-svn
http://www.newartisans.com/blog_files/git.from.bottom.up.php - git from the bottom up
Added:
>
>
http://www.eqqon.com/index.php/Collaborative_Github_Workflow
  CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

Revision 3428 Jul 2009 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 10 to 10
  git is a distributed revision control system. http://git.or.cz/
Added:
>
>
http://progit.org/book/ - git book (online and available in print)
 http://www-cs-students.stanford.edu/~blynn/gitmagic/ - the best "gentle introduction" to git that I've found.
http://jointheconversation.org/2008/06/02/railsconf-git-talk/ - excellent introductory screencast. about an hour long, but well worth it
http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.

Revision 3324 Jul 2009 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 65 to 65
  Unicode - the best quick intro I've seen: http://wiki.secondlife.com/wiki/Unicode_In_5_Minutes , and another that goes deeper: http://dmiessler.com/study/encoding/
A fun rant about how "unicode" is not the same thing as "utf-8": http://enjoydoingitwrong.wordpress.com/2009/06/22/unicode-is-not-utf/
Added:
>
>
Maker's Schedule - a very interesting article about how "makers" and managers view time differently: http://paulgraham.com/makersschedule.html
This is related to Demarco and Lister's discussion of "flow" in Peopleware. Here's Joel Spolsky's review of Peopleware: http://www.amazon.com/review/RYVTUPDAUANZW

Revision 3222 Jun 2009 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 22 to 22
  arch is another version control system that attempts to fix the problems in CVS while adding new features. It's had an interesting life so far; the primary developer went bust while writing it and it's since been picked up by other folks and has become a GNU project. http://www.gnu.org/software/gnu-arch/
Changed:
<
<
darcs is a patch-oriented version control system. It's interesting in that it doesn't look at code in terms of a tree that evolves over time, but in terms of a set of patches that product a desired result. http://abridgegame.org/darcs/
>
>
darcs is a patch-oriented version control system. It's interesting in that it doesn't look at code in terms of a tree that evolves over time, but in terms of a set of patches that product a desired result. http://darcs.net/
  mercurial is changeset-oriented system. It's supposedly the leading candidate to become the next-gen Linux SCM if Linus decides to switch away from git. http://www.selenic.com/mercurial/
Line: 63 to 63
  Markup Languages - XML, despite what Java folks will tell you, isn't the be-all and end-all of markup languages. The interesting discussion at http://www.reddit.com/r/programming/comments/7muux/ogdl_an_incredibly_lightweight_markup_language/ discusses OGDL, YAML, and XML and how they compare to one another.
Changed:
<
<
Unicode - the best quick intro I've seen: http://wiki.secondlife.com/wiki/Unicode_In_5_Minutes , and another that goes deeper: http://dmiessler.com/study/encoding/
>
>
Unicode - the best quick intro I've seen: http://wiki.secondlife.com/wiki/Unicode_In_5_Minutes , and another that goes deeper: http://dmiessler.com/study/encoding/
A fun rant about how "unicode" is not the same thing as "utf-8": http://enjoydoingitwrong.wordpress.com/2009/06/22/unicode-is-not-utf/

Revision 3102 Mar 2009 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 63 to 63
  Markup Languages - XML, despite what Java folks will tell you, isn't the be-all and end-all of markup languages. The interesting discussion at http://www.reddit.com/r/programming/comments/7muux/ogdl_an_incredibly_lightweight_markup_language/ discusses OGDL, YAML, and XML and how they compare to one another.
Deleted:
<
<
*Unicode in 5 minutes8 - the best quick intro I've seen: http://wiki.secondlife.com/wiki/Unicode_In_5_Minutes
 \ No newline at end of file
Added:
>
>
Unicode - the best quick intro I've seen: http://wiki.secondlife.com/wiki/Unicode_In_5_Minutes , and another that goes deeper: http://dmiessler.com/study/encoding/

Revision 3002 Mar 2009 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 62 to 62
 How to denote numeric ranges - http://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html In summary, use lower ≤ i < upper. Another way to describe these is "half-open ranges": http://www.siliconbrain.com/ranges.htm

Markup Languages - XML, despite what Java folks will tell you, isn't the be-all and end-all of markup languages. The interesting discussion at http://www.reddit.com/r/programming/comments/7muux/ogdl_an_incredibly_lightweight_markup_language/ discusses OGDL, YAML, and XML and how they compare to one another. \ No newline at end of file

Added:
>
>
*Unicode in 5 minutes8 - the best quick intro I've seen: http://wiki.secondlife.com/wiki/Unicode_In_5_Minutes
 \ No newline at end of file

Revision 2902 Jan 2009 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 60 to 60
 Notes on Distributed Computing - http://research.sun.com/techrep/1994/abstract-29.html Sun labs researchers point out the ways in which writing distributed computer programs is different than writing local ones.

How to denote numeric ranges - http://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html In summary, use lower ≤ i < upper. Another way to describe these is "half-open ranges": http://www.siliconbrain.com/ranges.htm \ No newline at end of file

Added:
>
>
Markup Languages - XML, despite what Java folks will tell you, isn't the be-all and end-all of markup languages. The interesting discussion at http://www.reddit.com/r/programming/comments/7muux/ogdl_an_incredibly_lightweight_markup_language/ discusses OGDL, YAML, and XML and how they compare to one another.
 \ No newline at end of file

Revision 2803 Dec 2008 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 14 to 14
 http://jointheconversation.org/2008/06/02/railsconf-git-talk/ - excellent introductory screencast. about an hour long, but well worth it
http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.
http://www.sanityinc.com/articles/partial-emacs-git-svn-mode - some tips for emacs and git-svn
Changed:
<
<
>
>
http://www.newartisans.com/blog_files/git.from.bottom.up.php - git from the bottom up
  CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

Revision 2708 Jul 2008 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 20 to 20
  CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool! (You can make TortoiseCVS play nicely with Cygwin if you tell TortoiseCVS to use your Cygwin home directory as its home. That way you can check out a directory tree using TortoiseCVS and then do cvs operations in Cygwin without having to login again. right click->CVS->Preferences... then click on the "Quirky" tab)
Changed:
<
<
arch is another version control system that attempts to fix the problems in CVS while adding new features. It's had an interesting life so far; the primary developer went bust while writing it and it's since been picked up by other folks. http://www.fifthvision.net/open/bin/view/Arch
>
>
arch is another version control system that attempts to fix the problems in CVS while adding new features. It's had an interesting life so far; the primary developer went bust while writing it and it's since been picked up by other folks and has become a GNU project. http://www.gnu.org/software/gnu-arch/
  darcs is a patch-oriented version control system. It's interesting in that it doesn't look at code in terms of a tree that evolves over time, but in terms of a set of patches that product a desired result. http://abridgegame.org/darcs/

Revision 2622 Jun 2008 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 11 to 11
 git is a distributed revision control system. http://git.or.cz/

http://www-cs-students.stanford.edu/~blynn/gitmagic/ - the best "gentle introduction" to git that I've found.

Added:
>
>
http://jointheconversation.org/2008/06/02/railsconf-git-talk/ - excellent introductory screencast. about an hour long, but well worth it
 http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.
http://www.sanityinc.com/articles/partial-emacs-git-svn-mode - some tips for emacs and git-svn

Revision 2520 Jun 2008 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 11 to 11
 git is a distributed revision control system. http://git.or.cz/

http://www-cs-students.stanford.edu/~blynn/gitmagic/ - the best "gentle introduction" to git that I've found.

Changed:
<
<
http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.
>
>
http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.
http://www.sanityinc.com/articles/partial-emacs-git-svn-mode - some tips for emacs and git-svn
  CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

Revision 2412 Apr 2008 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 8 to 8
 

Source Code Control

Added:
>
>
git is a distributed revision control system. http://git.or.cz/

http://www-cs-students.stanford.edu/~blynn/gitmagic/ - the best "gentle introduction" to git that I've found.
http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.

 CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool! (You can make TortoiseCVS play nicely with Cygwin if you tell TortoiseCVS to use your Cygwin home directory as its home. That way you can check out a directory tree using TortoiseCVS and then do cvs operations in Cygwin without having to login again. right click->CVS->Preferences... then click on the "Quirky" tab)

Line: 18 to 23
  mercurial is changeset-oriented system. It's supposedly the leading candidate to become the next-gen Linux SCM if Linus decides to switch away from git. http://www.selenic.com/mercurial/
Deleted:
<
<
http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.
 

Misc

Revision 2321 Jan 2008 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 18 to 18
  mercurial is changeset-oriented system. It's supposedly the leading candidate to become the next-gen Linux SCM if Linus decides to switch away from git. http://www.selenic.com/mercurial/
Added:
>
>
http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn.
 

Misc

Producing Open Source Software - http://producingoss.com/ "is a book about the human side of open source development. It describes how successful projects operate, the expectations of users and developers, and the culture of free software." From a quick skim of the table of contents (the whole book is online) it looks to be very complete.

Revision 2228 Dec 2007 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 50 to 50
  Notes on Distributed Computing - http://research.sun.com/techrep/1994/abstract-29.html Sun labs researchers point out the ways in which writing distributed computer programs is different than writing local ones.
Changed:
<
<
How to denote numeric ranges - http://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html In summary, use lower ≤ i < upper.
>
>
How to denote numeric ranges - http://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html In summary, use lower ≤ i < upper. Another way to describe these is "half-open ranges": http://www.siliconbrain.com/ranges.htm

Revision 2102 Aug 2006 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 50 to 50
  Notes on Distributed Computing - http://research.sun.com/techrep/1994/abstract-29.html Sun labs researchers point out the ways in which writing distributed computer programs is different than writing local ones.
Added:
>
>
How to denote numeric ranges - http://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html In summary, use lower ≤ i < upper.

Revision 2023 Nov 2005 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 20 to 20
 

Misc

Added:
>
>
Producing Open Source Software - http://producingoss.com/ "is a book about the human side of open source development. It describes how successful projects operate, the expectations of users and developers, and the culture of free software." From a quick skim of the table of contents (the whole book is online) it looks to be very complete.
 Project Life Cycle - is a collection of very useful info regarding the various phases a software project goes through over its life cycle. It also includes some template documents which are useful for interaction between the client and consultant. http://www.cratchit.org/dleigh/plc/plc-index.htm

Software Architecture - is an extremely nebulous term in the context of software. Everyone agrees that it's important, but nobody really agrees on what it is. This site is a useful resource, though. http://www.bredemeyer.com/

Revision 1921 Jul 2005 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 6 to 6
 
Added:
>
>

Source Code Control

 CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool! (You can make TortoiseCVS play nicely with Cygwin if you tell TortoiseCVS to use your Cygwin home directory as its home. That way you can check out a directory tree using TortoiseCVS and then do cvs operations in Cygwin without having to login again. right click->CVS->Preferences... then click on the "Quirky" tab)

Line: 14 to 16
  darcs is a patch-oriented version control system. It's interesting in that it doesn't look at code in terms of a tree that evolves over time, but in terms of a set of patches that product a desired result. http://abridgegame.org/darcs/
Added:
>
>
mercurial is changeset-oriented system. It's supposedly the leading candidate to become the next-gen Linux SCM if Linus decides to switch away from git. http://www.selenic.com/mercurial/

Misc

 Project Life Cycle - is a collection of very useful info regarding the various phases a software project goes through over its life cycle. It also includes some template documents which are useful for interaction between the client and consultant. http://www.cratchit.org/dleigh/plc/plc-index.htm

Software Architecture - is an extremely nebulous term in the context of software. Everyone agrees that it's important, but nobody really agrees on what it is. This site is a useful resource, though. http://www.bredemeyer.com/

Revision 1815 Mar 2004 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 38 to 38
 Agile Manifesto - http://agilemanifesto.org/
Changed:
<
<
Programming With Tracer Bullets - http://today.java.net/pub/a/today/2004/02/23/davenandy2.html I agree with most of what these guys are talking about. The more you try to "anticipate" what you're going to need in the distant future the more that you're guessing. Start small and build on that. I love the "programming is gardening" metaphor.
>
>
Gardening With Tracer Bullets - http://today.java.net/pub/a/today/2004/02/23/davenandy2.html I agree with most of what these guys are talking about. The more you try to "anticipate" what you're going to need in the distant future the more that you're guessing. Start small and build on that. I love the "programming is gardening" metaphor.

Notes on Distributed Computing - http://research.sun.com/techrep/1994/abstract-29.html Sun labs researchers point out the ways in which writing distributed computer programs is different than writing local ones.

Revision 1725 Feb 2004 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 36 to 36
 

Agile Manifesto - http://agilemanifesto.org/

Added:
>
>

Programming With Tracer Bullets - http://today.java.net/pub/a/today/2004/02/23/davenandy2.html I agree with most of what these guys are talking about. The more you try to "anticipate" what you're going to need in the distant future the more that you're guessing. Start small and build on that. I love the "programming is gardening" metaphor.

Revision 1625 Feb 2004 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="TechBookmarks"
Line: 34 to 34
  Communicating Sequential Processes - http://www.usingcsp.com/ a theoretically sound approach to concurrent programming.
Added:
>
>
Agile Manifesto - http://agilemanifesto.org/

Revision 1517 Feb 2004 - TobyCabot

Line: 1 to 1
Changed:
<
<
( back to TechBookmarks )
>
>
META TOPICPARENT name="TechBookmarks"
 

Revision 1421 May 2003 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 32 to 32
 Financial Calculations - http://quantlib.org/ is an open-source C++ library for sophisticated financial calculations.

Linux in the Workplace - http://linuxpip.org/ is a book that talks about how to use Linux in a business environment.

Added:
>
>
Communicating Sequential Processes - http://www.usingcsp.com/ a theoretically sound approach to concurrent programming.

Revision 1308 Apr 2003 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 13 to 13
  arch is another version control system that attempts to fix the problems in CVS while adding new features. It's had an interesting life so far; the primary developer went bust while writing it and it's since been picked up by other folks. http://www.fifthvision.net/open/bin/view/Arch
Added:
>
>
darcs is a patch-oriented version control system. It's interesting in that it doesn't look at code in terms of a tree that evolves over time, but in terms of a set of patches that product a desired result. http://abridgegame.org/darcs/
 Project Life Cycle - is a collection of very useful info regarding the various phases a software project goes through over its life cycle. It also includes some template documents which are useful for interaction between the client and consultant. http://www.cratchit.org/dleigh/plc/plc-index.htm

Software Architecture - is an extremely nebulous term in the context of software. Everyone agrees that it's important, but nobody really agrees on what it is. This site is a useful resource, though. http://www.bredemeyer.com/

Revision 1226 Feb 2003 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 28 to 28
 Binary Arithmetic Considered Harmful - It's not commonly understood that binary numbers are imprecise to the right of the decimal point. http://www-106.ibm.com/developerworks/java/library/j-jtp0114/ is a good intro to floating point and its problems. Although Java-centric, it has a good introduction to the topic and good references.

Financial Calculations - http://quantlib.org/ is an open-source C++ library for sophisticated financial calculations.

Added:
>
>
Linux in the Workplace - http://linuxpip.org/ is a book that talks about how to use Linux in a business environment.

Revision 1105 Feb 2003 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 25 to 25
  RFC's - are the documents that describe internet protocols. There are many ways to get them; among them are raw and cooked.
Changed:
<
<
Floating Point - It's not commonly understood that binary floating-point numbers are imprecise. http://www-106.ibm.com/developerworks/java/library/j-jtp0114/ is a good intro to floating point and its problems. Although Java-centric, it has a good introduction to the topic and good references.
>
>
Binary Arithmetic Considered Harmful - It's not commonly understood that binary numbers are imprecise to the right of the decimal point. http://www-106.ibm.com/developerworks/java/library/j-jtp0114/ is a good intro to floating point and its problems. Although Java-centric, it has a good introduction to the topic and good references.

Financial Calculations - http://quantlib.org/ is an open-source C++ library for sophisticated financial calculations.

Revision 1028 Jan 2003 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 9 to 9
  CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm
Changed:
<
<
CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool!
>
>
CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool! (You can make TortoiseCVS play nicely with Cygwin if you tell TortoiseCVS to use your Cygwin home directory as its home. That way you can check out a directory tree using TortoiseCVS and then do cvs operations in Cygwin without having to login again. right click->CVS->Preferences... then click on the "Quirky" tab)
  arch is another version control system that attempts to fix the problems in CVS while adding new features. It's had an interesting life so far; the primary developer went bust while writing it and it's since been picked up by other folks. http://www.fifthvision.net/open/bin/view/Arch

Revision 926 Jan 2003 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 7 to 7
 
Changed:
<
<
CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.html
>
>
CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.htm

CVS is fundamentally a UNIX program, but there are several different clients available. WinCVS is the most commonly used, but it's not very easy for non-technical people to use. At a couple of shops I've worked at we used CVS for code and Microsoft's VSS for documents. This is a bad idea for a lot of reasons, not least of which is that it requires you to use Windows to access version control. That's why I'm really excited about TortoiseCVS http://www.tortoisecvs.org/ which is a very well-designed Windows interface for CVS. It plugs into the Windows File Explorer so there's no new UI to learn; you perform version control operations from within a tool that everybody already knows how to use. Cool!

  arch is another version control system that attempts to fix the problems in CVS while adding new features. It's had an interesting life so far; the primary developer went bust while writing it and it's since been picked up by other folks. http://www.fifthvision.net/open/bin/view/Arch

Revision 823 Jan 2003 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 7 to 7
 
Changed:
<
<
CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvs.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.html
>
>
CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvshome.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.html
  arch is another version control system that attempts to fix the problems in CVS while adding new features. It's had an interesting life so far; the primary developer went bust while writing it and it's since been picked up by other folks. http://www.fifthvision.net/open/bin/view/Arch

Revision 716 Jan 2003 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 9 to 9
  CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvs.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.html
Added:
>
>
arch is another version control system that attempts to fix the problems in CVS while adding new features. It's had an interesting life so far; the primary developer went bust while writing it and it's since been picked up by other folks. http://www.fifthvision.net/open/bin/view/Arch
 Project Life Cycle - is a collection of very useful info regarding the various phases a software project goes through over its life cycle. It also includes some template documents which are useful for interaction between the client and consultant. http://www.cratchit.org/dleigh/plc/plc-index.htm

Software Architecture - is an extremely nebulous term in the context of software. Everyone agrees that it's important, but nobody really agrees on what it is. This site is a useful resource, though. http://www.bredemeyer.com/

Line: 20 to 22
 How to Report Bugs Effectively - http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

RFC's - are the documents that describe internet protocols. There are many ways to get them; among them are raw and cooked.

Added:
>
>
Floating Point - It's not commonly understood that binary floating-point numbers are imprecise. http://www-106.ibm.com/developerworks/java/library/j-jtp0114/ is a good intro to floating point and its problems. Although Java-centric, it has a good introduction to the topic and good references.

Revision 628 Apr 2002 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 17 to 17
  How To Ask Questions The Smart Way - Eric Raymond has written many interesting papers about programming in general, and especially Open Source. This one is great - it explains how someone can ask questions of programmers in a way that's most likely to generate a successful response. If you're a user then you should read it; if you're a programmer then you'll probably find it handy to point people to: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Added:
>
>
How to Report Bugs Effectively - http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
 RFC's - are the documents that describe internet protocols. There are many ways to get them; among them are raw and cooked.

Revision 521 Mar 2002 - TobyCabot

Line: 1 to 1
 ( back to TechBookmarks )

Line: 11 to 11
  Project Life Cycle - is a collection of very useful info regarding the various phases a software project goes through over its life cycle. It also includes some template documents which are useful for interaction between the client and consultant. http://www.cratchit.org/dleigh/plc/plc-index.htm
Changed:
<
<
Software Archtitecture - is an extremely nebulous term in the context of software. Everyone agrees that it's important, but nobody really agrees on what it is. This site is a useful resource, though. http://www.bredemeyer.com/
>
>
Software Architecture - is an extremely nebulous term in the context of software. Everyone agrees that it's important, but nobody really agrees on what it is. This site is a useful resource, though. http://www.bredemeyer.com/
  Extreme Programming - is a recent fad methodology, and I've pretty much hated the various programming fads that preceded it (TQM, ISO9000, CMM, etc). XP has some very good features, though, some of which I've incorporated into my day-to-day work. One is a strong belief in unit testing, which has definitely paid off for me. Another is working closely with the customer and setting very small, visible goals that you can easily track. Worth an hour or two at their web site: http://www.extremeprogramming.org/

How To Ask Questions The Smart Way - Eric Raymond has written many interesting papers about programming in general, and especially Open Source. This one is great - it explains how someone can ask questions of programmers in a way that's most likely to generate a successful response. If you're a user then you should read it; if you're a programmer then you'll probably find it handy to point people to: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Added:
>
>
RFC's - are the documents that describe internet protocols. There are many ways to get them; among them are raw and cooked.

Revision 415 Dec 2001 - TobyCabot

Line: 1 to 1
Changed:
<
<
( back to WebBookmarks -or- back to WebHome )
>
>
( back to TechBookmarks )
 

Revision 314 Sep 2001 - TobyCabot

Line: 1 to 1
Changed:
<
<
( back to WebBookmarks )
>
>
( back to WebBookmarks -or- back to WebHome )
 
Line: 14 to 14
  Extreme Programming - is a recent fad methodology, and I've pretty much hated the various programming fads that preceded it (TQM, ISO9000, CMM, etc). XP has some very good features, though, some of which I've incorporated into my day-to-day work. One is a strong belief in unit testing, which has definitely paid off for me. Another is working closely with the customer and setting very small, visible goals that you can easily track. Worth an hour or two at their web site: http://www.extremeprogramming.org/
Added:
>
>
How To Ask Questions The Smart Way - Eric Raymond has written many interesting papers about programming in general, and especially Open Source. This one is great - it explains how someone can ask questions of programmers in a way that's most likely to generate a successful response. If you're a user then you should read it; if you're a programmer then you'll probably find it handy to point people to: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Revision 206 Sep 2001 - TobyCabot

Line: 1 to 1
 ( back to WebBookmarks )

Added:
>
>
 
Line: 11 to 12
  Software Archtitecture - is an extremely nebulous term in the context of software. Everyone agrees that it's important, but nobody really agrees on what it is. This site is a useful resource, though. http://www.bredemeyer.com/
Added:
>
>
Extreme Programming - is a recent fad methodology, and I've pretty much hated the various programming fads that preceded it (TQM, ISO9000, CMM, etc). XP has some very good features, though, some of which I've incorporated into my day-to-day work. One is a strong belief in unit testing, which has definitely paid off for me. Another is working closely with the customer and setting very small, visible goals that you can easily track. Worth an hour or two at their web site: http://www.extremeprogramming.org/

Revision 111 Jul 2001 - TobyCabot

Line: 1 to 1
Added:
>
>
( back to WebBookmarks )

CVS is the Concurrent Versions System, a tool for source code revision control. The CVS home page is at http://www.cvs.org/ and the User's Guide (also called the "Cederqvist Manual" because it was written by a guy named Per Cederqvist) is at http://www.loria.fr/~molli/cvs/doc/cvs_toc.html. A book called "Open Source Development With CVS" is partially online. The parts that are online seem to overlap substantially with the Cederqvist book but might be useful: http://cvsbook.red-bean.com/cvsbook.html

Project Life Cycle - is a collection of very useful info regarding the various phases a software project goes through over its life cycle. It also includes some template documents which are useful for interaction between the client and consultant. http://www.cratchit.org/dleigh/plc/plc-index.htm

Software Archtitecture - is an extremely nebulous term in the context of software. Everyone agrees that it's important, but nobody really agrees on what it is. This site is a useful resource, though. http://www.bredemeyer.com/

View topic | History: r54 < r53 < r52 < r51 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding The Caboteria? Send feedback