One of the hardest things to learn as a developer is that the hard part of the job isn't writing the code. The hard part is learning to manage the code through its life stages and make it operate at scale in production without incident.
If you think your job is done when the code is merged, you're fooling yourself and harming your customers.
this is why I'm not a developer...I write a thing, use it, and abandon it... 😞
@opie There are one-use coding situations but they are exceedingly rare.
* Red Team protesting
* One time ETL
And even in the ETL case, you have to test and run it in production to verify...
P.S. There was a time in ye olden days when code didn't run 24x7 and you could run the program and be done. Those days are long past, much like discrete transistors.