Friday afternoon, around 2:00 I got a message telling me to check out SFDC99.com. At first, I was skeptical, here is yet another blog that is going to teach me Apex / java/ html etc…I had read it all before and have failed just about every time. Part of it was how the knowledge was presented, part of it was me saying “It is 20XX, why am I still having to write lines of code” and part of it was that I can do a BUNCH of cool stuff already with the goodies in Salesforce, what will learning Apex do for me.
This blog was different though, the tutorials were written in a conversational and logical manner that made sense and also didn’t come across as a developer talking to a kindergarten class.It also dawned on me…I was doing this stuff already. Sure, it might be through flows or crazy clever formulas and workflows, but the logic was there. My bias was pretty much erased completely once I saw this question:
1. If you can solve a business need using either a workflow or a trigger, which should you use?Always use a point-and-click solution (workflow) when possible!
- It’s easier for your team to create and maintain workflows
- Workflows are easier to find when debugging unexpected behavior in your org
- Workflows never break!
- You don’t have to write test classes
The reason this question really hit me was because I have ran into MANY developers that are code first, ask questions (and write documentation, test, get feedback on, deploy correctly) later.
Having seen and supported the aftermath of this type of developement, I really took a to the whole #ClicksNotCode and #ButtonClickAdmin philosophy to heart. Seeing a developer actually answer this question like I would was like a golden ticket.
It told me I could still believe in all the good stuff that makes a system like Salesforce.com great WHILE learning the dark side.
So, it has been approximately 48 hours since I started doing this thing, and here is what I have learned:
1) Just because you know code doesn’t mean you know salesforce.
2) APEX is way more intuitive than whatever code you might have tried to stumble through last time.
3) I am really thankful for my time supporting traditional CRM systems (Cough, Siebel, Cough) and having to muddle through gnarly SQL statements.
4) Having to have 75% code coverage is tough, but if you think about what you are trying to do with your trigger and then build out from there, you will do good.
5) Try and think how you would write a trigger to handle every transactions like getting coffee.
Next steps? Well, I just got my Head First Java book and have been working through that. Honestly, so far installing the JAVA SDK seems to be the hardest part (and I have installed Linux!), but that really isn’t a surprise since it is an Oracle Product.
I am also going to keep plugging away on the SFDC99.com tutorials. I have went through Chapter4 and am going to spend some time here getting a better grip on the basics before I move along. I am also going to keep “doing what I do” in terms of new functionality in SFDC. I love all the fun stuff like flows and workflows, but much like a padawan with a new lightsaber, I am going to try and use it as much as I can.