|more useful options|
Code "taste", coding guidelines, and revision control systemsby afoken (Chancellor)
|on Sep 16, 2016 at 21:24 UTC||Need Help??|
(Just thinking out lout a little bit more after writing Re: Starting a New Script ...)
A long time ago, in a
And of course, we were right. DF wrote the code, and nobody else touched it after that. Just for fun, we tried that with other pieces of code the team members wrote over the years, and we were often right. We could even guess who wrote the original code, and who changed it later.
When we later explained our little game and its origin to non-IT people, we compared it to wine tasting, and to guessing an author from a piece of text.
In the next episode, same
And of course, we were right again.
Using revision control systems makes the guessing game a lot less interesting (svn log, svn blame), and using strict coding rules and code templates generates more uniform code across the team.
But still then, without looking at the logs, you can see differences in the way team members write code. And you can often identify who wrote a piece of code: "Soft factors" like the length and complexity of subroutines, naming of identifiers, style of the embedded documentation (POD, doxygen), systematic spelling errors in identifiers and documentation, preferred algorithms, and so on.
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)