Those white clouds looked so sad and plain!
I’m writing this on a plane heading to the 2015 Grace Hopper Celebration of Women in Computing, and it seemed a fitting time to recap some of the amazing experiences I had at this year’s Dreamforce (#DF15).
It’s been a while since my last post, and I have to say that I’ve been in a bit of Dreamforce withdrawal for the past month and a bit. That and catching up with the work that actually pays the bills (love ya ETR!).
Lately I’ve covered some pretty dense topics (SOQL, For Loops, Apex Collections), so I wanted to lighten up our code batter.
Today, we’ll tackle something on the more airy side and also something super fun to work with (and really handy for all Awesome Admins to know). Welcome to code kitchen, where we’ll whip up a batch of conditional statements!
I completed the available Salesforce Trailhead modules last Friday with mixed feelings. I’m really pleased to have checked all the boxes and gained all the badges, but I’m more than a little sad that I’m done (for now).
I wanted to give back some love to the Salesforce Developer Relations group by writing a review. You can probably guess that I loved it, but I hope to say more on why, and better yet, get you to check it out for yourself. Plus some tips on how to best use the tool, and advice on what you might want to skip over if you’re short on time.
I’ve always been into puzzles and word games. I guess that’s one of the things that I like about the coding that I’ve done in the past. I have about 10 years (on and off…mostly off these days) experience with CFML and SQL, so code logic isnt’ new to me, even if Object Oriented Programming is. So when shortly after Dreamforce, Salesforce announced Trailhead I was thrilled! I just now finished my first trail and thought I’d write a wee post to tell you all about it.
You must be logged in to post a comment.