One of my goals for 2020 was to stick to an intermittent fasting routine. I completed 6600 hours of fasting in 2020. On average, that’s 18 hours of fasting every day, for 365 days. Other interesting stats include the longest streak of 440 fasts and the longest fast of 37 hours. I did reasonably well to maintain a healthy weight despite stress-induced binge eating during the pandemic.

My fasting journey started in mid of 2019. In the second half of July 2019, I was experiencing sharp pain in my left arm and shoulder. During that week in the middle of the night, I woke up all sweaty, with shortness of breath. I anxiously started googling for the nearest urgent care location, and the shortest path to reach there, just in case I need to rush. Fortunately in the next few minutes, I regained control of my breath. I drank a glass of water and decided to wait until morning. I visited my primary care physician the next day to find out what’s going on, and potentially plan for my angioplasty or bypass surgery (or whatever they do to fix the heart-related problem).

I like my doctor. He is not aggressive with any medications or prescriptions. His advice usually contains words like an embrace, adapt, or wait. After performing preliminary checks he confirmed that while the incident was indeed frightening, and showed all the symptoms of cardiac arrest, it was not a heart attack! The subsequent lipid profile tests etc confirmed his diagnosis.

While the diagnosis was good, when I carefully looked at the lab results, my LDL cholesterol was at the upper threshold of the safe range. My BMI was indicating that I was overweight. The pain in my left arm wasn’t completely gone. What if my doctor was wrong? This was a clue that I needed to make changes in my lifestyle. Fortunately, two things happened.

1. I read an interesting article about magician Penn Gillette losing 100 pounds by fasting for 3 months. He essentially followed One Meal A Day approach to maintain the weight loss.
2. I met a friend who had lost about 20 pounds in 3 months by following the intermittent fasting practice. It was super impressive.

I started taking deep dive into some internet research to understand the basics of intermittent fasting. While it looks like a modern fad, it has been practiced for centuries by various cultures and religions. For example, Hindu Lunar calendar has a 2-week schedule based on the full moon and new moon. On the 11th day after the full moon and new moon, one fasts from sunrise to sunset. That’s twice a month. It’s called Ekadashi fast.

The physiology of fasting is fascinating. Once you have the food, the digestion kicks in, and food breaks into glucose, amino acids, and fatty acids. Ghrelin or the ‘hunger hormone’ decreases and insulin increases. Insulin carries the nutrients into cells to be stored as glycogen, fat, etc., or used as energy. This phase - anabolic - lasts for 4 hours.

After the anabolic phase, the catabolic phase kicks in. For the next 12 hours, your blood glucose continues to drop and the liver starts breaking down glycogen for energy.

The catabolic phase transitions to the fat-burning phase. That’s 16 hours after you ate. As the name indicates, during the fat burning phase fat stores break down for energy. The fat burning phase lasts for 8 hours and transitions into the ketosis (and the deep ketosis phase).

I will not go into a lot of technical details here. That’s the basic overview of the physiology of fasting.

Coming back to the point. In August 2019, I started my fasting journey with a 16/8 schedule which meant 16-hour fasting and an 8-hour eating window. Just within a week or so I got used to it. I found it too easy, then I transitioned to the 18/6 schedule. And eventually settled on the 20/4 schedule for most of 2019. I use Zero Fasting to keep me motivated. I got the results I hoped for and did not experience any pain in my left arm or shoulder since then.

Note: To put in Penn Gillette’s words. If you take health and nutrition advice from a random internet stranger. You are an idiot.

This question comes up occasionally in my conversations with customers. Often there is a need to programmatically upload an attachment (a pdf or an image) file to Salesforce using MuleSoft. If the integration developer is not very familiar with the Salesforce Platform, it usually confusing due to the way Salesforce manages the attachments.

As shown in the following ER diagram, there are multiple entities involved in storing and managing the attachments in Salesforce

• Salesforce attachments are stored in ContentDocument (and ContentVersion) objects.
  • The ContentDocument object is used to retrieve, query, update and delete the latest version of a document.
  • The ContentVersion object is used to create, query, retrieve, search, edit, and update a specific version of a Salesforce CRM Content document.
