So your client refuses to pay: why you need to start building backdoors to your applications.
Disclaimer: I am not a lawyer, and this is not legal advice.
A few days ago, I wrote an article where I emphasize the importance of getting everything in writing. In it, I share my experience with a scummy real estate agent who tried to get out of paying me by continuously moving the goal posts on a project, which was agreed upon verbally.
Unfortunately for him, I was able to brick his application remotely.
I’ve been writing code since 2010, and there have only been a handful of clients that have flat-out refused to pay me after a job’s been completed. In my experience, the majority of billing issues I’ve encountered have mostly been either technical-related (“Who’s Zelle?”) or needing to pay in installments. Let me be clear: I’m not talking about those clients. Rather, I’m referring to clients that simply refuse to pay an agreed-upon amount and continue to use your application.
So let’s talk about defensive programming.
The term “defensive programming” traditionally refers to software architecture intended to defend…
