{{ !articles[0].partner.isSponsoringArticle ? "Platinum" : "Portal" }} Partner
java,agile,tips and tricks,industry

Everybody Fails Sometimes.

Everybody makes mistakes, otherwise we would all write bug free code. For most of us a mistake can be fixed and doesn’t have too serious consequences.

When I first released the Pico Plugin Framework, to make sure that the framework doesn’t clash with itself I enclosed the class definition in an if statement with class_exists. Now that was fine, but I hadn’t counted on the fact that if there was more than one version of the framework installed then the possibly the wrong version of the class would be loaded and used which would lead to odd behavior. Such as putting in a debug statement and then having a scratchy head moment when the debugging statement is not called.

Rather than beating myself up too much about it I got back down to developer land, did some Googling and thinking and implemented a factory pattern. The it was all good and the world could go back to sleep knowing I had fixed the problem.

So what did I take away from all this? Just a reminder of one of my personal values. Everybody fails sometimes. What matters is how you recover, and deal with the failure.

Have you failed at something? But through perseverance overcome the problem and gone on to success? If so I would love to hear about it so why not leave a comment.

Published at DZone with permission of {{ articles[0].authors[0].realName }}, DZone MVB. (source)

Opinions expressed by DZone contributors are their own.

{{ tag }}, {{tag}},

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}
{{ parent.authors[0].realName || parent.author}}

{{ parent.authors[0].tagline || parent.tagline }}

{{ parent.views }} ViewsClicks