<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Marty Y. Chang on Medium]]></title>
        <description><![CDATA[Stories by Marty Y. Chang on Medium]]></description>
        <link>https://medium.com/@martyychang?source=rss-e4aa18052ae9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*eRjXaZgP_MtsgS6V.jpeg</url>
            <title>Stories by Marty Y. Chang on Medium</title>
            <link>https://medium.com/@martyychang?source=rss-e4aa18052ae9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:59:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@martyychang/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Sweet Scripts for SuiteScript 2.1 User Events]]></title>
            <link>https://medium.com/@martyychang/sweet-scripts-for-suitescript-2-1-user-events-360855547281?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/360855547281</guid>
            <category><![CDATA[suitescript]]></category>
            <category><![CDATA[netsuite]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Sun, 21 May 2023 19:23:51 GMT</pubDate>
            <atom:updated>2023-05-21T19:23:51.999Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Ballmer says, “Power to developers!”" src="https://cdn-images-1.medium.com/max/1024/1*Cgb5T09WMCUz0kLSbMTBXQ.jpeg" /></figure><p>NetSuite’s <a href="https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1510274245.html">sample script</a> shows a few dozen lines of code that gets the job done. But how do you then tackle the challenge of <a href="https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_164882052792.html">writing concise and scalable unit tests</a>? 🤔 There must be an easier way!</p><pre>/** <br> * How does this look instead?<br> *<br> * @NApiVersion 2.1<br> * @NScriptType UserEventScript<br> */<br>define([&#39;SuiteScripts/Modules/trigger&#39;, &#39;SuiteScripts/Modules/customer&#39;],<br>function(trigger, customer) {<br>    return trigger.getEntryPoints(customer);<br>});</pre><p>By moving the business logic into a custom customer module, we are now one step closer to compact and resilient unit tests <a href="https://github.com/oracle/netsuite-suitecloud-sdk/tree/master/packages/unit-testing">with Jest</a>. Let’s take a look at the special sauce in the module. 👨‍🍳</p><pre>/**<br> * Sample event handlers for Customer records.<br> * <br> * @NApiVersion 2.1<br> * @NModuleType public<br> */<br>define([&#39;SuiteScripts/Modules/hello&#39;, &#39;SuiteScripts/Modules/goodbye&#39;],<br>function(hello, goodbye) {<br>    const M = {};  // module to return<br>    <br>    /**<br>     * Business logic to execute in `beforeSubmit()` when<br>     * `context.type === context.UserEventType.CREATE`.<br>     */<br>    M.createBeforeSubmit = function(newRecord) {<br>        newRecord.comments = hello.greet() + &#39; And... &#39; + goodbye.salute();<br>    };<br>    <br>    /**<br>     * Business logic to execute in `beforeSubmit()` when<br>     * `context.type === context.UserEventType.EDIT`.<br>     */<br>    M.editBeforeSubmit = function(newRecord, oldRecord) {<br>        newRecord.comments = &#39;Edited. Yup.&#39;;<br>    }<br><br>    return M;<br>});</pre><p>This <strong>Customer</strong> user events module ☝️ has a specific convention for its functions: the user event&#39;s <a href="https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4407992070.html">context.type</a> concatenated with the capitalized name of the entry point. Below are a few examples.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4e423623835aef04bafc004981b250a3/href">https://medium.com/media/4e423623835aef04bafc004981b250a3/href</a></iframe><p>But wait… what happened to N/record?!</p><p>You may have noticed that instead of calling <a href="https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4273155868.html">newRecord.setValue({fieldId: &#39;comments&#39;, value: &#39;...&#39;})</a>, the sample handlers above ☝️ set the comments property directly, as if newRecord was a simple JavaScript object! 😮</p><p>This is implemented with little trick using <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy">Proxy</a> in the trigger module, 😉 where context.newRecord and context.oldRecord are wrapped inside proxies that look and feel like simple JavaScript objects. And <a href="https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_158755248128.html">SuiteScript 2.1</a>—<em>not</em> 2.0—makes this all possible! 🍾 Thank you, NetSuite. ❤️</p><p>And finally, the true gem 💎 of this structure is the ability to easily write unit tests for the business logic in the customer module.</p><pre>import customer from &#39;SuiteScripts/Modules/customer&#39;;<br><br>describe(&#39;Customer module&#39;, () =&gt; {<br>  it(&#39;handles beforeSubmit() on CREATE&#39;, () =&gt; {<br>    let newRecord = {};<br>    customer.createBeforeSubmit(newRecord);<br><br>    expect(newRecord.comments).toContain(&#39;Hello&#39;);<br>    expect(newRecord.comments).toContain(&#39;Goodbye&#39;);<br>  });<br>});</pre><p>Not a single N/record mock in sight. 🙌</p><p>What do you think? Let me know on <a href="https://twitter.com/martyychang">Twitter</a> or <a href="https://www.linkedin.com/in/martyychang">LinkedIn</a>. ✉️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=360855547281" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Succeed at Modern Slavery]]></title>
            <link>https://medium.com/@martyychang/how-to-succeed-at-modern-slavery-5bfa5cf50b44?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bfa5cf50b44</guid>
            <category><![CDATA[slavery]]></category>
            <category><![CDATA[real-estate]]></category>
            <category><![CDATA[justice]]></category>
            <category><![CDATA[economic-inequality]]></category>
            <category><![CDATA[blacklivesmatter]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Tue, 02 Jun 2020 15:37:53 GMT</pubDate>
            <atom:updated>2020-06-02T15:37:53.930Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*oI-eCYOL23kvqqjtb34fRg.jpeg" /></figure><p>In the old days slavery used to be easy. All you had to do was go to the slave auctions and put in a couple of bids, but alas those days are gone. Thanks for nothing, Lincoln.</p><p>But if you’re looking for a way to indefinitely profit from other people’s labor while barely having to lift a finger, I’m going to share a great little secret with you. <a href="https://www.state.gov/j/tip/what/">Forget sex trafficking and all the dangerous stuff</a> that will get you jailed or killed. What I’m about to share with you is perfectly legal and widely promoted in America!</p><p>While it won’t look the same as what those grand plantations once did, you can start building your modern “plantation” in a few easy steps. It’s a bit hard to start from scratch if generational wealth can’t bankroll you. But trust me, once you get going, expansion will become increasingly easier for you, your kids and your grandkids. Ready for the details? Easy as one-two-three.</p><ol><li>Buy residential property in an economically stable city like Boston.</li><li>Rent out the property at market rates.</li><li>Take the proceeds, and repeat from step 1.</li></ol><p>Once you have a couple of properties, you can kick back and let your renters put food on your table for you! If they can’t pay, kick them out. There are plenty of other suckers out there. And if they <em>can</em> pay, try upping the rent every year or two. You won’t ever get to 100% of a renter’s net income like in the good ol’ days, but if you catch a good one <a href="https://money.cnn.com/2016/06/22/real_estate/rent-affordability-housing-harvard/?iid=EL">you can squeeze out close to 50% of her pay</a>.</p><h4>Low risk</h4><p>Unlike starting a business where you’re going big or going bust, you can keep you boring day job while you work toward acquiring your first investment property.</p><p>You can even take out a second mortgage from a bank to start sooner. Sure, you have to pay back the loan, but in the end you’ll grow your plantation more much more quickly. Once you have your first investment property, and rent starts coming in, you’ll able to purchase a second investment property with a loan justified by the rent from the first property. Then getting the third will be even easier. Get the picture?</p><h4>Limitless potential</h4><p>There’s really no limit to how much property you can acquire this way, because it’s all legal and there are no anti-trust laws against personal property ownership. So why haven’t you started already? Get in the game now before prices go up!</p><h4>Don’t overthink it</h4><p>Every once in a while you’ll have to kick a renter out. People get laid off. Accidents happen. Whatever. In these cases you may feel some bothersome emotions come up, but know that <a href="https://www.theguardian.com/money/2013/sep/16/buy-to-let-landlord-still-ethical">there are ways to get over yourself</a> and keep going.</p><p>And if you’re worried that your renters are white not black like the first African slaves, who cares? Focus on the passive income headed your way. If they’re black, that’s just an added bonus.</p><h4>Final assessment</h4><p>While renting is not as profitable as slavery used to be, the life of a landlord can be as good or even better than a plantation owner. Sure, these renters won’t give you all of their harvest like slaves would have done back in the 1700s. Plus you have to deal with crap like complaints, threats of litigation (don’t worry, mostly just show), brokerage fees and taxes.</p><p>But on the upside…</p><ul><li>You don’t have to see your renters every day. In fact when you get good at what you do, you can collect rent without ever seeing your renters.</li><li>No one’s giving you dirty looks like you’re a slave owner. In fact, many people will celebrate your success and try to follow in your footsteps!</li><li>The net result of having passive income while hardly doing any work is the same!</li></ul><p>Overall you’re in the clear. No legal concerns, and best of all everyone’s already used to paying rent. Just keep the size of your distributed plantation on the DL, unless you’re working with another landlord to prop the prices up. The last thing you want is to draw attention to yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bfa5cf50b44" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Which integration touched my record?]]></title>
            <link>https://medium.com/@martyychang/which-integration-touched-my-record-413fda2bfeeb?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/413fda2bfeeb</guid>
            <category><![CDATA[ipaas]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[integration]]></category>
            <category><![CDATA[business-systems]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Fri, 06 Mar 2020 17:23:16 GMT</pubDate>
            <atom:updated>2020-03-06T17:23:16.571Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c-heoKE2AkPXIlAyhQ4dqg.jpeg" /></figure><p>When you procure a modern iPaaS solution like <a href="https://tray.io/">Tray.io</a> that can integrate your entire tech stack with Salesforce at the core, over time you may start to wonder which external workflow is responsible for touching a record in your CRM system at a given point in time. Creating a different Salesforce user for every integration workflow you’d ever build is infeasible. Luckily a free solution is as easy as creating a new field in Salesforce.</p><h3>Every modern workflow has a unique URL</h3><p>Every workflow you would ever build has a unique URL that contains some kind of workflow ID. The Tray Platform we use at <a href="https://www.drift.com/">Drift</a> is no exception, and the gaining visibility into which workflow touched which record is as simple as populating a custom field on the object with a link to the workflow.</p><p>Here’s an example from Drift’s Salesforce org. On the <strong>Contact</strong> object I have created a new <strong>Last Known Modified By Workflow URL</strong> field (LastKnownModifiedByWorkflowUrl__c).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0TTCrsgSSccpEjCIXxowYg.png" /><figcaption>Contact field: Last Known Modified By Workflow URL</figcaption></figure><p>Then, in Tray I mapped a static value to this field in the update operation. This value is simply the workflow’s URL copied from my browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CMyeFt7xuXWrqi4LLFiGxA.png" /><figcaption>Tray workflow URL hard-coded in Salesforce step</figcaption></figure><p>This is the basic setup, and if you apply this same convention to all of your workflows, you will see in you record’s history in Salesforce which workflow touched a record at a given point in time.</p><h3>Use a timestamp parameter to force history tracking</h3><p>Sometimes a single workflow may update the same record many times before another workflow gets to it. In these cases, you can force history tracking by appending a workflow execution timestamp to the URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T142tB2RCZRkNtkTiReVoA.png" /><figcaption>Timestamp appended as URL parameter to Tray workflow URL</figcaption></figure><p>Now every time the Tray workflow updates a contact, a field history entry is guaranteed as long as tracking is enabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pWAjMqGajouQ8tOCNFdlHQ.png" /><figcaption>Contact History showing entry for Last Known Modified By Workflow URL</figcaption></figure><p>That’s all there is to it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=413fda2bfeeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should You Declare Variables in Apex?]]></title>
            <link>https://medium.com/@martyychang/should-you-declare-variables-in-apex-4713795cb52b?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4713795cb52b</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[apex]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Mon, 23 Dec 2019 19:17:22 GMT</pubDate>
            <atom:updated>2019-12-23T19:17:22.052Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CPywwmm66W7GRpZ25DaBDw.png" /><figcaption>Salesforce debug log showing iteration in a for loop</figcaption></figure><p>Long-running operations may still be omitted from the log, if it’s being handled behind the scenes by the Lightning Platform. I figure empirical evidence would be the best way to prove whether variable assignments can be a performance drag.</p><h3>Hypothesis: Local Variables Slow Down Loops</h3><p>The hypothesis is that declaring local variables for convenience or readability within a loop slows loop execution, when compared with accessing items within a Map directly.</p><p>Consider the simple scenario below, where I want to assign the account owner as the contact owner for a given list of contacts.</p><pre>Map&lt;Id, Account&gt; accountMap = new Map&lt;Id, Account&gt;([<br>    SELECT Id, OwnerId<br>    FROM Account<br>    WHERE Id IN :accountIdSet<br>]);</pre><pre>for (Contact eachContact : contactList) {<br>    Account contactAccount = accountMap.get(eachContact.AccountId);<br>    eachContact.OwnerId = contactAccount.OwnerId;<br>}</pre><p>If the hypothesis is true, a faster loop implementation would eliminate the contactAccount variable.</p><pre>Map&lt;Id, Account&gt; accountMap = new Map&lt;Id, Account&gt;([<br>    SELECT Id, OwnerId<br>    FROM Account<br>    WHERE Id IN :accountIdSet<br>]);</pre><pre>for (Contact eachContact : contactList) {<br>    eachContact.OwnerId =<br>            accountMap.get(eachContact.AccountId).OwnerId;<br>}</pre><h3>Performance Lab Setup</h3><p>The performance lab contains a two-part setup.</p><ul><li>Salesforce project for actually executing each performance test and generating the raw data.</li><li>Python script for collecting performance test results from Salesforce.</li></ul><p>Fork the <a href="https://github.com/martyychang/salesforce-performance-lab">salesforce-performance-lab</a> repo on GitHub to write your own!</p><h3>Conclusion: Declare the variable!</h3><p>Below is a summary of the results from over 1,000 samples running each loop, with 100 accounts in the map being referenced and 200 contacts in iteration.</p><ul><li><strong>3.048 ms</strong> when declaring a local variable within the for loop.</li><li><em>3.097 ms</em> when accessing map items directly within the for loop.</li></ul><p>While these results in themselves seem counterintuitive and hard to believe, perhaps the more salient point from the data is that there is no practical advantage to be gained by omitting a local variable declaration within the for loop.</p><p>So, let’s go ahead and declare local variables as we please!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4713795cb52b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Log Inspector to Probe Apex Timeouts in Salesforce]]></title>
            <link>https://medium.com/@martyychang/log-inspector-to-probe-apex-timeouts-in-salesforce-4495ec451f24?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4495ec451f24</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[apex]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Fri, 13 Dec 2019 15:54:27 GMT</pubDate>
            <atom:updated>2019-12-13T15:54:27.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_owoFd_-lG0zdD3gaJu4A.png" /><figcaption>Salesforce Developer Console Execution Overview Timeline</figcaption></figure><p>Below are my two favorite errors in all of Salesforce.</p><ol><li>Apex CPU time limit exceeded</li><li>UNABLE_TO_LOCK_ROW: unable to obtain exclusive access to this record</li></ol><p>They’re my favorites because I’m seeing them everyday at the moment and spending lots of quality time getting to know them. Although I know these errors and I must break up soon — my first love is my wife — I thought to acknowledge this hopefully brief relationship by starting a live journal on this sweet winter fling.</p><h3>How we met</h3><p>When I added myself to the Apex exception email list in my new Salesforce org, I started receiving love notes via email with subject lines like the following.</p><blockquote>Developer script exception from Drift : AccountTrigger : AccountTrigger: System.LimitException: Apex CPU time limit exceeded</blockquote><p>Ah, Apex CPU time limit, how I’ve missed you…</p><blockquote>Developer script exception from Drift : AccountTrigger : AccountTrigger: execution of AfterUpdate caused by: System.DmlException: Update failed. First exception on row 0 with id 0034A00003I4bIJQAZ; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record or 1 records: 0034A00003I4bIJQAZ: [] ()</blockquote><p>And UNABLE_TO_LOCK_ROW is an old friend from the days when I first started dabbling in batch jobs and ETL integration jobs. So great to see you again!</p><p>AccountTrigger wasn’t to be our only communication channel. I also started meeting other components sending the same warm sentiments.</p><ul><li>ContactTrigger</li><li>TaskTrigger</li><li>CloudingoAgent.ContactUpdatePOSyncTrigger</li><li>Zendesk.TrgrZendeskUserFromContact</li><li>Zendesk.TrgrZendeskOrganization</li><li>cbit.cbt_Accounts</li><li>rh2.PS_Contact_Describe_Async</li><li>… and more!</li></ul><h3>Enter the Log Inspector</h3><p>The first delightful learning came <a href="https://salesforce.stackexchange.com/questions/287717/how-to-analyze-apex-cpu-consumption/287727#comment431799_287717">from Stack Exchange</a> about the <a href="https://help.salesforce.com/articleView?id=code_dev_console_view_system_log.htm&amp;type=5">Log Inspector</a> available within the Developer Console. The three things I’ve loved about this.</p><ul><li>Execution Overview &gt; <strong>Timeline</strong>: This diagram visually pops out the long-running pieces of the operation. You can see how much is under your control and get a sense for how much is happening within managed packages beyond your control.</li><li>Stack Tree &gt; <strong>Performance Tree</strong>: This groups various events that incur time costs and allows you to drill down incrementally to figure out what piece of automation you want to optimize.</li><li><strong>Execution Stack</strong>, <strong>Source</strong> and <strong>Variables</strong> work in conjunction with the Execution Log to show you the state of Salesforce at the point of an entry within the debug log. Clicking to different lines of the debug log will refresh those panels to give you the right contextual information.</li></ul><h3>Next steps</h3><p>The next step in this relationship is for me to try to benchmark performance and assess the impact of making incremental changes to reduce runtime.</p><p><em>The struggle is real. </em><a href="https://twitter.com/@martyychang"><em>Tweet me</em></a><em> or </em><a href="https://www.linkedin.com/in/martyychang"><em>send me a note on LinkedIn</em></a><em> if you have suggestions or advice on resolving these timeout errors, and you can expect a follow-up post in the coming week.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4495ec451f24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enable Two-way Sync with Salesforce]]></title>
            <link>https://medium.com/@martyychang/enable-two-way-sync-with-salesforce-71b53d7d4fd?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/71b53d7d4fd</guid>
            <category><![CDATA[workato]]></category>
            <category><![CDATA[integration]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[crm]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Mon, 22 Apr 2019 15:44:56 GMT</pubDate>
            <atom:updated>2019-04-22T15:44:56.091Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*995pa49Ezov6qzCv65Cp1g.jpeg" /></figure><p>Among CRM, ERP and other systems, two-way syncs enable an organization to smoothly roll out new functionality in one system while still making use of the best features from another system. One common example is that a company trying to move its entire CRM operations from a legacy system to a new one like Salesforce may choose to lead with Salesforce CPQ as an extension of the current CRM system, supported by a two-way sync of quotes and quote line items.</p><p>This kind of integration usually supports these scenarios.</p><ul><li><strong>Create</strong> — Record created in one system is also created in the other</li><li><strong>Edit</strong> — Record edited in one system is also edited in the other</li><li><strong>Delete</strong> — Record deleted in one system is also deleted in the other. This feature is usually the elephant in the room that creates agita for the team.</li></ul><p>To demystify the bidirectional sync and create confidence in a simple approach, read on for a hypothetical scenario and practical solution you can try for free on your own. Afterward you will gain a sense of what’s actually involved in building a two-way sync.</p><h3>Hypothetical scenario</h3><p>Shortly after Acme, Inc. acquired Pinnacle Corporation, Acme executives launched an initiative to integrate Pinnacle’s FinancialForce ERP instance into Acme’s existing Salesforce CRM instance. <a href="https://www.workato.com/pricing?audience=general&amp;type=self">Workato</a> is used as the iPaaS middleware, and so far the following objects have been synced smoothly.</p><ul><li>Accounts</li><li>Opportunities (without line items)</li><li>Products</li><li>Price books</li><li>Price book entries</li><li>Quotes (without line items)</li></ul><p>The project team is now ready to start syncing quote line items.</p><h4>Story: Sync quote line items on create and edit</h4><blockquote>Acceptance criteria: Given a quote in the Pinnacle org that is already synced to the Acme org, when a new quote line item is added to the quote in the Pinnacle org, then within 5 minutes the quote line item is synced to the Acme org under the correct quote.</blockquote><ol><li>In the Acme org, create a <strong>Pinnacle Quote Line Item ID</strong> 18-character text field to hold the ID of the corresponding record in the other org.</li><li>In the Pinnacle org, create an <strong>Acme Quote Line Item ID</strong> 18-character text field for the same purpose.</li><li>Next, create a workflow rule in the Pinnacle orgthat fires when a quote line item is created or edited. The workflow rules should have a filter to skip records edited by users having the <strong>Bypass Sync Automation</strong> custom permission, assumed to be assigned to the Workato Integration user.</li><li>Configure the workflow rule to send an outbound message to Workato, and put <strong>Quote Line Item ID</strong> and <strong>Acme Quote Line Item ID</strong> in the message along with any other fields to sync.</li><li>Configure Workato to accept the message. If <strong>Acme Quote Line Item ID</strong> is empty, Workato should create a new record in the Acme org. If the field is populated, Workato should update the existing record in the Acme org.</li><li>Configured Workato so that if a record is created in the Acme org, Workato also updates the source record in the Pinnacle org with the <strong>Acme Quote Line Item ID</strong>.</li></ol><p>Now quote line items created and edited in the Pinnacle org will also result in a corresponding create or edit operation in the Acme org!</p><h4>Story: Sync quote line items on delete</h4><blockquote>Acceptance criteria: Given a quote line item in the Pinnacle org that is already synced to the Acme org, when the quote line item is deleted, then within 5 minutes the quote line item is also deleted from the corresponding quote in the Acme org.</blockquote><ol><li>In the Pinnacle org, create a <strong>DML Operation Subject</strong> custom object with four fields described below.</li><li>Create a <strong>Subject ID</strong> 18-character text field on DML Operation Subject.</li><li>Create an <strong>Acme Subject ID</strong> 18-character text field.</li><li>Create an <strong>Object API Name</strong> 80-character text field.</li><li>Create a <strong>Type</strong> picklist field with “insert”, “update” and “delete” for values.</li><li>Create an Apex trigger on the <strong>QuoteLineItem</strong> object that creates a <strong>DML Operation Subject</strong> record for every line item that is deleted, with the appropriate fields mapped.</li><li>Create a workflow rule on the DML Operation Subject object to fire whenever a new record is created with with <strong>Object API Name</strong> “Quote” and <strong>Type</strong> “delete”.</li><li>Configure the workflow rule to send an outbound message to Workato.</li><li>Configure Workato to accept the message and delete the corresponding quote line item from the Acme org.</li></ol><p>Now quote line items deleted from the Pinnacle org will also be automatically deleted from the Acme org!</p><h3>More food for thought</h3><p>The <strong>Bypass Sync Automation</strong> custom permission briefly mentioned above can be used as part of a standard integration pattern that includes a <strong>Sync Status</strong> global value set to control what records are synced and how. (<a href="https://twitter.com/martyychang">Let us know</a> if you’re interested in a follow-up post on this topic!)</p><p>But even with just these two simple stories delivered, you’ve got a viable solution and blueprint for syncing line items from one system to another. What do you think?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*TC-eyR9aEcYqQ4idUgqNpA.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71b53d7d4fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lightning Ready in 6 Weeks]]></title>
            <link>https://medium.com/@martyychang/lightning-ready-in-6-weeks-5172b15d066a?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5172b15d066a</guid>
            <category><![CDATA[trailblazer]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[crm]]></category>
            <category><![CDATA[lightning]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Thu, 31 Jan 2019 19:39:38 GMT</pubDate>
            <atom:updated>2019-02-27T18:13:56.692Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Starting with the Winter ’20 release, Salesforce will turn on Lightning Experience for all orgs on a rolling basis. Start preparing today!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lOvkm7q48IEAJ9XC" /><figcaption>Promotion for the <a href="https://developer.salesforce.com/calendar">Lightning Now Tour</a></figcaption></figure><p>If you manage an Enterprise Edition or Unlimited Edition org, and if the automated push to Lightning Experience <a href="https://admin.salesforce.com/be-lightning-ready-by-the-winter-20-release">promised in Winter ’20</a> makes the hair on your arms tingle, there’s good news! At the time of writing this blog post, Winter ’20 is still over 6 months away, and you can be Lightning Ready in <em>just 6 weeks</em>.</p><p>Sound like a “beach body” commercial? Try this six-week plan to roll out Lightning Experience and decide for yourself.</p><h3>Week 1: Start the backlog</h3><p>How long is the global rollout going to take? The only way to find out is to do the analysis and estimate the work to be done in your <a href="https://www.scaledagileframework.com/team-backlog/">team’s backlog</a>, and a team of three including a product owner is usually enough to get the ball rolling. The path can be pretty straightforward.</p><ol><li>Fix obvious problems from the <a href="https://help.salesforce.com/articleView?id=lex_readiness_check.htm&amp;type=5">Lightning Experience Readiness Report</a></li><li>Schedule 2-hour discovery workshops for each of your <a href="https://en.wikipedia.org/wiki/Persona_(user_experience)">user personas</a></li><li>Invite one or two representative super users to each workshop</li></ol><p>The workshops can follow a simple agenda.</p><ul><li>Turn on Lightning Experience for your super users in production (or in a Full sandbox if production feels too uncomfortable)</li><li>Ask your super users to run through their daily routine</li><li>Ask your super users to try completing their most complex activities</li><li>Take notes on what works and what really needs attention!</li><li>Convert your notes into user stories</li></ul><h3>Week 2: Build confidence to handle elephants</h3><p>Chances are the workshops confirmed your worst fears: There are some elephants in the org. These elephants are the custom components or entire packages from the AppExchange that work poorly or not at all in Lightning Experience. No problem, just take a deep breath.</p><p>Then take stock of your elephants, and tackle them one at a time with <a href="https://www.scaledagileframework.com/spikes/">spikes</a> that create <a href="https://www.scaledagileframework.com/architectural-runway/">architectural runway</a> for your team.</p><blockquote>How do you eat an elephant? One bite at a time.</blockquote><p>In the meantime, if you have more personas to discover, repeat last week’s discovery workshops to continue building the backlog in parallel.</p><h3>Week 3: Start delivery for your early adopters</h3><p>With stories in the backlog and a smooth runway, it’s time to deliver! First, prioritize the stories for your early adopters. The ideal early adopter is someone who embraces change and whose day-to-day activities in Salesforce require the least effort to convert. Then, with the backlog prioritized, you can apply <a href="https://www.scrum.org/resources/what-is-scrum">scrum</a>, <a href="https://www.slalom.com/solutions/slalom-product-engineering-methodology">Product Engineering Methodology</a> or your favorite agile framework and rev up the delivery engine!</p><p>Once you’ve covered good ground with converting features from Salesforce Classic to work in Lightning Experience, make use of your sandboxes and show your work to a few super users. This will keep your users engaged while also giving you time to respond to feedback before the first pilot release.</p><h3>Week 4: Deliver to your early adopters</h3><p>Have you made a release yet? If not, now would be a good time to get the goodies into the hands of at least one pilot group in <strong>production</strong>. <a href="https://www.slalom.com/thinking/organizational-change-management-delivery-whitepaper">Change management</a> is critical to the success of your pilot. Keep in close touch with these early adopters, watch them do their work, give support, collect feedback and resolve any major issues that are uncovered.</p><p>Also, continue delivery for the next set of personas!</p><h3>Week 5: Incorporate real-world feedback</h3><p>With the pilot live, feedback should be making its way to the product owner and into the team backlog. While the product owner refines and prioritizes the new stories, continue delivering for the next set of personas!</p><h3>Week 6: Wait… are we done already?</h3><p>Five weeks into this repeatable process, your team is operating at a pretty steady pace and delivering stories left and right. Depending on the complexity of your org and the number of personas supported, you may already be done by now! And if you’re not totally done yet, you should now have a well groomed backlog that enables you to forecast when the rollout should be complete across the organization.</p><p>The rollout process for each persona is summarized below.</p><ol><li>Fix obvious, easy issues identified in the readiness report</li><li>Run a workshop and/or collect feedback for the persona</li><li>Write user stories and create architectural runway</li><li>Size and prioritize the stories in the backlog</li><li>Deliver the stories</li><li>Release the goodness to users in that persona (including communications, training, etc.)</li></ol><h3>There’s no time like the present</h3><p>Are you excited to start rolling out Lightning Experience? Are you still anxious? Check out the additional resources below, and <a href="https://www.slalom.com/work/partners/salesforce">let us know</a> what’s on your mind!</p><ul><li><a href="https://releasenotes.docs.salesforce.com/en-us/spring19/release-notes/rn_lex_transition_assistant.htm">Lightning Experience Transition Assistant</a></li><li>“<a href="https://trailhead.salesforce.com/content/learn/trails/lex_admin_migration">Make the Move to Lightning Experience</a>” on Trailhead</li><li>“<a href="https://help.salesforce.com/articleView?id=lex_rollout_strategy.htm&amp;type=5">Develop Your Lightning Experience Rollout Strategy</a>”</li><li><a href="https://success.salesforce.com/0F93A0000009SE1">* Lightning Now! *</a> group in the Trailblazer Community</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5172b15d066a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Salesforce Agility in 3 Steps]]></title>
            <link>https://medium.com/@martyychang/salesforce-agility-in-3-steps-331aa4381b76?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/331aa4381b76</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[crm]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Fri, 07 Dec 2018 20:20:18 GMT</pubDate>
            <atom:updated>2018-12-07T20:20:18.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1UW4-BuyERD2vnJBLDrB1w.png" /><figcaption><a href="https://www.merriam-webster.com/dictionary/agile">Merriam-Webster</a></figcaption></figure><p>Today, “agile” can feel like a gilded buzzword that gets more eye-rolls than smiles. You’ve heard the promise of faster time to ROI, you’ve read <a href="https://hbr.org/sponsored/2016/04/agile-practice-the-competitive-advantage-for-a-digital-age">articles by HBR</a> espousing the benefits, and yet the experience of you and your peers falls short of expectations.</p><p>Perhaps you are in <a href="https://hbr.org/sponsored/2018/03/survey-data-shows-that-many-companies-are-still-not-truly-agile">the group of hopeful adventurers</a> who have started on the journey toward agile for Salesforce. Or you may be considering an agile approach and need to know what’s <em>really</em> involved. To focus and accelerate your efforts, take this 3-step challenge and assess your results.</p><p><strong>WARNING!</strong> You may be surprised at how easy “agile” can be.</p><h3>1. Deploy to production regularly</h3><p>When did you last deploy to production? And when is your next deployment to production? If you are using <a href="https://www.scrum.org/resources/what-is-scrum">scrum</a>, your answer should simply be, “We deploy to production at the end of every sprint.” Period. Without exception.</p><ul><li>If you think deploying to production is risky, reevaluate your testing strategy.</li><li>If your team does not test consistently, reinforce testing as part of your team’s definition of done.</li><li>If your manual testing strategy doesn’t scale, automate your tests.</li></ul><p>You can deploy multiple times to production within a sprint, <a href="https://engineering.salesforce.com/deploying-in-the-six-figures-and-beyond-b3b1c7a6a869">even daily</a>, but at a minimum you <em>must</em> deploy once per sprint. Regular deployments to production are the foundation on which agility is realized.</p><p><em>Stay tuned for a future post on continuous integration with Salesforce DX!</em></p><h3>2. Separate deployments from releases</h3><p>Are you worried about deploying changes to production when users are not yet ready for the new functionality? Have no fear! <a href="https://www.scaledagileframework.com/release-on-demand/">Feature toggles</a> are the solution to this challenge, allowing you to deploy <em>without</em> releasing.</p><ul><li><strong>deploy</strong> (<em>transitive verb</em>): to move code and metadata</li><li><strong>release</strong> (<em>transitive verb</em>): to make features available for use</li></ul><p>As new features are beefed up and <em>deployed</em> to production, toggles allow a product owner representing a company’s business interests to decide when the right time is to <em>release </em>the feature to end users.</p><p>Salesforce ships with countless built-in toggles for features like <a href="https://help.salesforce.com/articleView?id=shared_contacts_overview.htm&amp;type=5">Contacts to Multiple Accounts</a> or <a href="https://help.salesforce.com/articleView?id=admin_enable_multicurrency.htm&amp;type=5">Multiple Currencies</a>. You can easily do the same, using something as simple as a custom permission or a custom setting!</p><h3>3. <strong>Close the loop with user feedback</strong></h3><p>What do you do with all those hidden goodies deployed to production and the feature toggles associated with them? Get user feedback early and often! Embrace A/B testing as a best practice, and use the toggles to intentionally launch controlled pilot programs and beta programs to gather feedback from the real world. This way, when the release goes live for <em>everyone </em>you have solid assurance that you have delivered a great product into the hands of your users.</p><p>Embrace your super users. Give them special early access passes. Then prove you are listening to them by channeling their feedback directly into your product backlog.</p><h3>What’s holding you back?</h3><p>The three steps to achieving Salesforce agility truly are straightforward.</p><ol><li>Deploy regularly to production</li><li>Separate deployments from releases</li><li>Get real-world feedback early and often</li></ol><p>Still, hesitation is common when these feel like new concepts. If you want more detailed answers to questions regarding your unique situation, get in touch via <a href="/service/mailto:connect@slalom.com">email</a> or <a href="https://twitter.com/slalomboston">Twitter</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=331aa4381b76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Admin vs. Developer — Who to Hire?]]></title>
            <link>https://medium.com/@martyychang/admin-vs-developer-who-to-hire-f319f0bec9c4?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f319f0bec9c4</guid>
            <category><![CDATA[crm]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Mon, 19 Nov 2018 21:38:15 GMT</pubDate>
            <atom:updated>2018-11-19T21:38:15.509Z</atom:updated>
            <content:encoded><![CDATA[<h3>Admin vs. Developer — Who to Hire?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a2cFEVU4AnvOmFqcvzE4kQ.jpeg" /><figcaption>Photo by <a href="http://startupstockphotos.com/post/123128014991/at-barrel-soho-nyc">Startup Stock Photos</a> from <a href="https://www.pexels.com/photo/7374/">Pexels</a></figcaption></figure><p>While implementing Salesforce at a large publicly traded company, a colleague questioned whether asking newly hired admins to learn Salesforce DX, Git and GitHub is too much. “Aren’t version control, scratch orgs and deployment concerns squarely in the developers’ court?” I started to wonder whether we had hired admins when we actually wanted developers, but then I thought… what exactly is the difference?</p><p>Historically “code” in the form of Apex had been a clear line in the Salesforce space between admin and developer. But then came <a href="https://developer.salesforce.com/page/Visual_Workflow">Visual Workflow</a>. Flows blurred that line by providing a point-and-click interface for implementing complex business logic, later enhanced with <a href="http://releasenotes.docs.salesforce.com/en-us/spring15/release-notes/rn_forcecom_process_visually_automate.htm">Process Builder</a> as an easier entry point. Flows are in many ways equal to Apex in capabilities, but are flows “code”? In other words, should an admin be expected to create and maintain flows? And if so, in which environment?</p><p>As more powerful declarative capabilities like flows come to the Salesforce platform, I think it’s worth clarifying the most fundamental difference between an admin and a developer.</p><h3>What’s in a name?</h3><p>Common language always helps in discussion, but unfortunately no English dictionary holds definitions for “admin” and “developer” specific to the IT domain. Still, Merriam-Webster does offer a starting point.</p><ul><li><a href="https://www.merriam-webster.com/dictionary/administer"><strong>administer</strong></a> (<em>transitive verb</em>): to manage or supervise the execution, use, or conduct of</li><li><a href="https://www.merriam-webster.com/dictionary/develop"><strong>develop</strong></a> (<em>transitive verb</em>): to create or produce especially by deliberate effort over time</li></ul><p>Transforming those verbs into nouns applied to Salesforce and other systems, I propose these working definitions for the two roles in question.</p><ul><li><strong>administrator</strong> (<em>noun</em>): one who maintains and supports the use of current features and functionality for end users</li><li><strong>developer</strong> (<em>noun</em>): one who builds and delivers new features and functionality for end users</li></ul><p>Administrators keep the ship afloat and block distractions for developers who are building the next most valuable feature. Both roles are absolutely necessary within an organization, and whether the two roles are assigned to employees 1-for-1 is far less important than recognizing the need for <em>both</em>.</p><h3>Focus on the individual vs. the team</h3><p>System administration is like an individual sport, where each incident can be logged, assigned and resolved independently by one admin in relative isolation. Admins compete with themselves and with each other to push the limits of the common “time to resolution” metric used to measure service delivery. Individual performance is the focus here.</p><p>But system development is without question a team sport, where teamwork and collaboration are fundamental requirements. The best developer alone can never outperform a team of well-trained peers. So while an admin can be expected to figure out how she can do her own job better and faster, a developer should be expected to figure out how her <em>team</em> can deliver better results faster. <em>Team</em> performance is the focus.</p><p>Since a developer plays on a team, the developer <em>must</em> learn the skills needed to play well with others. A developer learning to work with tools like Salesforce DX and Git is analogous to a soccer player learning to dribble and to pass the ball. These skills are crucial to the team’s success, and a developer should expect and embrace the periodic need to sacrifice personal convenience so as to increase overall effectiveness of the team.</p><h3>Who do you really need right now?</h3><p>Suggestions below.</p><ul><li>Need to crush some Tier 1 tickets? Hire more admins.</li><li>Need to deliver on a growing backlog of system enhancements? Hire more developers.</li></ul><p>To be very clear, organizations of all sizes need admins <em>and</em> developers. In fact, one employee commonly <em>does </em>play both roles on the job, especially at smaller companies. Expect to cross-train as needed.</p><p>Keep in mind that an employee may be predisposed as an admin or as a developer, just like how some athletes excel at individual sports and some at team sports. Using the functional definitions given here for an admin and a developer, you can now plan to build the right team at the right time.</p><p><em>This post first appeared at </em><a href="https://medium.com/@martyychang"><em>https://medium.com/@martyychang</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f319f0bec9c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The line between admin and developer]]></title>
            <link>https://medium.com/@martyychang/the-line-between-admin-and-developer-b1c1a1133588?source=rss-e4aa18052ae9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1c1a1133588</guid>
            <category><![CDATA[system-administration]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Marty Y. Chang]]></dc:creator>
            <pubDate>Sat, 25 Aug 2018 11:07:53 GMT</pubDate>
            <atom:updated>2018-09-18T03:17:05.488Z</atom:updated>
            <content:encoded><![CDATA[<p>While implementing Salesforce at a $2.4B publicly traded company, a colleague asked me whether asking newly hired admins to learn Salesforce DX, Git and GitHub is too much. “Isn’t version control, scratch orgs and deployment concerns squarely in the developers’ court?” I started to wonder whether we had hired admins when we actually wanted developers, but then… what exactly is the difference?</p><p>Historically “code” in the form of Apex had been a clear line in the Salesforce space between admin and developer. But then came <a href="https://developer.salesforce.com/page/Visual_Workflow">Visual Workflow</a>, which blurred that line of separation by providing a visual point-and-click interface for implementing complex business logic, later enhanced with <a href="http://releasenotes.docs.salesforce.com/en-us/spring15/release-notes/rn_forcecom_process_visually_automate.htm">Process Builder</a> as an easier entry point. This feature commonly called “flows” is in many ways equal to Apex in capabilities, but is it “code”? In other words, should an admin be expected to create and maintain flows? And if so, in which environment…?</p><p>As more declarative capabilities like flows come to the Salesforce platform, I think it’s worth clarifying what I believe is the most fundamental difference between an admin and a developer.</p><h3>First: What’s in a name?</h3><p>Common language always helps in discussion, but unfortunately no English dictionary holds definitions for “admin” and “developer” specific to the IT domain. Still, Merriam-Webster does offer a starting point.</p><ul><li><a href="https://www.merriam-webster.com/dictionary/administer"><strong>administer</strong></a> (<em>transitive verb</em>): to manage or supervise the execution, use, or conduct of</li><li><a href="https://www.merriam-webster.com/dictionary/develop"><strong>develop</strong></a> (<em>transitive verb</em>): to create or produce especially by deliberate effort over time</li></ul><p>Transforming those verbs into nouns applied to Salesforce and IT systems at large, I propose the functional definitions below for the two roles in question.</p><ul><li><strong>administrator</strong> (<em>noun</em>): one who maintains and supports the use of current features and functionality for end users</li><li><strong>developer</strong> (<em>noun</em>): one who builds and delivers new features and functionality for end users</li></ul><p>Administrators keep the ship afloat and block distractions for developers who are building the next most valuable feature. Both roles are absolutely necessary within an organization. But whether the two roles are assigned to employees 1-for-1 is far less important than recognizing the need for <em>both</em>.</p><h3>The difference: Focus on the individual vs. the team</h3><p>System administration is like an individual sport, where each incident can be logged, assigned and resolved independently by one admin in relative isolation. Admins compete with themselves and each other to push the limits of the common “time to resolution” metric used to measure service delivery. Individual performance is the focus.</p><p>But system development is without question a team sport, where teamwork and coordination are fundamental requirements. The best developer alone can never outperform a team of well trained peers. So while an admin can be expected to figure out how she can do her own job better and faster, a developer should be expected to figure out how the <em>team</em> can deliver better results faster. <em>Team</em> performance is the focus.</p><p>Since a developer plays as part of a team, the developer <em>must</em> learn the skills needed to play well with others. A developer learning to work with tools like Salesforce DX and Git is analogous to a soccer player learning to pass the ball. These skills are non-negotiable, and a developer should expect and embrace the periodic need to sacrifice personal convenience in the interest of increasing total effectiveness of the team.</p><h3>So, who do you really need right now?</h3><p>To be very clear, organizations of all sizes need admins <em>and</em> developers. In fact, one employee commonly <em>does </em>play both roles on the job, especially at smaller companies.</p><p>But just like how some athletes prefer individual sports over team sports, an employee may be predisposed to excel more as an admin or as a developer. Using the functional definitions given here for an admin and a developer, I hope we will all reap the benefits of hiring the right people into the right roles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1c1a1133588" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>