Mistakes I've Made: A Biography

Ever feel like a total fuck up? I have. Almost every day in fact.

More recently, here are some profoundly stupid mistakes I’ve made in my short Salesforce Development career to date:

  1. I spent 7 full business days trying to figure out how to get images to upload to the Salesforce database from a Lightning Component. I rewrote it several dozen times in different ways. When it finally seemed to sort of work, we decided to upload to AWS instead. Easier and more cost effective in the long run. D’oh!
  2. I spent nearly 2 days trying to figure out to use a component a colleague had made rather than ask for help, because I was embarassed to admit I was stuck. D’oh!
  3. I wrote a super slick component and Apex class to query the Google Places API to auto fill an address form, only to see Salesforce announce they were releasing the same thing soon. Also I might have been able to get around the need to pipe the API through an Apex class if I’d RTFM’d.
  4. I’ve programmatically written half a dozen bits of functionality that were already available as drag and drop components. Oops.
  5. I’ve publicly reached out to other developers on Twitter and Stackexchange asking for help, outing my total n00b status.
  6. I’ve written SOQL queries within for loops within SOQL queries within for loops within… you get the picture. Holy governor limits, Batman.
  7. I’ve created massive methods of spaghetti code that I could no longer follow within just hours of creating it. Refactoring is fun, kids.

What’s my point in sharing these faux-pas? Simply this: development is messy. It’s never as good as we’d like it to be. We do embarrassing stuff all the time. There’s no such thing as genius programmers. Some of us are just better at hiding our mistakes than others.

Written on August 9, 2017