Some things change how you fundamentally program. Automation is one of those
things. It is what will save you from wasting your weekend stepping through
tedious and error-prone processes like regression testing (unit, integration,
performance, functional, etc.), builds, deployment, or even documentation.
Automation is one of those buzzwords we all know our projects should have
(like "performance," "security," "maintainability," etc...), but the question
is how?
Microsoft gave us a huge answer with .NET 2.0's MSBuild - its new build
platform with a process-oriented scripting language. It can revolutionize not
just how you build, but also how you test, deploy, and automate many of your
development processes. The problem with these scripts, like the problem with
anything ... (more)
Automating processes is critical to the success of any software project.
Because computers can perform redundant tasks faster and more reliably than
people, automation becomes more necessary as the processes become larger and
more complicated. This is one of the main drivers behind Test Driven
Development - constantly rerunning an automated build with Unit Tests. This
article will provid... (more)
Web sites are based on a client-server model. While the client (usually a
browser) can use client-side script such as JavaScript to do simple tweaking
of existing data, getting new data requires a request to the server. The
server does the heavy processing and makes a response back, which redraws the
entire Web page. Most development required these interactions to be atomic so
that each ... (more)
Most developers just focus on getting the initial code done, ignoring the
important questions that ultimately affect the total cost of development.
This article will address how to handle these issues in a way that will
benefit the total cost of development.
Beyond Just HelloWorld
In enterprise development, the ability to program the design doc is taken for
granted. Managers and senior de... (more)
After years of nearly every tradeshow, magazine, and technologist saying how
wonderful unit tests are, developers know that they're supposed to write unit
tests. But it's not always that easy. For example, while most developers can
write tests for a trivial class library, it's much harder to write tests for
the database.
There is much value in testing the database - it can contain complic... (more)