What you must make programmer do - At least once!
Every programmer hates it, no one will raise their hand to do, and everyone says: I didn't think that was my job?!
Do you have a hot-shot programmer, or a team who thinks their coding doesn't smell? 😤
Owners, Dev Managers, or Senior Dev with a 'smart junior' - The one thing you can do to reign everyone in... have them:
"Write end-user documentation for your application"
I can guarantee no one will make it out the door without finding a few errors in the code, especially if you're the coder! You can look at the code tens-to-hundreds of times and not spot the error. Even run it through a checker - "All looks good here boss!"
You won't find anything until you try explaining how something functions, in great detail, that will cause you to lean back in your chair and say "Huh, that's not what it should be doing.", or finally realize the steps are just too confusing and it should be simpler.
It's a great way to humble yourself and the team! It helps you locate errors before the users do, allowing you to get in front of it, maybe even delay sending code into production?! (I know... delaying is almost sacrilege!!)
I suggest anyone who has a hand in programming, customer service, quality assurance, or any part of the life cycle - try to write documentation with the mindset that a user has never seen your application and they need to start at page ZERO!
Needless-to-say, we will be writing some updates ASAP and going through the documentation process again because of the changes.
It might be painful. No one want's to do it. But trust me, it will benefit everyone on the team to WRITE exactly how something works, with all the buttons & sliders, and what should be the end results.
It's eye-opening!