Skip to main content

"If I Didn't Develop it Custom from Scratch, it's No Good"

It's time for developers to lose the "if I didn't develop it custom from scratch, it's no good" attitude. The other day, we were all sitting around at an internal technology presentation when suddenly, one of my collegues remarks snidely, "...with all these drag-and-drop, code-generating wizards driving development, are my .Net developers going to be writing code anymore?" Another collegue presented .Net Mobile 5.0 and all the new enhancements within Visual Studio 2005. Following the theme of "get developers away from developing plumbing and "every project needs _____ (logging, exception handling, data access, etc.)" code", these Microsoft tools take away many of the headaches involved with mobile development for the Windows Mobile platform.

Get over yourself! Code generators, IDE drag-and-drop functionality, and open/shared source frameworks serve as strong examples of industry innovation. One might be a strong coder/programmer but I believe it's both arrogant and ignorant to think these tools aren't as good as what you can whip up in a day. Bullcrap. If you still think this way then go take your laptop off to a deserted island (you'll want to pack a solar converter) and build applications in a vaccume. Your users...er, user will adore you. I can guarantee your code won't be nearly as robust, feature rich, maintainable, or error-free as what code be reused from commercial or open/shared source.

Unfortunately, I see this behavior every day. Oh sure, you'll plug in a few shared source libraries here and there: Log4J, Ant, whatever. But if it comes to working on a commercial tool such as a BPEL or a business rule engine/product...? No way! Heaven forbid you should get away from the code! What if the product needs modification?! C'mon. Do you really need to modify the Windows Server 2003 source code...? "Sure. I know better than 60,000 Microsoft employees. I do!"

It's an old, tired cliche but developers need to work smarter-not harder. With globalization, I guarantee there are 500 Russian, Chinese, Indian, or Nebraskans who can not only code you under the table but charge 1/5th of what you invoice. If no one else, you owe it to your clients or your firm. Become an innovator. Find the most effective and cost-aware method of accomplishing a task or solving a problem-not the method which most glorifies your precious custom code.

Stop reinventing the wheel out there folks. Plug in the commercial tools and shared libraries when applicable. It will propel your projects toward success, keep the industry innovative, and make our firms far more profitable and productive.

Comments

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)]

I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent!

I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around.

Thanks in advance!

Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario...
I'm workin…

Shrinking WSS (Sharepoint) SQL Server Log Files

Yesterday, while migrating a source repository from StarTeam to TFS, I received the following error:
"TF30042: The database is full. Contact your Team Foundation Server administrator."Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file.

Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve:

Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here.
Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. The Auto_…