I recently came across an interesting tool for looking at source code metrics SourceMonitor from Campwood Software.  This tool looks at source within a set of sub-directories and gives you basic measures about your software.

The following are a sample of measures captured through this application:

• Total Source Lines
• Total Statements
• Percentage of documentation
• Complexity
• Block Depth

A very interesting chart is the summary one below; this gives you an idea of how well your source fits within a predefined set of measures.

When developing software, you need great strategies and tactics to succeed.

You may have an excellent vision on what you want to get to and a well thought-out approach; however if the developers writing the code mess up the implementation or don't follow the requirements your strategy will be meaningless.

On the other hand you could have the most experienced hardworking developers working on your project.  If they get sent in the wrong direction based upon a faulty strategy either due to lack of experience, lack of experience with the technology, requirements that aren't clear, picking the wrong technology, methodology or incorrect architecture your project could be in real trouble.

Finding the right combination of strategy and tactics can be a challenge, however once the balance is achieved, your project is almost guaranteed to be a success!

Some companies look to technology to achieve this balance however this can truly only be found through experience and/or an effective mature process.

In most cases projects fail or fall short of expectations due to strategy type issues.

Visual Studio .NET 2005 provides a very powerful frameworks for performing web testing.

Here are some tips to make the most out of these features:

• When creating controls on your forms, make sure each control gets an ID even if these controls get created dynamically.  This will give a consistant name for checking fields on post-backs.  If you don't do this VS.NET generates a name like ctl00.  If you move things around on your page, this may become ctl01 and your test will break.
• Besure to take advantage of Context Parameters, these allow you to quickly define constants to be used across tests.

Why the efficient coder?

Well - There are really a number of different motivations/categories to care about the idea of becoming an efficient coder see if you can pick where you're at...

1)  You think you have an extremely stable position where you just show, up cut a little bit of code, not really deliver anything and pick up your paycheck, if this is you this blog really isn't for you...

2)  You have deadlines that never get met, but these deadlines aren't really that important, if the deadlines aren't that important your job/department probably isn't that important and hense when the next round of lay-offs you might be a good candidate, if not you might by in category 1

3)  You care some what about delivering your software on time and your project is understaffed so you're working 50-60 hours per week (an incompetant project manager/boss goes along way to put you into to this category)

4)  You're a consultant and get paid by the hour...the more you can get done in one hour (and sell yourself) goes a long way to boost your hourly rate...would you rather work 40 hours at $100/hr or 80 hours at $50/hr?

Kevin

COMPLE - ATTACH - SWITCH - REFRESH - ENTER

Once changes are made in my application, I speak these words into my microphone.  At that point I can keep my hands on the keyboard and not get distracted by finding the mouse and then making the required clicks. 

Touch Typing is pretty good for keeping your hands on the keyboard and the occasional trip up to the function keys, but keeping your mind on the actual code and not on seaching for the mouse/click points/function keys is key for quickly evolving code.

For more information, please visit www.dasblog.net from newtelligence.