tag:blogger.com,1999:blog-5706654834612108875.post3995828225709920020..comments2024-02-28T05:07:19.881+02:00Comments on EOH: Microsoft BI and Development : Thou shalt comment thine codeAnonymoushttp://www.blogger.com/profile/14855339893003672250noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-5706654834612108875.post-71328697222880898342012-07-06T09:54:20.434+02:002012-07-06T09:54:20.434+02:00My view is the only place one should comment is on...My view is the only place one should comment is on Blog PostsNick Bowenhttps://www.blogger.com/profile/03439267509567671625noreply@blogger.comtag:blogger.com,1999:blog-5706654834612108875.post-34790334020535319942012-07-05T14:22:51.745+02:002012-07-05T14:22:51.745+02:00Agree with Mark here. If you need to comment, it m...Agree with Mark here. If you need to comment, it means you need to right click and click on refactor :) Yes, keep SQL to (CRUD) simple and fast, thus no comments there as well.Nico Mulderhttps://www.blogger.com/profile/01546475120827964125noreply@blogger.comtag:blogger.com,1999:blog-5706654834612108875.post-69583313381805364052012-07-05T14:01:28.210+02:002012-07-05T14:01:28.210+02:00I like comments above a class giving a 2 line desc...I like comments above a class giving a 2 line description of why it exists but....<br />Comments are old school, needed because us old guys wrote spaghetti code that was covered in more mud code. <br />Good code needs no comment, if you need to comment youve probably written it wrong.<br />There also should be no business code in SQL, so no comments.Mark Biagiohttps://www.blogger.com/profile/08126172267771016761noreply@blogger.comtag:blogger.com,1999:blog-5706654834612108875.post-29629883135911325982012-07-04T14:04:35.807+02:002012-07-04T14:04:35.807+02:00Fanie, I agree with you that excessive commenting ...Fanie, I agree with you that excessive commenting can sometimes add to the 'noise' level of code, making it more difficult to understand (I'm specifically talking about code, not SQL, where comments do help a lot). I've found that if I need comments to explain some code, it usually indicates that the code is too complex and needs re-factoring.<br /><br />However, I also try to at Matthys Meintjeshttps://www.blogger.com/profile/10719783516528359746noreply@blogger.comtag:blogger.com,1999:blog-5706654834612108875.post-958311425755455902012-07-03T17:14:58.183+02:002012-07-03T17:14:58.183+02:00Yet again I personally feel the need NOT to commen...Yet again I personally feel the need NOT to comment on code. For the basic reason being that code should read as English and not at "gibberish". when our code is clean and readable one should never even need comments. This is only my opinion tho but do feel that when it comes to SQL especially, commenting might be the best thing since sliced bread. <br /><br />Nice post overall, love Anonymoushttps://www.blogger.com/profile/15894812919647503492noreply@blogger.comtag:blogger.com,1999:blog-5706654834612108875.post-36899005834328895312012-07-03T14:55:51.756+02:002012-07-03T14:55:51.756+02:00Always interesting when one of the most basic thin...Always interesting when one of the most basic things in development requires justification...we are lazy by nature it seems. I was a compulsive commentor when I coded, and it was always interesting for me to read my own code the next day and find my comment and my code disagreed. Helped to find bugs before deployment though!<br /><br />Regardless of what the lazy techies try to convince us of, Pieter Krugerhttps://www.blogger.com/profile/11118806855467216818noreply@blogger.com