The Worst Software Experiences: PTC Creo and Enterprise-Level Blunders

Working with software can often be a challenge, but some experiences are truly nightmarish. In this article, we will explore two particularly grueling and frustrating software endeavors that experts have had the misfortune to engage with. The first is the infamous PTC Creo, a Computer-Aided Design (CAD) program that serves as a prime example of software that consistently fails to deliver its intended functionality. The second is a combination of issues stemming from an IBM framework and an enterprise versioning system, both of which were overused and inconsistently supported, ultimately leading to severe usability issues and substantial stress for the users.

PTC Creo: A Design Hindrance

PTC Creo, while billed as a CAD system, is more accurately described as a CDH program (Computer Design Hindrance). The frustration with this software stems from its inability to perform even the most basic tasks that one would expect from a design tool. Here are some of the key issues that made working with PTC Creo a nightmare:

Design Tree Updates: PTC Creo frequently fails to update design trees without any prior warnings, making it challenging to track design changes and manage complexity. Inconsistent Cutting: The cutting function often fails to cut surfaces it's intended to, leading to inconsistencies and errors in the design process. Incorrect Mass Calculations: The software's mass calculation functions are unreliable, often producing inaccurate results which can be critical in design validation. Insufficient Macros: The ability to create custom macros to enhance workflow is reliant on purchasing additional programming packages, which can be prohibitive for many users.

Support for PTC Creo has been equally frustrating. In one particularly distressing incident, an employee was told by support that they were foolish for drawing a feature in a specific manner. After re-creating the feature according to the supposed "correct" method, it soon fell apart two days later, leading to further criticism from support. This experience led the employee to stress and ultimately breakdown, prompting them to avoid working with PTC Creo forever.

Enterprise-Level Blunders: IBM Framework and Versioning System

The second set of software nightmares revolves around an IBM framework and a custom IBM versioning system at a major bank. Despite initial potentials, these tools were used in ways that were beyond their intended scope and support, leading to various complications and frustrations.

IBM Framework BTT

BTT (Bank Transaction Tool) by IBM was designed specifically for managing bank transactions. However, the bank extended its use far beyond its intended purpose. The framework was initially meant to handle transactions in the back-end. Instead, it was used for communication between the front- and back-end as well as between different screens within the front-end. This misapplication created numerous issues:

Misuse for Non-Transaction Purposes: The framework, which was not designed for such expansive use cases, was overburdened with additional functionalities. This led to code that made no sense and was redundant. Expired Support: The version the bank was using became somewhat obsolete as the newer version solved numerous bugs. However, rather than refactoring to the newer version or using it for new modules, they continued to rely on the old, unsupported version. Security Issues: Over time, the misuse of the framework contributed to a lack of security and stability, which were critical for handling financial transactions.

The support for BTT was limited and dependent on the purchase of a newer, supported version. Despite the bank's efforts to maintain support, the lack of proper refactoring and the need to continue using an outdated version led to significant usability and security issues.

Custom Versioning System

The custom versioning system at this same bank was designed to be a stable and easy-to-use tool initially. However, it transformed into a complex and inefficient system due to numerous 'nice to have' but ultimately unimportant changes. This system became so problematic that the bank had to introduce a new role, the release manager, to handle the seemingly simple process of merging branches.

Complex Merging: The process of merging branches was so complicated that it required significant time and effort, often leading to mistakes and issues in the released code. Security Risks: The custom versioning system's complexity and frequent changes introduced numerous security risks, making it difficult to maintain a stable environment for the application. Release Manager Role: The introduction of the release manager role underscores the complexity and inefficiencies of the versioning system, as even someone trained to perform simple tasks found it challenging to execute without errors.

The frustration with the custom versioning system was palpable. Errors and issues were common during the release process, leading to additional stress and delays. The release manager found themselves constantly troubleshooting and debugging, with support times often exceeding a full day.

Conclusion

Working with software that exceeds its intended purposes can be incredibly frustrating and lead to severe usability issues. PTC Creo and the IBM framework and versioning system at the bank highlight the importance of understanding and adhering to the specific use cases of software tools. It is crucial to realize that software tools are not one-size-fits-all solutions and should be used within their intended scopes to avoid severe complications and unnecessary stress.