These are the famous last words of a developer who is hoping that what exists will solve your problem. They might not fully understand your problem – where the should comes in – but they have some pretty solid confidence in their code in which it will work.
It’s hard to go through your career as a developer and never utter this statement – I have done it myself many times at the end of a late night deploy – it was probably more hope than belief at that point. At that point, you’ve been up late, probably trying to finish that last feature that you’ve been burning the candle at both ends and semi-colons are starting to look like colons and any coding guidelines you had, have since gone out the door.
Looking back, I would have liked for someone to poke holes in what I was saying at that point in time;
- Why should it work and not will work?
- Are you okay with it not working or is this the last try?
- What are you not confident about?
- What is the impact to “it not” working?
I could have probably saved myself some late night bug fixing had these questions been put forth to me to challenge my assumptions on my own code.