I have always treated my professional work with software as very serious business.
We aren't developing anything with direct life-safety consequences, but we are dealing with PII and other people's money. I see no reason to relax due diligence on anywhere along this spectrum. It's either correct or its not, and the consequences for getting something wrong are universally bad for all involved.
Now, I also strongly believe in the idea that software development is inherently an art form. The nuance is that within this art form, there are still very rigid conceptual frameworks you need to work with. For instance, designing the UI for any application is more-or-less a pure art form. Developing the SQL schema backing that UI is arguably something that is 100% deterministic and can have mathematical proofs established which prove its correctness one way or another.
The key to the success of any software project is blending these two worlds together in a sustainable and responsible way.
We aren't developing anything with direct life-safety consequences, but we are dealing with PII and other people's money. I see no reason to relax due diligence on anywhere along this spectrum. It's either correct or its not, and the consequences for getting something wrong are universally bad for all involved.
Now, I also strongly believe in the idea that software development is inherently an art form. The nuance is that within this art form, there are still very rigid conceptual frameworks you need to work with. For instance, designing the UI for any application is more-or-less a pure art form. Developing the SQL schema backing that UI is arguably something that is 100% deterministic and can have mathematical proofs established which prove its correctness one way or another.
The key to the success of any software project is blending these two worlds together in a sustainable and responsible way.