<?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 Lloyd Carroll on Medium]]></title>
        <description><![CDATA[Stories by Lloyd Carroll on Medium]]></description>
        <link>https://medium.com/@lloydcarroll?source=rss-2dbc3eb8d7f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jl_akceetdW1oByF8El54A@2x.jpeg</url>
            <title>Stories by Lloyd Carroll on Medium</title>
            <link>https://medium.com/@lloydcarroll?source=rss-2dbc3eb8d7f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:16:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lloydcarroll/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[Getting Started as a Software Developer]]></title>
            <link>https://blog.devgenius.io/getting-started-as-a-software-developer-35c8815f5168?source=rss-2dbc3eb8d7f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/35c8815f5168</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[employment]]></category>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Lloyd Carroll]]></dc:creator>
            <pubDate>Thu, 02 Jul 2020 00:53:17 GMT</pubDate>
            <atom:updated>2025-10-24T00:40:44.621Z</atom:updated>
            <content:encoded><![CDATA[<h3>Getting started as a Software Developer</h3><p>…</p><h4>Hey! Thanks for reading my post! <a href="https://lloydcarroll.substack.com/?utm_campaign=medium">My work now lives here</a> ⬅️</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*HdPaaLzov9CzZ7AL" /><figcaption><a href="https://unsplash.com/photos/bPVM4nOy0Rg">https://unsplash.com/photos/bPVM4nOy0Rg</a></figcaption></figure><p>A couple of my friends have lost their jobs through COVID. They don’t work in “tech”, but it was something they’d always wanted to know more about.</p><p>I put together a quick overview on how to get started as a developer for them and I thought I’d share it here too.</p><p>I know this is cliche but there has literally never been a better time to get started. Just this week, <a href="https://blogs.microsoft.com/blog/2020/06/30/microsoft-launches-initiative-to-help-25-million-people-worldwide-acquire-the-digital-skills-needed-in-a-covid-19-economy/?utm_source=morning_brew">Microsoft announced </a>a plan to help 25 Million people learn the skills needed to succeed in our digital world.</p><p>In times like these, it’s important to stay focused and have something to work towards — All you need is a laptop!</p><h4>But I’m 32, can I really start now?</h4><p>Yes, absolutely. There are plenty of people who get started at 30 plus, 35 plus, 40 plus!</p><p>If you get stuck in and think software engineering is for you, your first job might be with 22 yr olds. But that doesn’t really matter if you’ve all got the same skill level.</p><p>Plus there’s a significant advantage in the life experience and maturity you would bring to your role in a team.</p><p>Another thing to bear in mind is that no one knows everything. Professional software engineers spend a lot of time researching and googling things themselves. Either as a refresher or to find a better way of doing something.</p><p><strong>Still not convinced?</strong></p><p>Fine, here’s some evidence:</p><ul><li><a href="https://medium.com/@SamOrgill/how-to-retrain-to-be-a-software-developer-at-30-in-an-age-biased-industry-570eccfd276b">Retraining to be a software developer at 30</a></li><li><a href="https://medium.freecodecamp.org/stories-from-300-developers-who-got-their-first-tech-job-in-their-30s-40s-and-50s-64306eb6bb27">300 developers who got their first jobs in their 30’s, 40’s and 50’s</a></li><li><a href="https://techbeacon.com/app-dev-testing/so-you-want-be-great-developer-30-inspiring-stories">So you want to be a great developer at 30</a></li></ul><p>I mentioned Microsoft committing to training people before, but there’s also tools like <a href="https://westryve.com/">Stryve</a> popping up, where you can keep track of your learning and find a community of other people on the same path.</p><h4>Ok, you’ve convinced me, now what!</h4><p>Before we read further, I want to say that it is easy to get overwhelmed. But, know that literally any of this stuff is google-able.</p><p>So if you get stuck at any time during this article or after, it is all there… you just have to know what to look for.</p><p>There are a couple of gotchyas:</p><ul><li>Watch out for the date of any articles you google. Recency is important because things move fast in technology.</li><li>Cross-reference anything you google for other consensus. A lot of times you will find one persons opinion on how to do something. Make sure it’s the right way for you to move forward and be open to trial and error.</li></ul><h4>The Basics</h4><p>Generally, development is split into two halves; ”front-end” and ”back-end”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9XLLSEa-CMFc-UIq.png" /><figcaption><a href="https://devcode.la/blog/frontend-y-backend/">https://devcode.la/blog/frontend-y-backend/</a></figcaption></figure><p>Most modern websites work by running applications and databases on servers, which return a web page to you when you land on a URL.</p><h4>Woah, hold up, <em>servers</em>, <em>applications</em> and <em>databases</em>?</h4><p>Remember how I said you can google this stuff?</p><p>… Just joking! Maybe we do need a bit of a glossary of terms</p><ul><li><strong>Application</strong>: a piece of software that does tasks like storing and retrieving information</li><li><strong>UI</strong> (user interface): how the website looks and feels (front-end)</li><li><strong>Database</strong>: A software application that stores information in a specific way so that it can be retrieved (back-end)</li><li><strong>Server</strong>: A kind of computer that allows us to store a database or application on it (back-end)</li><li>“<strong>foobar</strong>”: words that are used in place of (or in reference to) other words you might use in a finished website, like; User, Post, Comment</li><li><strong>Hello World</strong>: A term used to define how to make the simplest working solution within a tech stack</li></ul><p>Take a blog site for instance. There is a front end UI which lets us read the blog posts and comments.</p><p>There would also be some kind of application that retrieves data from a back-end database in a certain way so that it can be displayed the right way on the UI.</p><p>I hope that’s starting to make sense…</p><p>If you want to read more, here is <a href="https://careerfoundry.com/en/blog/web-development/50-web-development-buzzwords-that-all-new-programmers-should-learn/">50 terms</a> and acronyms that you should start to get your head around</p><h4>Back-end or front-end development?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E_kCOaK4GxExaTCp.jpg" /><figcaption><a href="http://www.redrobotsystems.co.uk/front-end-middleware-back-end/">http://www.redrobotsystems.co.uk/front-end-middleware-back-end/</a></figcaption></figure><p>Often, people will end up in a career that takes them down the front end or back end path but sometimes people do both.</p><p>For anyone getting started, however, my recommendation is always to choose front end web development.</p><p>The reason is that its simple to get started, there are heaps of resources available and you can see your work immediately!</p><h3>Ok, I’m ready…</h3><p>I’ll outline a few things in this next section</p><ul><li>Front end basics</li><li>Setting up your laptop</li><li>HelloWorld.html</li></ul><p><strong>Front end basics</strong></p><p>To build a basic web page, you use these 3 main languages:</p><ul><li><a href="https://www.w3schools.com/">HTML</a> to tell your browser how to display the page itself</li><li><a href="https://www.w3schools.com/css/default.asp">CSS</a> to tell the browser how to style and colour the page</li><li><a href="https://www.w3schools.com/js/default.asp">JavaScript</a> (or JS) to tell the browser to do smart stuff on the page or do additional styling</li></ul><p>A quick search will show you there are heaps of variants and “flavours” of CSS and JavaScript but we don’t need to worry about that right now.</p><p><strong>Setting up your laptop:</strong></p><p>I said at the top that all you need is a laptop. This is absolutely true.</p><p>A code editor is like the GarageBand or iMovie of software development.</p><p>There are a bunch of them our there, but VisualStudio Code is hands down the best (and yep, it’s free!): <a href="https://code.visualstudio.com/">https://code.visualstudio.com/</a></p><p>Download it and follow the instructions to install it.</p><p><strong>HelloWorld</strong></p><p>Ok, open up VisualStudio Code.</p><ul><li>Select File -&gt; New File from the toolbar</li><li>Select File -&gt; Save As</li><li>Select your Desktop as the folder to save in</li><li>Name the new file “HelloWorld.html”</li></ul><p>Next copy and paste this text below into the file:</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br>&lt;body&gt;<br><br>&lt;h1&gt;Hello World! &lt;/h1&gt;<br>&lt;h2&gt;This is My First JavaScript&lt;/h2&gt;<br><br>&lt;button type=&quot;button&quot;<br>onclick=&quot;document.getElementById(&#39;demo&#39;).innerHTML = Date()&quot;&gt;<br>Click me to display Date and Time.&lt;/button&gt;<br><br>&lt;p id=&quot;demo&quot;&gt;&lt;/p&gt;<br><br>&lt;/body&gt;<br>&lt;/html&gt;</pre><p>Hit save in Visual Studio Code again.</p><p>Open up your desktop in Finder and right-click to “Open With” and select your default browser (mine is Chrome).</p><p>What happened? A working webpage!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*0Vi7aEA2u83ry9_K_-nxXw.gif" /></figure><p>Yep, it’s <em>that easy!</em></p><h4>Ok but surely that’s not it? This page looks like crap!</h4><p>You’re right, there is a lot more to it! This is just a teaser to get you started :)</p><p>So if you thought that was fun and want to keep digging, there are a few things you should do.</p><p>Pick a language, stick to it, complete tutorials until you can build something on your own. Practice, practice, practice.</p><p>At some stage in the future, you will probably want to do a course somewhere like <a href="https://generalassemb.ly/education?format=all&amp;where=online">General Assembly</a> or somewhere else, but to get the most out of something like that you’ll need a strong handle on the foundations.</p><h3>My recommended path to becoming a developer for real</h3><h4>1. Understanding the basics of HTML:</h4><p>This will give you a better taste for HTML and get you started with a bunch of <a href="https://www.w3schools.com/html/default.asp">HTML Tutorials</a>.</p><h4>2. Understand the foundations of everything:</h4><p>This free course from Stanford University has been recommended for people starting out for a number of years — <a href="https://online.stanford.edu/courses/soe-ycscs101-sp-computer-science-101">Computer Science 101</a></p><p>It goes deeper into how computers work and will give you a better foundation to build on.</p><h4>3. Getting specific:</h4><p>One of the best resources available is <a href="https://www.freecodecamp.org/">https://www.freecodecamp.org/</a>. Have a dig around and pick something to learn that interests you.</p><p>If you enjoy it, get through it and want to move on you can also look at something like</p><ul><li><a href="https://developers.google.com/web/fundamentals">Web Fundamentals</a> from Google</li><li>Detailed courses and certification with <a href="https://docs.microsoft.com/en-us/learn/">Microsoft Learn</a></li></ul><p>The thing with these is that they’re kinda skewed toward Google and Microsoft, so don’t get too hung up on that.</p><h4>4. Extended:</h4><p>If you’re capping out with the free resources, it might be time to sign up to something like</p><ul><li><a href="https://www.codecademy.com/">https://www.codecademy.com/</a> or</li><li><a href="https://generalassemb.ly/">https://generalassemb.ly/</a></li></ul><p>These offer paid courses and certifications which will be really helpful when you’re trying to get a job.</p><h3>That’s it!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*zFuBeXYWRcHyVZ_m" /><figcaption><a href="https://unsplash.com/photos/YVT21p6pO_g">https://unsplash.com/photos/YVT21p6pO_g</a></figcaption></figure><p>I really hope this article leaves you feeling empowered to get started in a new career as a software developer.</p><p>I’d love to hear feedback on the content or any other resources that you think are good for new starters.</p><p>Peace!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35c8815f5168" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/getting-started-as-a-software-developer-35c8815f5168">Getting Started as a Software Developer</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The end of XML for Property Tech]]></title>
            <link>https://medium.com/domain-tech/domain-api-for-real-estate-crms-c3ee7da920cf?source=rss-2dbc3eb8d7f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3ee7da920cf</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[property-management]]></category>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[real-estate]]></category>
            <category><![CDATA[proptech]]></category>
            <dc:creator><![CDATA[Lloyd Carroll]]></dc:creator>
            <pubDate>Sun, 25 Nov 2018 01:00:39 GMT</pubDate>
            <atom:updated>2025-10-24T00:39:48.722Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is a semi-technical post. If you’re interested in how the Domain Property API can work for you, check out our </em><a href="https://developer.domain.com.au/docs/packages-and-plans/crm"><em>CRM getting started page</em></a><em> or </em><a href="https://domainapi.typeform.com/to/HuGH11"><em>get in touch</em></a><em>.</em></p><h4>Hey! Thanks for reading my post! <a href="https://lloydcarroll.substack.com/?utm_campaign=medium">My work now lives here</a> ⬅️</h4><h3>Why use a CRM</h3><p>In the real estate industry a “CRM” builds web applications that act as intermediaries between agencies and the various portals and websites they use to market their properties. These CRM’s provide a central location to manage listings and media content, and to capture enquires about those listings across the various real estate portals like <a href="https://domain.com.au/">domain.com.au</a>.</p><h3>XML Bulk Upload?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*42hOJbj1OVXj42MddT0Bjw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/VNXhUxPOL4c?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kristina Tamašauskaitė</a> on <a href="https://unsplash.com/search/photos/old?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Until recently, integration between a CRM and real estate website was conducted via “XML Bulk Upload”. XML is a widely accepted file format standard that allowed files and metadata to be transferred in a predictable way.</p><p>If you’re familiar with XML, you’ll know that it’s been declining in use for over a decade. The reason for this decline was largely due to the way files were generated, transported and ingested, or “read”.</p><p>An XML schema is relatively easy to maintain once the standard is met. But, due to XMLs rigidity it has always been hard to change the format if the party who defined the schema originally, wanted to add or retract an element from the existing schema.</p><p>For example, Domain adding a flag to denote a `ruralListing = true` becomes a major change management exercise with all existing CRM’s who upload to Domain.</p><p>Latency between changes in the CRM and the Domain Website also became an issue. CRM developers would create workflows where listings would be uploaded or changed in “bulk” as a scheduled job.</p><p>This means that agents would receive enquiries for properties that had already sold or leased, and on the flip-side would miss out on leads that they might have received while the listing was stuck in the CRM’s processing queue.</p><p>This isn’t a blemish on the CRM’s developers: it’s simply a representation of how technically mature the industry was at the time the XML standard was born, and how far we’ve come with real-time technology since then.</p><p>Ultimately, these issues have had the potential to affect the Agents reputation as well as Domains’ end-users satisfaction.</p><p>As Domain aims to provide the best platform for people to find their home, and a significant chunk of our revenue comes from those Agents who expose their listings on Domain — we had an opportunity to define a new norm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uYOHxCXr-5j_FLlfRJkxRw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/sggw4-qDD54?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Annie Spratt</a> on <a href="https://unsplash.com/search/photos/start-up?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Which brings us to the domain.com.au <a href="https://developer.domain.com.au/docs/introduction">Property API</a>.</h3><p>Since the 2000s, adoption and acceptance of public API’s has grown exponentially. Organisations in almost all industry verticals now see the value of making their internal systems accessible to the public. Take Dropbox and Slack for example, who’s core products are not API’s, but are completely accessible via their public API.</p><p>Likewise, developers recoginise that they can take advantage of this access to benefit their core customers.</p><p><a href="https://developer.domain.com.au/docs/introduction">Our API</a> empowers CRM’s to provide a better Agent and Customer experience by enabling a fast, reliable and secure way to integrate with <a href="http://domain.com.au/">domain.com.au</a>, <a href="http://commercialrealestate.com.au/">commercialrealestate.com.au</a> and soon, <a href="http://allhomes.com.au/">allhomes.com.au</a>.</p><p>From the start, we knew that access to the <strong>full</strong> listings life-cycle was crucial for our developer customers. Exposing just one or two endpoints would not be valuable enough for them to migrate to the API.</p><p>Our V1 API was the first real estate API that exposed the complete CRUD endpoints for our listings service, including functionality to check performance down to a single listing.</p><p>You could also search for an Agent and Agency, or locate all listings belonging to them.</p><p>Since then, we’ve built out our <a href="https://developer.domain.com.au/docs/webhooks">Webhook</a> offering to allow real-time access to leads as they’re received from customers and included property evaluation data to help Agents have more informed conversations with prospects.</p><h4>So why move to API?</h4><p>Our Property API is the new benchmark for listings management — But as an Agent or a CRM, why would you be better off ditching XML?</p><p><strong>Speed</strong></p><ul><li>Know that new or updated listings will be available on Domain within minutes</li><li>Receive <a href="https://developer.domain.com.au/docs/endpoints/webhooks/webhooks_createsubscription">webhook</a> notifications for all Enquiries, to be the first to get in touch with prospects on via vendor and sales channels</li><li>Access previous listings and enquiries on Domain for a quicker ramp up with a new Agency or CRM</li></ul><p><strong>Reliability</strong></p><ul><li>Guaranteed notifications of every new lead received, without worrying about email template changes, accidental spam walls and proxy email addresses</li><li>1:1 listing create, update and archive with live processing and error report endpoints</li><li>99.995% service availability with a no planned outages policy and multiple layers of DDOS protection</li></ul><p><strong>Security</strong></p><ul><li>Guaranteed safety of Agents leads and listing performance statistics through OAuth2 compliant Domain Membership service</li><li>Agencies can revoke a CRM’s access at any time</li><li>CRM developers can use our organisations feature to control who access to the production API</li></ul><p><strong>Feature Rich</strong></p><ul><li>Build our property <a href="https://developer.domain.com.au/docs/endpoints/properties/properties_getpriceestimate">price estimates</a> into your CRM to inform richer conversations between Agents and Vendors</li><li>Leverage <a href="https://developer.domain.com.au/docs/endpoints/suburbperformancestatistics/suburbperformancestatistics_get">suburb performance</a> statistics for better conversations with Buyers and Vendors</li><li>Use our free <a href="https://developer.domain.com.au/docs/endpoints/properties/properties_suggest">property validation</a> endpoint to verify addresses on the fly as listings are created in your CRM</li></ul><h3>Where to from here?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*75Goj0CI3DzgMTvXxxZ6FA.jpeg" /></figure><p>We have a number of initiatives on our roadmap including ability to check the Domain listing calculator via API and receive notifications once your listing has completed processing. We’re also working on SDKs in the languages most common in the industry.</p><p>Right now, we want to continue to work with more CRM’s to help them migrate to API.</p><p>We want to understand how we can make it easier for you to get started on the property API, and what else we can look to include to help you service your customers better.</p><p>You can check out our <a href="https://developer.domain.com.au/docs/packages-and-plans/crm">CRM getting started guide</a> and reach out to our team directly on <a href="https://domainapi.typeform.com/to/HuGH11">dev-relations@domain.com.au</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3ee7da920cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/domain-tech/domain-api-for-real-estate-crms-c3ee7da920cf">The end of XML for Property Tech</a> was originally published in <a href="https://medium.com/domain-tech">Tech @ Domain</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Better decisions: two systems ]]></title>
            <link>https://uxdesign.cc/better-decisions-72e955c70a5c?source=rss-2dbc3eb8d7f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/72e955c70a5c</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Lloyd Carroll]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 09:49:24 GMT</pubDate>
            <atom:updated>2025-10-24T00:38:56.843Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hey! Thanks for reading my post! <a href="https://lloydcarroll.substack.com/?utm_campaign=medium">My work now lives here</a> ⬅️</h4><blockquote>“If there is time to reflect, slowing down is likely to be a good idea.”</blockquote><p>– Daniel Kahneman, ‘Thinking, Fast and Slow’</p><p>The process of making decisions is the same for most of us: come up with a set of options based on the information we have at hand, and try to select the best option against a set of criteria we trust.</p><p>Leaders are tasked with making critical decisions every day, but rarely do we stop to check if our decision making process is still accurate, and the outcomes as expected.</p><p>Daniel Kahneman is a psychologist who’s work focused on judgment and decision-making, as well as behavioral economics.</p><p>His <a href="https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman-ebook/dp/B00555X8OA">book</a> “Thinking, Fast and Slow” is built around a vast body of research and statistical analysis from the investment banking industry, and challenges our capacity to make decisions without subconscious bias clouding our vision.</p><p>Kahneman posits’ that although we might think we’re taking a logical approach, we now know that these decisions are not made by drawing on data and evidence in the way we expect.</p><p>The findings outlined have a clear overlay for product and technology leaders; where the strategic decisions we make continue to carry more weight as barriers to entry drop, providing customers more choice and leverage.</p><h3>Defining The Two Systems</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bdDl2hkVO8qx_zA7.png" /><figcaption><a href="https://www.rogerleishman.com/2017/12/thing1.html">Source</a></figcaption></figure><p>While there are many ways to describe and categorise the different decision biases we carry with us, Kahneman adds an easy to understand abstraction to our thought processes which he defines as two, distinct systems:</p><blockquote>“System 1 operates automatically and quickly, with little or no effort and no sense of voluntary control”</blockquote><p>System 1 is the intuitive, rapid and automatic system which demands less energy is where most of our decisions are made.</p><p>We use our experiences, perception of past events and biases to make decisions with this system.</p><blockquote>“System 2 allocates attention to the effortful mental activities that demand it, including complex computations”</blockquote><p>This is the inherently slower, thinking, conscious and effortful system which we engage for learning, but do not engage as much as we should for decision-making activities.</p><p>Key to working with these models to make better decisions is accepting that although we might feel like we are conducting critical analysis when making strategic decisions, more often than not we remain reliant on bias-affected memories and expectations that System 1 serves us.</p><h3>Lazy Thinking</h3><p>One striking observation from Kahneman’s research is that although System 2 is far more reliable than System 1, System 2 is inherently lazy.</p><p>That is to say, if the information to make a decision appears to be available at system 1, system 2 will happily leave that responsibly with system 1 and remain idle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CTbB2g53hXyp7YQK.png" /><figcaption><a href="https://bigthink.com/errors-we-live-by/kahnemans-mind-clarifying-biases)">Source</a></figcaption></figure><p>A great example of the difference between System 1 and System 2 is in this riddle. Try answering it and, after you read it, immediately write down the first answer that crosses your mind:</p><blockquote>“A bat and a ball cost $1.10 in total. The bat costs $1.00 more than the ball. How much does the ball cost?”</blockquote><p>If you said that the ball cost 10 cents, you aren’t alone. But you’d be incorrect.</p><p>If the ball costs 10 cents, then the bat would cost $1.10 <em>(“The bat costs $1.00 more than the ball.”)</em>, which would total $1.20 breaking the stated constraints <em>(“A bat and a ball cost $1.10 total.”)</em>.</p><p>The answer is that the ball costs 5 cents (consequently, the bat is $1.05).</p><p><strong>Wait, what?</strong></p><p>Part of the reason for this laziness is the sheer availability of information from System 1.</p><p>The speed with which we are able to respond to changing circumstances with this voluntary system is far greater than the effort required to engage and leverage the logic of System 2.</p><p>Another reason for is the physical energy required to support System 2.</p><p>The brain uses <em>more</em> energy when we are conducting tasks that rely heavily on System 2.</p><p>As we lean on System 2 more, we may feel some kind of “decision-fatigue” and are more likely to fall back on readily available information at system 1.</p><p>As such, we have a propensity to fall back into the answers suggested to us by system 1 when engaged in tasks requiring more logic, because our body’s energy stores are actively supporting System 2.</p><h3>Memory vs. Experience</h3><p>Like it or not, the fact is we simply do not accurately comprehend the past the way that we <em>think</em> we do:</p><blockquote>“The core of the illusion is that we believe we understand the past, which implies that the future also should be knowable, but in fact we understand the past less than we believe we do.”</blockquote><p>What Kahneman is saying here is that those prior decisions and outcomes system 1 uses to gauge how we should respond to the current situation, are themselves tainted by our preferences and other experiences we have had and, by how we expected or would have preferred something to turn out.</p><p><strong>Deep, huh?!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/0*6RWVhmwU_-NMrLEK.png" /><figcaption><a href="https://greenbookblog.org/2012/03/15/lessons-from-thinking-fast-slow-system-1-and-system-2/">Source</a></figcaption></figure><p>This is crucial to keep front of mind when making decisions that affect customers or end-users.</p><p>We can apply this by challenging initial preferences for a certain “solution” or product feature.</p><p>It can actually be liberating to dig into why you think taking a certain direction is correct:</p><p><em>Is there data? If so, does it support your hypothesis? If not, how have you arrived at that solution and is it possible to gather that data?</em></p><p>I also think this is relevant when leading process improvement or change initiatives.</p><p>Oftentimes, teams will focus on the perceived negatives that may come out of a change initiative while overlooking the positive benefits that have occurred as a result.</p><p>In this instance, the baseline analysis that done to determine current state is key to understanding and communicating the changes that have occurred (positive and negative).</p><p>Ensuring that this analysis is made available to teams impacted by the change and kept current throughout the change process, will help bridge the gap between our biased memories and the actual impact of the change.</p><h3>Speed vs. Outcomes</h3><p>Another fascinating finding outlined in the book is that out of all surveyed investors, the most active traders had the worst returns.</p><p>That is to say; the traders who made <em>more</em> <a href="https://www.fool.com/investing/general/2014/11/24/9-critical-investing-lessons-from-a-nobel-prize-wi.aspx">changes to their portfolio</a>, had <em>worse performing portfolios </em>than their peers who made less trades in the same period.</p><p><strong>Why?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bOJeUcaewXXL7WeG" /><figcaption><a href="http://www.pseudoparanormal.com/2017/08/book-report-thinking-fast-and-slow_8.html">Source</a></figcaption></figure><p>The traders’ decision to increase trade frequency was driven by a skewed reliance on System 1, where decisions are not supported by thorough analysis.</p><p>This in turn lead to trades that were either bad, or worse than they could have been had the appropriate time been spent up front to understand the risk.</p><p>This is a self-depreciating, destructive cycle, where System 1 guides us to make a call based on poor evidence, and then when the result is poor, we don’t learn from it because we don’t take the necessary time with System 2 to reflect on that decision and outcome process.</p><p>Think for a moment about how this kind of “decision bi-polar” could affect the efficacy of your product strategy.</p><p>Far too often, product teams rely on prior experience and hypotheses to come to “strategic” product and roadmap decisions, when these could have been made more accurately using readily available customer and product data.</p><p><strong>So what about the other traders?</strong></p><blockquote>“In addition to improving the emotional quality of life, the deliberate avoidance of exposure to short-term outcomes improves the quality of both decisions and outcomes.”</blockquote><p>This ties in to the concept of <a href="https://www.mckinsey.com/business-functions/organization/our-insights/the-organization-blog/slowing-down-to-speed-up">slowing down to speed up</a>, or focusing on the job to be done and product outcomes, instead of flawed success measures like team output.</p><p>Although some commentators feel differently, I don’t believe Kahneman is mandating that metrics should drive every aspect of the decision-making process.</p><p>Instead, data and analytics should be investigated and leveraged towards informing the why or what of a decision.</p><p>For example, setting the next quarters’ focus should be based on facts at hand about our customers desired outcomes, against a calculated return on investment.</p><h3>The take-home message?</h3><p>Decisions made with System 1 are okay for certain situations and short term outcomes like troubleshooting a production bug or deciding sprint priorities.</p><p>Any strategic decisions should rely on System 2 and be underpinned by hard data, projections and (you guessed it) customer needs.</p><p>Likewise, when digging into a new problem that we potentially want to solve with our product, we need to remain focused on the problem and strategic goals at hand. Is revenue, growth, adoption or innovation the focus? Does the problem tie into that?</p><p>Moreover, Kahnemans’ book is an absolute must read for decision-makers.</p><p>It challenged the way I make decisions every day by providing great insight into how we <em>actually</em> behave vs. how we should be aiming to behave under pressure.</p><p>I am guilty of falling back to System 1, but feel empowered to recognise when this has occurred and reflect on my decisions in a new light.</p><p>If you enjoyed this, please give it a 👏🏻, share or shoot me a comment. This post originally appeared on my blog <a href="https://lloydcarroll.com/blog/post-2-28jaj">https://lloydcarroll.com/blog/post-2-28jaj</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72e955c70a5c" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/better-decisions-72e955c70a5c">Better decisions: two systems 🧠</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seven Deadly Sins of Software Delivery]]></title>
            <link>https://medium.com/domain-tech/seven-deadly-sins-of-software-delivery-7563c0857843?source=rss-2dbc3eb8d7f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7563c0857843</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[cicd]]></category>
            <dc:creator><![CDATA[Lloyd Carroll]]></dc:creator>
            <pubDate>Mon, 16 Apr 2018 12:33:56 GMT</pubDate>
            <atom:updated>2025-10-24T00:40:15.214Z</atom:updated>
            <content:encoded><![CDATA[<p>…</p><h4>Hey! Thanks for reading my post! <a href="https://lloydcarroll.substack.com/?utm_campaign=medium">My work now lives here</a> ⬅️</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mXTG8OsqpNbJseZQuZbysQ.jpeg" /><figcaption><a href="http://www.deadlysins.com/gluttony/">Seven Deadly Sins — Gluttony</a></figcaption></figure><p>Based on recent engagements I and my network have had, I’ve decided to write up some of the key fallacies that I see occurring in software product deliveries today.</p><h4>1. Not knowing the problem you’re solving</h4><p>I can’t stress enough how important this is — yet time and time again, I see projects that have been kicked-off without a clearly defined problem statement.</p><p>Without one, it is difficult to gather adequate requirements, build shared understanding amongst the team, develop scope or accurately measure outcomes.</p><p>If you don’t feel you can talk through the problem your software or product is going to solve, take it back to basics. Understand the needs and problems that your key stakeholders or target customers are facing and leverage their feedback to set your backlog and test your product.</p><h4>2. Releasing anything you can’t measure</h4><p>If you aren’t able to measure the success of your product, it is difficult to determine where you should focus your attention next.</p><p>With software itself, if you don’t have logs, how do you know if your system is holding up under pressure, and where it’s falling over?</p><p>It’s no different for the product as a whole.</p><blockquote>Build, Measure, Learn</blockquote><p>Eric Reis’ <a href="http://theleanstartup.com/principles">Lean Startup</a> method coins the “Build, Measure, Learn” loop as a way to iterate everything from vision with your leadership team, down to setting strategy and prioritising your backlog.</p><p>This has theory has been proven time and time again. Measure the right things and be willing to challenge your biases and learn from your customers.</p><h4>3. Seeing deadlines as the enemy</h4><p>The Agile Scrum framework was conceptualised out of a need to combat insane deadlines in B2C software deliveries. Ultimately, they provide leverage for your team to prioritise what’s important. It narrows the scope to focus on delivering what can be delivered, while removing external blockers that might linger without the implicit pressure of a date.</p><p>Remember, Agile is a way of building software and products with the knowledge that things aren’t always as they seem; it is not a path to delivering “faster” or without deadlines.</p><p>If a deadline is in place, we need to build adaptability into our plans to allow flexibility based on customer feedback or moments of clarity throughout the build phase.</p><p>As the deadline approaches, scope has to be reduced and if that can’t be reduced, quality is next in line – this in turn increases risk.</p><p>On the other hand, don’t plan <a href="https://www.techrepublic.com/blog/10-things/10-classic-mistakes-that-plague-software-development-projects/">too far ahead </a>and do not commit to any dates without engaging subject matter experts who’s areas of expertise the software or product will cover.</p><h4>4. Scrum Masters are not Project Managers</h4><p>Although highly valuable roles, they’re <a href="https://www.knowledgehut.com/blog/agile-management/five-common-mistakes-in-agile">seriously different</a> in both responsibilities and importantly: personality.</p><p>The scrum master is primarily a facilitator and coach, understanding the needs of the team and working to ensure they’re met, while balancing the needs of the teams’ customer (generally Product people). They are responsible for keeping the team on track, ensuring agile delivery practices are followed and improved and, maintaining team “health”.</p><p>Whereas, Project Managers (agile or otherwise) work with stakeholders to set priorities, understand risks and determine critical paths. They take on the responsibility of tracking requirements, project change management, ticket prioritisation and resource allocation.</p><p>I have no quick tips to help you avoid this fallacy, but my observation is that it is commonly an agile maturity piece that can be addressed at a programme transformation or org structure level.</p><p>You need to identify the need you’re trying to fulfil with these distinct roles: is it task pushing, deadline watching and stakeholder communication? Or is it team cohesiveness, performance and better software?</p><p>Ultimately, if you’re asking your scrum master to make <a href="https://www.scrumalliance.org/community/articles/2012/august/a-scrum-master-is-not-a-project-manager-by-another">decisions</a> about priority or deadlines, you should rethink your delivery strategy.</p><h4>5. Missing product mindset</h4><p>As technology professionals, we need to rethink how we position our expertise.</p><p>The code you ship, your ability to <em>write</em> code in the first place, the analysis done to understand user needs, the vision you put into creating your product strategy. These are all skills that provide a benefit to some consumer; ergo, they’re products we provide our colleagues, stakeholders and customers.</p><p>Failing to see our individual contribution as a product is a missed opportunity. Shifting into this mindset provides a grounding from where we can leverage our implicit knowledge and learned experiences towards better products, solution design and customer outcomes.</p><h4>6. Too little documentation</h4><p>We are probably all be familiar with this Agile value:</p><blockquote><em>Working Software over Comprehensive Documentation</em></blockquote><p>Agile Manifesto, 2001…</p><p>But what about once you’ve launched and have a new Product Manager or Engineer joining the team? What about when you’re handing a feature to QA to test (yes many teams still have QA — and they add value!)?</p><p>The emphasis on working code over comprehensive documentation does not mean <a href="https://www.knowledgehut.com/blog/agile-management/five-common-mistakes-in-agile">no documentation</a>. And valuable documentation does not mean TOGAF 9.1 Certified architecture artefacts either (what a mouthful).</p><p>Document the value that your product features provide, spin up some whiteboard diagrams on the system or work flows as a team and post them on a wiki somewhere.</p><p>As you grow and scale, you need to ensure that you can on-board new team members quickly, and maintain availability of critical production systems.</p><p>Documentation is a key piece to enabling both these things.</p><h4>7. Fear of releasing (too early)</h4><p>The highest performing technology organisations are continuously deploying features to production.</p><p>Yet, I still work with product and delivery teams who are afraid of this shift — and I do understand it.</p><p>If you’ve been working in tech long enough, you’ve definitely experienced the pain of a call from an angry exec who can’t login at 10pm, or finding all the Ops people’s phones are “broken” after an erroneous Friday afternoon release.</p><p>That said, CICD is not going anywhere. Along with cloud technologies, it is enabled largely by the culture shift towards automating anything that we do manually more than a couple of times.</p><p>This shift means that we can complete steps in the release chain at the click of a button instead of handing them off to other teams, or waiting for change approvals. Code can be committed, tested and deployed without the long “release trains” of yore.</p><p>This is great for your product and for your teams. It’s a better motivator for engineering teams to ensure their services will work in production. It speeds up the time to release which then allows you to catch any other regression issues or customer feedback sooner, so that adjustments can be made sooner again.</p><p>In fact, if there was one thing here I’d say fix first, it would be to empower your development teams to release to production as they see fit.</p><p><em>If you enjoyed this, please give it a 👏🏻 and shoot me a comment with any feedback you might have, or anything you think I’ve missed.</em></p><p><em>You can reach me at </em><a href="http://bit.ly/2KnPfYd"><em>lloydcarroll.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7563c0857843" width="1" height="1" alt=""><hr><p><a href="https://medium.com/domain-tech/seven-deadly-sins-of-software-delivery-7563c0857843">Seven Deadly Sins of Software Delivery</a> was originally published in <a href="https://medium.com/domain-tech">Tech @ Domain</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>