Early Summer 2024

Training, Sharing & Declarative Statements

“Almost nothing important that ever happens to you happens because you engineer it.” - David Foster Wallace

Over lunch the other day I got to talking with someone I consider quite successful about what I want next in my career. Stating what I want has always been tough for me. I didn’t have Laurence Fishburne telling me that the rules of leadership include never being afraid to ask for something. So I looked this person I respect a lot in the eye and Declared what I wanted. More on that soon.

This year marks my 10th anniversary of launching CRM Analytics (aka Wave/Einstein/Tableau) at Dreamforce. To commemorate this I started to refresh my engineering skills and renew credentials. I shared this with a friend who overlapped with me at Salesforce and his perspective helped me realize something. The way I used to build solutions relied on Imperative engineering.

Using the work lunch above as an analogy: For a particular set of job opportunities, if an opportunity improves my career, and does not worsen things with family, then go for it, or else, etc., etc. That’s Imperative engineering. Here’s what that looks like using a Declarative statement: I want to advance my career while being a great parent. Don’t focus on controlling the step-by-step How. Start with What is the problem and What is the outcome you want. The hard part about the paradigm shift from Imperative engineering to Declarative statements isn’t the technology. It’s being clear about What you want.

Subscribe to Beta app to read the rest.