Robust Web Application Initialization

When a web based application starts up, it should do so carefully to avoid a number of problems.  This post outlines the problems you might run into, and a list of coding preparations that can be made to avoid these problems.

Module Initialization

Given a module that is designed to be re-used across many applications, what is the correct way to initialize it, and why?

Configuring Date Format

There is endless discussion on how to format dates on the web, but most of this discussion is completely useless because it ignores the real world issue: different users want to see dates differently.  No single date format will be suitable to everyone.  This post is how to structure your product so that everyone sees the date values formatted as they would like to see them.

Advertisement

Two is Not Better Than One

In software design you often must choose between two competing approaches.  Which is better?  It is tempting at times to say “Let’s do both, and let the user choose.”   That might be good, but there are many cases where that is a serious mistake.

#27 A Proper Module does NOT need a Config File

It is common for a system or a program to have a config file: that is a file that holds a bunch of settings that can be adjusted by the administrator or user to get desired effect.  A code module, that is designed to be embedded into a running program and is designed to be reused in multiple programs, should NEVER require a configuration file.

Installer Design Principles

Software needs to be installed.  This has been a large pain point in many of the software products I have seen. Proper installer design can make a huge difference in the supportability of a product.