Comments on: Top Developer Security Pet Peeves, What Are Yours? http://blog.impactalabs.com/2009/02/17/top-developer-security-pet-peeves-what-are-yours/ Sun, 06 Jun 2010 23:16:06 +0000 hourly 1 http://wordpress.com/ By: Kevin Lam (IMPACTA) http://blog.impactalabs.com/2009/02/17/top-developer-security-pet-peeves-what-are-yours/#comment-137 Kevin Lam (IMPACTA) Thu, 26 Feb 2009 22:03:56 +0000 http://blog.impactalabs.com/?p=369#comment-137 Hey Hal, those are really good ones and ones that I hear pretty often -- that the processes imposed don't seem to add value or make sense! I'll add that those processes have a good reason behind them (I am guilty of helping make some of those processes), but the real problem is that the value/purpose isn't apparent too all parties! Thanks for your post and sharing your thoughts Hal! --Kevin Hey Hal, those are really good ones and ones that I hear pretty often — that the processes imposed don’t seem to add value or make sense! I’ll add that those processes have a good reason behind them (I am guilty of helping make some of those processes), but the real problem is that the value/purpose isn’t apparent too all parties! Thanks for your post and sharing your thoughts Hal!

–Kevin

]]> By: Hal Martin http://blog.impactalabs.com/2009/02/17/top-developer-security-pet-peeves-what-are-yours/#comment-135 Hal Martin Thu, 26 Feb 2009 15:11:51 +0000 http://blog.impactalabs.com/?p=369#comment-135 My biggest pet peeve is the excessive bureaucracy imposed by Software Engineering. For example, trying to impose a coding standard (variable names, method names) on a Visual Studio project which is inconsistent with the coding standard used for .NET classes. For example, mindlessly following some software process (Agile, SCRUM) even when it makes no sense. My biggest pet peeve is the excessive bureaucracy imposed by Software Engineering. For example, trying to impose a coding standard (variable names, method names) on a Visual Studio project which is inconsistent with the coding standard used for .NET classes. For example, mindlessly following some software process (Agile, SCRUM) even when it makes no sense.

]]>