How do you know you are ready to present your software? When it works. :)
Do you attempt to find any showstoppers or critical issues before a release goes out? Yes, always. Take the requirements documentation / minimal functionality docs and ensure the functionality behaves as expected.
Is shipping a fearful thing or is it second nature all day every day? If you want to be and stay completive, you should be able to deploy every second of every day with minimal fear.
How do you find things you might have missed? Automated Testing, feedback, end user interaction.
To catch errors in software before being deployed is an entire industry unto itself. I would start with automated testing. Unit, Functional, Integration, etc. Test,test,test,test,test,test.
Next, automate the deployment process. Deploy to multiple non-production environments. Create an 'alpha' group from the client/s to sign off on the release before being deployed to production. This gets the clients buy in (and thus shared responsibility) on the release.
I could, and sometimes do, go into this topic in depth. Feel free to reach out to me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How do you know you are ready to present your software? When it works. :)
Do you attempt to find any showstoppers or critical issues before a release goes out? Yes, always. Take the requirements documentation / minimal functionality docs and ensure the functionality behaves as expected.
Is shipping a fearful thing or is it second nature all day every day? If you want to be and stay completive, you should be able to deploy every second of every day with minimal fear.
How do you find things you might have missed? Automated Testing, feedback, end user interaction.
To catch errors in software before being deployed is an entire industry unto itself. I would start with automated testing. Unit, Functional, Integration, etc. Test,test,test,test,test,test.
Next, automate the deployment process. Deploy to multiple non-production environments. Create an 'alpha' group from the client/s to sign off on the release before being deployed to production. This gets the clients buy in (and thus shared responsibility) on the release.
I could, and sometimes do, go into this topic in depth. Feel free to reach out to me.