a view of the Marsh

...: Chatter by Year

2016

October

2014

March

February

2013

September

July

June

March

February

January

2012

December

November

October

September

August

July

June

May

April

March

February

January

2011

November

October

July

June

May

April

March

February

January

2010

December

November

October

September

August

July

June

May

April

March

February

January

2009

December

November

October

September

August

July

June

May

April

March

February

January

2008

December

November

October

September

August

...: Chatter by Keyword

ASP.NET

Browsers

Business

Cascading Styles (CSS)

Charity Work

Community

Definitions

Design

Education

Ethics

Firefox

First Post

Hockey

I.T. Events

Internet Explorer

Junk mailer/poster

Life

Microsoft

MS Access

Music

Other sports

Printers

Programming

sci-fi

Software

Speaking/Presentations

SQL

Survey

Teaching

The Marsh

Tips & Tricks

Tools of Trade

U.S. Events

Visual Basic (VB.NET)

Web Design

World Events

...: Marsh Chatter

Choices… A Recurring Series

Like many aspects of our lives, there are usually too many selections to choose. For example the menus at a coffee shop or a lunch counter, and then we have our developing tools.

In my years of programming, I’ve created test code to determine the “best” way and/or the “fastest” way to perform an action or to evaluate different code. These tests usually result in “throw-a-way” code. This code is used to quickly prove a condition and then move on.

I will use this article title over time, to cover specific cases that I found beneficial to "show" just how much better or faster one use of code over another actually is. These examples will be considered "throw-a-way" code. They will be developed just enough to show consistent results. The parts you would pull out for a fully developed use, will be identified, however all of the supporting form layout and code to just see the results will be considered "ugly".

The first member of this series will be For Loop vs. Do Loop which will then be morphed or refactored using the .NET String Builder Object. Later I will resurrect code used to confirm that DataReaders are significantly faster than DataSets.

In general, you can just believe what others write or tell you... or you can do it yourself. Sometimes you have to take on the challenge and see for yourself. So follow along and get your hands dirty.