So are you saying lets be less ambitious with the software we created and instead make it work perfectly? I.e.less is more... so we need to educate Product?
No that is not what I am saying at all! I am perceiving that this comment chain might end up going into a logic trap or they call it "leading the witness" in the courtroom.
So are you saying lets be less ambitious with the software we created and instead make it work perfectly? I.e.less is more... so we need to educate Product?
No that is not what I am saying at all! I am perceiving that this comment chain might end up going into a logic trap or they call it "leading the witness" in the courtroom.
not my intention at all, just trying to figure how to apply "resistant to introducing code" in day to day? How do you do it?
Have you had a look at defensive programming as a methodology? Check that out then you might get a better understanding of where I am coming from :)
Oh yeah absolutely, another thing I forgot to add to the ever-growing list of how to create good software :)
Defensive programming is a core methodology for me.