• The attachment is stored in ContentDocument (Or ContentVersion) and linked to any sObject (Contact, Account etc) via ContentDocumentLink Object
• Thus, to successfully upload an attachment to Salesforce following needs to happen
  • Upsert an attachment (file) to ContentDocument/ContentVersion object
  • Query the ContentDocument/ContentVersion to get the ContentDocumentId
  • Use the ContentDocumentId to link to your sObject (Account, Lead Opportunity, etc) by upserting the relationship in the ContentDocumentLink object

Following flow chart shows the general approach to upload an attachment to Salesforce:

Mule DSL code to achieve this

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73

    <sub-flow name="Upload Attachment">
        <ee:transform 
            doc:name="Prepare ContentDocument">
            <ee:message>
            <ee:set-payload>
            <![CDATA[%dw 2.0
                output application/java
                ---
                [
                    {
                        Title: "filename" //Replace this with actual filename,
                        PathOnClient: "filename" //Replace this with the path on storage system
                        VersionData: payload.content as Binary {class: "byte[]"}
                        //This is the attachment content
                    }
                ]
                ]]>
            </ee:set-payload>
            </ee:message>
        </ee:transform>
        <salesforce:create type="ContentVersion"
            doc:name="Create ContentDocument"
            config-ref="Salesforce_Config"/>
        <ee:transform doc:name="Get Attachment Id">
            <ee:variables>
                <ee:set-variable variableName="contentVersionId">
                    <![CDATA[%dw 2.0
                    output application/java
                    ---
                    payload[0].id
                    ]]>
                </ee:set-variable>
            </ee:variables>
        </ee:transform>
        <salesforce:query 
            doc:name="Get ContentDocumentId"
            config-ref="Salesforce_Config">
            <salesforce:salesforce-query>
                SELECT ContentDocumentId From ContentVersion Where Id = ':contentVersionId'
            </salesforce:salesforce-query>
            <salesforce:parameters>
            <![CDATA[#[
                output application/java
                ---
                {
                    "contentVersionId" : vars.contentVersionId
                }
            ]
            ]]>
            </salesforce:parameters>
        </salesforce:query>
        <ee:transform doc:name="Prepare ContentDocumentLink">
            <ee:message>
                <ee:set-payload>
                    <![CDATA[%dw 2.0
                    output application/java
                    ---
                    [
                        {
                            LinkedEntityId: vars.accountId,
                            ContentDocumentId: payload[0].ContentDocumentId,
                            ShareType: "I"
                        }
                    ]
                    ]]>
                </ee:set-payload>
            </ee:message>
        </ee:transform>
        <salesforce:create 
            doc:name="Create ContentDocumentLink"
            config-ref="Salesforce_Config"
            type="ContentDocumentLink" />
    </sub-flow>

With this approach you can easily upload attachments to Salesforce.

I recently read “Made to Stick” by Chip Heath and Dan Heath. It was a fun and quick read. While I liked their framework of SUCCESs (Simple, Unexpected, Concrete, Credible, Emotional, Stories) to get the idea to stick, I thoroughly enjoyed the explanation of the Curse of Knowledge. The curse of knowledge occurs when a knowledgeable individual/expert assumes that the others have the background to understand a specific concept.

According to Chip and Dan, In general, getting your message across has two stages - the Answer Stage, and the Telling Others Stage. In the Answer Stage, you use your expertise to arrive at the idea that you want to share. This involves studying the material and becoming capable of answering. However, the same factors that worked to your advantage in the Answer Stage will backfire on you during the Telling Others stage. To get the answer, you need expertise, but you can’t dissociate expertise from the Curse of Knowledge. You know things that others don’t know, and you can’t remember what it was like not to know those things. So when you start sharing the answer, you’ll tend to communicate as if your audience were you.

This reminds me of another news I read a long time ago about an audio illusion. Once our brains know what to expect to hear, they do, even if, in reality, it is impossible.