Watch this video, it is an important example of the responsibility we have as software developers.
Politics aside, think about the users' experience, how do you think they feel?
- A person sees all of these "cryptic" error messages.
- The system is difficult to use.
- The system constantly kicks you out.
- There is a helpline, that no-one is going to use.
- There is a lack of trust in the system, what happens when the page changes?
- A person tried the system 4 times throughout 40 days.
Due to the horrible user experience this fueled a sentiment of a lack of trust toward the Floridian Government.
This lack of trust will cost millions to them and the local economy.
Some of us will be in a position where our code will have real life-changing consequences to the public. Our code could make somebody homeless, our code could kill somebody.
Let that sink it.
Everyone relies on software to do everything for them, as we enter a world of greater automation the responsibility is going to lie on our shoulders.
The right to accessibility, the right to ease of use, and any future rights of software consumers is our collective responsibility.
There are other examples of software errors and although some are unavoidable most of the time it is the lack of foresight and testing.
Next time a client expects a quick return on their investment, remember that recklessness could destroy their company and your work could hurt somebody.
I admit that early in my career I've personally been pressured, sometimes this was self-inflicted, to deliver quickly, and to cut corners. I regret those decisions but being young, ego-driven, learning as I go I was trying to impress.
We all learn and grow.
This is why you should test, this an article I wrote which focuses on bang for the buck testing method I default to.
Reach out to me.