Well, there's the usual suspect, Mr. It Depends. Sounds more like a diaper for geriatric people. However, I'm very comfortable with doing a variety of problem solving on the computer. Sometimes I'll use the IDE to mock up some classes, sometimes I use Visio to do some flow/state charting or more general stuff, sometimes I'll write out the requirements in gory detail in Word or FrontPage, depending on my mood. Oh geez, sometimes I even write unit tests first! Marc

Roger Wright wrote:

So, what about you? Do you take special care in working with date-related code?

I don't see how anyone can use database and programming languages for anything sensible having to do with dates. I mean, come on. You can't even use SQL Server (or couldn't, I actually haven't looked at it in years) for chronology of anything historical before, what 1751? Was that the magic date? And what about MFC or .NET? something like 1901 for the earliest date? It's absurd, IMO. For a long time anytime I had to deal with dates I would use a 3 field structure for year, month, and day, and had my own routines for comparisons. Marc

Rama Krishna Vavilala wrote:

ut considering all the testing and documentation

testing and documentation? Really? From Microsoft??? TLW

Chris Meech wrote:

Like many things in this world that are a challenge to design and build, a lot of the engineering is a compromise between competing or opposing forces. And so it goes too with software

Except, naively I suppose, I have the concept that in other professions, there's such a thing as real process improvement. For example, processes in surgery improve. Of course, we don't expect processes in patient care to improve! So, I guess if I were to take the analogy to its logical extreme, software development is a bureaucratic process, not a scientific process. Hmmm. TLW

* Everything throws an exception, with no thought toward recovery or continuation * Considerations in the architecture for re-use is left until the code is heavily invested in a non-re-use architecture/implementation * Management preaches modular design, actual implementation is tightly coupled Why is it always the same, where ever I go? :sigh: TLW