tag:blogger.com,1999:blog-7641928.post111659635646656146..comments2024-03-27T03:14:37.389-04:00Comments on The Grey Lines: Developers and InfrastructureMark Griffinhttp://www.blogger.com/profile/06696309270838259732noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7641928.post-1124369066121418152005-08-18T08:44:00.000-04:002005-08-18T08:44:00.000-04:00I'm a big fan of being a mile wide and, well, pret...I'm a big fan of being a mile wide and, well, pretty deep, too.<BR/><BR/>Perhaps if the developer is "sheltered" by an effective IT organization that provides the appropriate layers of review to inspect-in coding to handle the things that can go wrong in the infrastructure layer, then the developer doesn't have to understand much about things outside of the development tool.<BR/><BR/>However, solid understanding of hardware, OS, network, security, database issues are absolutely essential to being a good architect or an effective consultant.<BR/><BR/>I can't count the number of times that I've taken on a new client only to find out that I'm the most knowledgeable about their own infrastructure within a matter of a few weeks (OK, sometimes a few days).<BR/><BR/>Developers and Infrastructure... don't kid yourself you gotta know it to be good.<BR/><BR/>-MAnonymousnoreply@blogger.com