• I agree with the other persons that have posted and stated that today Code Projects have application requirements, end user requirements by roles, programing bugs, and end user issues.

    With todays available tools you can and should always test for and resolve pre-release any issues with application requirements, end user requirements by roles, and programing bugs.

    I have never worked anywhere that called or considered an end user workflow issue a bug.

    This includes any misunderstood application workflow issues.

    These have always been considered a missed or new requirement for a new feature.

    Deffinately had my share of issues with poor memory management and/or data typing back in the day.

    IMHO: Everyone that used a first or second generation abstraction language did.

    Now with the programing languages, massive amounts of cheap physical memory for use, solid definitions for data types that are portable across platforms and languages, etc... the Bug's of yesterday have turned into the IT equivalent of Polio or the Black Plague.

    However we still have our issues. As systems become more open, interconnected, and protable the "NEW BUGS" are more about the security of an application or system is from external unwanted interferance or influence. How safe is your code, application, production systems from being affected by an unwanted third party influence?

    Sure we still have code annoyances that can be resolved by patches and updates, those will always occur.

    But there was a time, and there will be again, where everything we do and how we do it will have to be changed before what is broken can be reparied.

    Just ask SONY how close we are to that time again....

    Recently they had a real good taste of things to come... 😎