Developer hints/#3093

Nov 13, 2006 / pixtur
Jan 5, 2009 / phsouzacruz

Attached files

No files uploaded
This is a draft by pixtur. It will not be enforced :)

Use SVN to check the changes of othersπ

Having several active developers is very good not only for implementing more, but for implementing better code. Do not think that the other developers are super brains. Check all their changes! Every code can contain bugs, and reading the changes carefully will help us to get our code more stable.

Since the svn-server of sourceforge is so incredibly slow (grrr sourceforge again) checking the changes before updating might be cumbersome. On WindowsXP I do it it this way:
  1. I have one streberdirectory with my head revision.
  2. I have a second directory streber_head which I use for checking updates. I always update streber_head first and then use TotalCommander's "Sync directory" function ( to checkout all changes. If things look weird, I use WinMerge to clean up.
Do not hesitate to ask questions! Although pixtur tends to write some cryptic code, this is not a good habbit. All code should be understood by more than one person.

If something looks strange or cryptic, at a note right into the code:

 if($i = 0) {   #@@@ pixtur 2006-12-10: This looks buggy

The code is not property of a single person! If you need to change something, do it (If you know, what you are doing). If there is no comment block above the function, if was probably written by pixtur. Ask questions!

Review your changes, before committingπ

With TortoiseSVN you can double click on all changed files and review the changes in detail. pixtur is using this not only to write detailed commit messages (as every good developer does), but also to review all is changes. This way he already found a huge number of bugs before anybody was even bugged. :)

No Comments