Tenrox? Un-handled errors in application software - a UX and Quality challenge

-

Tenrox in a former incarnation was a rather primitive website with a decidedly built-by-desktop-coders feel. It did work, but was difficult to use, and so like many a functionally correct product, did not gain the enthusiasm of its users that any product supplier would desire. The title of the software - Tenrox - made this situation additionally uncomfortable for its long suffering users...

Unfortunately, the user issues were not confined to usability: there were also occasions of unexpected errors:

Although this dialog is ugly, in case of un-handled errors it can actually be catastrophic failure may be the best thing to do. This is to avoid data loss, data leakage, unauthorized access and other unexpected behavior.

Today, Tenrox.com is marketed "a cloud based project management software that helps you plan and schedule your projects track time and expenses" - already sounds better!

Comments

Post a Comment

Popular posts from this blog

Perl: panic! or stay with Perl, and re-engineer? - No Programming language is perfect - Strongly Type Languages might NOT have less bugs

-
Image
GEP Launcher is/was some old x86 program, which was in an unfortunate manner, revealed to be written in Perl. Perl is a much maligned language, something like JavaScript, without the good parts. There is no compiler which in itself has the advantage to shorter iteration times during development, but then all checks and validations are performed only when the program is actually running. Originating in a lax kind of West Coast environment, Perl kind of "sits by the poolside" and lets you do what you want, no matter the consequences. A running joke is that almost anything can be interpreted by Perl: so, something like Regular Expressions, the code can be easy to write, but hard to read. And it's generally agreed that developers spend far more time reading than writing code.  Unfortunately for fans of particular programming languages, it is difficult to objectively measure the prevalence of bugs with a particular language. Reports abound of how buggy C++ projects tend to be,...
Read more

Yahoo: still learning ReactJS ... - Deploying a dev build to a live website

-
Image
For frontend web developers, there is a handy Chrome plugin, to inspect the state of the ReactJS website. However, a disadvantage is of course that just about any other ReactJS dev can also inspect your public website. If you happen to have deployed using a *dev* (internal, not really optimized for production) build, then this can be detected by your users. Unfortunately Yahoo Mail! had this issue for a while (but it seems OK now)... Word to the wise: sanity check your production software now and then!
Read more

travis-ty - Time formats are difficult and require OS and application/website regular maintenance (Y2K, 2038, short term decisions and long term issues)

-
Image
travis is a great service that provides CI (Continuous Integration) build platform suitable for github based projects. For Open-Source projects, there is a free tier.  - but there was a wee booboo if the end-time of a build is not yet set: This could be case of defaulting to the start of Unix time or 'epoch'. Unix time is measured from the beginning of the year 1970, measured in seconds. An alternative implementation would be to use a null to indicate unknown time - however even the inventor of null considers it to be a mistake. This being a website, the client side code must be JavaScript, in which there is another option undefined, although normally that is used to indicate a bug for example if attempting to access part of the program that does not exist. (for example, a typo attempting to use a function that does not exist). This is possible, because JavaScript is a dynamically 'duck typed' language, where objects and data are accessed by convention rather than by c...
Read more