<?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[cinch Technology - Medium]]></title>
        <description><![CDATA[cinch Technology - Medium]]></description>
        <link>https://medium.com/cinch-technology?source=rss----dd91e4c4d50a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>cinch Technology - Medium</title>
            <link>https://medium.com/cinch-technology?source=rss----dd91e4c4d50a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:29:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/cinch-technology" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Spending a day with unicorns at AWS GameDay]]></title>
            <link>https://medium.com/cinch-technology/spending-a-day-with-unicorns-at-aws-gameday-c30a0ea66484?source=rss----dd91e4c4d50a---4</link>
            <guid isPermaLink="false">https://medium.com/p/c30a0ea66484</guid>
            <category><![CDATA[fun]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Toli]]></dc:creator>
            <pubDate>Fri, 10 Mar 2023 16:03:47 GMT</pubDate>
            <atom:updated>2023-03-10T16:05:53.646Z</atom:updated>
            <content:encoded><![CDATA[<p>In October 2022, 50 of us attended the Amazon Web Services (AWS) GameDay. Whether you’ve never heard of it or you want to participate, I hope this gives you a flavour of what to expect if you attend one in the future.</p><p>And if you are attending one soon, scroll down to the end of our post for our takeaways — they may help you!</p><h3>What is AWS GameDay?</h3><p>GameDay is a collaborative learning exercise that tests skills in implementing AWS solutions to solve real-world problems in a gamified, risk-free environment. This is a <strong>hands-on</strong> opportunity for technical professionals like us at cinch to explore AWS services, architecture patterns, best practices, and group cooperation.</p><p>Every GameDay is set out in the same way. Participants are new hires on their first day at Unicorn Rentals — the <strong>world&#39;s largest provider of mythical creatures</strong>. Unicorn Rentals is a fictitious new start-up starting to branch into Infinidash, using Unicorns as a taxi service.</p><h3><strong>So, what did our day entail?</strong></h3><p>Our challenge was managing Unicorn Rentals API (Application Programming Interface) requests and ensuring this new service <strong>ran smoothly</strong>. The engineers working on this before had left this project half-completed, so we were up against the clock to <strong>complete</strong> the work and earn as much <strong>money</strong> as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*_jFMTpFTqmpK7NIb3NjnGg.png" /><figcaption>The game’s schedule is portrayed as nine days in the calendar. Action started on Friday — day 4</figcaption></figure><p>We were divided into teams, and each given a dashboard each that tracked outstanding tasks to complete and monitor:</p><ul><li>the <strong>number</strong> of unicorn taxis we had available</li><li>how <strong>busy</strong> the taxis were</li><li>the <strong>money</strong> we have made for the company</li></ul><h3>Pizzas getting cold</h3><p>The day was broken up by an engineer’s three favourite words: <strong>‘Pizza is here!’</strong> Even that couldn’t pull us entirely away from the game. Things were starting to get <strong>exciting</strong>, and people were starting to get <strong>competitive</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/304/1*-roEeILCGEAFwqyEWDhtsQ.png" /><figcaption>No one rushed to the pizzas — people were too into the game!</figcaption></figure><h3>Time for good, collaborative decisions</h3><p>Most of the tasks were completed by lunch, so we enjoyed AWS&#39;s incredible spread of pizzas on offer. Once tasks were completed — as you might do with your business — the challenge morphed into how good you were at <strong>trading</strong> and making <strong>wise purchasing decisions</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6oNcul24_TDmxSnq9ru02w.png" /><figcaption>Watching the leaderboard was intense!</figcaption></figure><h3>So, who won?</h3><p>The day went by as quickly as it took to get a Unicorn to someone’s birthday party — very fast — and it came time to see who’d got the best results. There were three clear winners!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*pFHRxbwVlSVaBtc2gbIeWg.png" /><figcaption>Clear winners of the Game Day — they even survived some relentless Chaos Engineering at the end!</figcaption></figure><ul><li><strong>Team Slow, Late and Expensive </strong>stole the thunder — and they got first dibs on some incredible prizes.</li><li><strong>Team Rainbow Riders</strong> came second despite their efforts to deploy more efficient Cloud Resources.</li><li><strong>Team Rylan’s Rainbows </strong>clinched the third spot comfortably, and enjoyed some fantastic prizes too.</li></ul><h3>Game Days are fun</h3><p>All the teams enjoyed the day — but it wasn’t about winning but it was about <strong>learning</strong> and <strong>having fun</strong> (yes, my team came last).</p><p>As this was our first in-person Game Day, this one was ace — days like this <strong>reinforce why you got into tech </strong>in the first place.</p><p>We got to <strong>know each other better</strong>, and it gave us a chance to sink our teeth into some real tech challenges and learn so much about the field we work in.</p><h3><strong>Main takeaways</strong></h3><p>We learned some interesting things during this game that can be used both for the GameDay and day-to-day work!</p><ul><li><strong>Don’t mess with DNS</strong> — both your APIs can be down, and you will not be making money!</li><li><strong>Health Check APIs are there for a reason </strong>— you can check if your change is working before you change it in production.</li><li><strong>Teams want code freezes if they are earning money </strong>— roll back rather than roll forward.</li><li><strong>Take turns looking at the dashboard </strong>to spot things regularly — you may not be making money for various reasons at any point in time.</li><li><strong>Communicate</strong>, communicate, communicate!</li><li><strong>You can go into debt (negative money), </strong>but that’s a good thing!</li></ul><h3>We love learning</h3><p>cinch’s engineering community is a vital cog in the machine. We love learning, challenging ourselves, and working in a culture that <strong>celebrates inclusivity</strong> and <strong>collaboration</strong>. If you want to find out more about engineering opportunities at cinch, head to our <a href="https://careers.cinch.co.uk/">careers site</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c30a0ea66484" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cinch-technology/spending-a-day-with-unicorns-at-aws-gameday-c30a0ea66484">Spending a day with unicorns at AWS GameDay</a> was originally published in <a href="https://medium.com/cinch-technology">cinch Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pomodoro Pairing at cinch ]]></title>
            <link>https://medium.com/cinch-technology/pomodoro-pairing-at-cinch-3fb66ca81d36?source=rss----dd91e4c4d50a---4</link>
            <guid isPermaLink="false">https://medium.com/p/3fb66ca81d36</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[cinch]]></category>
            <category><![CDATA[pomodoro]]></category>
            <dc:creator><![CDATA[Katie Annabelle Raby]]></dc:creator>
            <pubDate>Mon, 08 Aug 2022 07:10:34 GMT</pubDate>
            <atom:updated>2022-08-08T07:10:34.405Z</atom:updated>
            <content:encoded><![CDATA[<p>In the Search squad we recently started using the ‘<em>pomodoro pairing</em>’ technique for our pairing/mobbing sessions. We wanted to try something different to keep our focus during longer sessions. Since some of us had already used the pomodoro technique before, it seemed well worth giving it a try. Since trying it for the first time, we’ve seen some great benefits, and it has now grown into a habit within the squad to use this technique during any of our collaboration sessions.</p><h3>What actually is the pomodoro technique?</h3><p>No, it has nothing to do with tomatoes! Okay, maybe a little bit. The pomodoro timer was given its namesake in the 1980s when Francesco Cirillo, a university student, used a tomato timer to measure his 25-minute interval study sessions. These short sessions became known as a pomodoro. In the pomodoro technique, <strong>work is broken down into intervals, typically around 25-minutes. Each interval is separated by a short break.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tdtoFRmkUE-etCfQz_IK1w.jpeg" /><figcaption>A handheld pomodoro tomato timer</figcaption></figure><h3>The pomodoro steps</h3><ol><li>Decide on a task</li><li>Set the pomodoro timer (25 mins, adapt to suit)</li><li>Work on the task</li><li>When the timer finishes, take a short break (typically 5 mins)</li><li>Repeat steps 2–4 until you’ve done 3 or 4 pomodoros</li><li>Take a longer break</li></ol><h3>Pomodoro pairing</h3><p>To start using the pomodoro pairing technique, take the above pomodoro steps and adapt them accordingly to fit your pairing or mobbing sessions.</p><p>A great tool to use is <a href="https://cuckoo.team/">Cuckoo Timer</a>, especially for remote teams. To get started with Cuckoo, create a shareable link which opens a new session for participants to join. In the sessions sidebar, there is an option to use the pomodoro technique, which displays the suggested work and break lengths to select from. Using a tool such as Cuckoo is a great way to ensure that everyone in the session each hears the alarm, and can hold each other accountable to the timer so that sessions don’t run over.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GPZcQuQzIVebSmaI" /><figcaption>Cuckoo interface, with a ‘Use the Pomodoro Technique’ option in the sessions sidebar.</figcaption></figure><p>After each pomodoro, choose a different driver to ensure that all participants in the pair or mob get the opportunity to regularly switch roles. Once the new driver is set up and ready to code, start the timer again for another pomodoro.</p><p>You may find yourselves drifting off too far from the task at hand during the session. If this happens, recognise it, and bring yourselves back to the task at hand. A good rule of thumb is, at the end of the current pomodoro, if you’re still working through a thought process, let that play out until the end then consider that the end of the pomodoro. Don’t forget to take your break!</p><p>Some of the benefits we’ve found so far of working in this way are:</p><ul><li>Making sure we take enough breaks — very easily forgotten throughout the day! ☕️</li><li>Working for shorter time intervals keeps navigator(s) focused on the session at hand</li><li>Regular switching of pairing roles gives ample time in each role</li><li>Manageable work sessions allow other squad members to drop in and out</li><li>Work (and commits) are broken down into manageable chunks</li></ul><p>It’s safe to say we have seen a lot of benefits to using this technique so far, and we will definitely continue to use it. Do you use pomodoro pairing in your team at work? Give it a try, and comment your experience below!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/0*GFDWUMh2bqTCSrZo.png" /></figure><p><strong>Additional resources</strong><br>- <a href="https://shopify.engineering/pair-programming-explained">Pair programming explained</a> (and other techniques you can employ)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fb66ca81d36" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cinch-technology/pomodoro-pairing-at-cinch-3fb66ca81d36">Pomodoro Pairing at cinch 🍅</a> was originally published in <a href="https://medium.com/cinch-technology">cinch Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Atomic Design: A practical interpretation from one developer]]></title>
            <link>https://medium.com/cinch-technology/atomic-design-a-practical-interpretation-from-one-developer-34c3c238003f?source=rss----dd91e4c4d50a---4</link>
            <guid isPermaLink="false">https://medium.com/p/34c3c238003f</guid>
            <dc:creator><![CDATA[Josh Stennett]]></dc:creator>
            <pubDate>Thu, 21 Jul 2022 15:12:56 GMT</pubDate>
            <atom:updated>2022-07-21T15:12:56.109Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Before reading this blog post, it’s worth reading at least chapter 2 of Atomic Design by Brad Frost: </em><a href="https://atomicdesign.bradfrost.com/table-of-contents/"><em>https://atomicdesign.bradfrost.com/table-of-contents/</em></a><em><br>Don’t worry — it’s not that long.</em></p><p><strong>Foreword</strong><br>I am a Software Engineer in Partner Tooling, mostly focussing on Front End development. We use React and have followed Atomic Design principles when trying to organise our components. This blog post is my opinion on how to practically implement Atomic Design, suggesting some guidelines to follow in addition to the textbook definitions. By no means am I stating that the approach put forward in this post is <em>correct</em>.</p><p><strong>What the book says about atomic design</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*L6zAfahmw_wCe1jQm7Bpig.jpeg" /></figure><p>Atomic Design puts forward a suggestion on how to organise components into 5 categories: Atoms, Molecules, Organisms, Pages, and Templates. Each category growing in complexity as you go up the list; except for Templates which are more like skeletons for Pages.</p><p>This is exemplified best in this image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*X7AnGFuWcrc7rOxP94Y6JQ.jpeg" /></figure><p><strong>What the book doesn’t say</strong><br>Atomic Design is an idea, not a concrete practical framework. It might actually apply more directly to design, rather than development. In order to remain implementation agnostic, it leaves lots of decisions up to the developer that might not be obvious on the surface. In attempting to follow Atomic Design, you may find yourself asking questions like:</p><p><em>“This component only consumes UI library components, does that make it an atom, or a molecule?”</em></p><p><em>“This component feels quite big, and is definitely a molecule. But at what point does it become an organism?”</em></p><p><em>“This component relies on an API call, does that effect its classification?”</em></p><p>In this blog post I am hoping to resolve lots of these questions within the context of how I approach React development, by adding onto the definitions and adding additional guidelines.</p><p><strong>Atoms</strong></p><ul><li>Atoms should be indivisible, hence the name. They form the “foundational building blocks” of your application.</li><li>Should be generic: designed to be reusable in any context, not have opinionated implementation details.</li><li>Should feel lightweight, performant, and accessible.</li><li>Should consist of basic elements only, not other components.</li><li>Should be tested via unit tests.</li><li>Can contain stateful properties, if necessary, but consideration should be given if it is needed at this level. Consider putting stateful properties in the Molecule level.</li><li>Should not make API calls or be otherwise tied to APIs.</li></ul><p><strong>Molecules</strong></p><ul><li>Preferred to be reusable, however sometimes implementation specific Molecules are necessary. E.g. “Selector” and “HomepageSelector” are both valid Molecules, but consideration should be given to the necessity for the later.</li><li>Should follow the Single Responsibility Principle, despite being a composition of Atoms, should produce one functioning element.</li><li>May consist of multiple atoms and html elements.</li><li>May contain stateful properties</li><li>May contain API requests.</li><li>Should be tested with unit tests, could have end to end/synthetic user tests.</li></ul><p><strong>Organisms</strong></p><ul><li>May be reusable but may also be implementation specific. For example, a footer bar will be very reusable, however a TableFilters organism may also be equally valid, but specific to one table.</li><li>Will consist of one or more Molecules and can have additional html elements. Possibly one Molecule repeated many times.</li><li>Should be a standalone portion of the interface and avoid depending on other Organisms.</li><li>Will likely contain API requests and stateful properties</li><li>Might be tested with unit tests, might be tested with end to end/synthetic tests</li></ul><p><strong>Pages</strong></p><ul><li>Specific instances of Templates (if they exist), orchestrating Organisms and other components into a fully functional webpage.</li><li>Likely to make API requests and contain stateful properties.</li><li>Should be tested with end to end/synthetic user tests.</li></ul><p><strong>Templates</strong></p><ul><li>Not a “bigger organism”</li><li>Page level objects that “place components into a layout and articulate the underlying content structure”.</li><li>Personally, we rarely implement these in React, but a full-page design in figma could be considered a Template.</li></ul><p><strong>Practical examples of components classification</strong><br>When trying to decide what to classify a component as, it is helpful to start “bottom up”, and settle on the lowest categorisation that fits. If the component doesn’t break any of the guidelines of what makes an atom, it is more than likely an atom. If it breaks one of the guidelines, it <em>could</em> still be an atom, but might not be. If it breaks many of the guidelines, move on to assess if it is a molecule, and so on, until you find the smallest classification that best fits the component.</p><p>Sometimes, the purpose or intention of the component is the most important factor in deciding its category. An organism component may be quite simple, but its intention, role, or purpose can place it solidly in the organism category, despite it perhaps not meeting many of the expected criteria. You may often hear developers referring to this in terms of a component “feeling” like an organism, or “feeling more like a molecule than an atom”. This blog post aims to disambiguate the classification of components as much as possible, but do not ignore this developer intuition, as its all 1s and 0s at the end of the day.</p><p>The following examples, using real components that have been simplified for the purpose of this post, should give you a good understanding of my thought process when categorising several different components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7rx1K25AbMXRrVk4siUSHA.png" /><figcaption>An example of an Atom component</figcaption></figure><p>Here we see a component that is very simple. It is indivisible, containing only one element. It has a colour property, but it isn’t stateful. While it does contain a component, it is a very simple Chakra UI component. Sometimes Chakra UI components may make this component feel like a Molecule, in this case it is very simple so fits within the Atom category.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0KfQRF0QxHX2Rg_EExEHmA.png" /><figcaption>An example of how Atom components can sometimes appear “big”</figcaption></figure><p>Here we have a component that takes a few props in, has a non-stateful property, a little bit of logic, and returns one of two elements. It could be conceived that this component is a Molecule, but in my opinion, it is still an Atom. The result of executing this component is still one element, even though it is not always the same element. You could argue that due to the conditional rendering, the component is “divisible”, but in my opinion that isn’t a big enough justification to warrant upgrading it to a Molecule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EdTBQ9EvIbHkA1AJdvOMgw.png" /><figcaption>An example of how sometimes, Molecules can appear small.</figcaption></figure><p>Here, we see a component that is composed of one element, possibly indicating that it might be an Atom. However, the element it returns is itself an Atom — the first clue that it probably something larger. Combined with that, and the fact that this component makes a web request, it should be considered a molecule. This is a good example of where the book falls short of a real-world implementation: as this is indivisible, it could be considered atomic — but in my experience this component is “larger” than an atom, even if it only returns one element.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b4_ILvR_gOGceUkpWgVVzw.png" /><figcaption>An example of a typical molecule</figcaption></figure><p>Here we see the simplest form of a molecule; there is very little going on beyond composition of multiple components. This immediately disqualifies it as an atom, and with a lack of further complexity it falls solidly into the molecule category.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AWSjwkOke9PP3n_-mltNbQ.png" /><figcaption>An example of an organism component</figcaption></figure><p>This component appears to be quite simple. It has no state or properties, and simply organises a few elements into a particular layout. Due to its use of several elements it is clearly not an atom. It could be considered a molecule, then, if it were not for one key factor: the elements (ExportButton, PageSizeSelector, Search) are all molecules themselves. This places this component firmly in the organism category, despite it being otherwise simple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ka9f85Zq2ny8Fb1OMHiSGQ.png" /><figcaption>An example of a Page component</figcaption></figure><p>This component highlights the importance of the purpose of a component being a key indicator for its category once you get to the organism/page level. Just looking at the code, it could be argued that this component is a molecule; the component only uses atoms or simple Chakra UI components, and places them in a logical layout. It doesn’t have any complicated state, hooks, api calls, etc, and so appears quite simple. However, the components’ purpose (perhaps given away by its name) is to function as a homepage or landing page for our website. In our case, this is a very simple page with nothing but a login button, essentially. This meets the criteria of the page category because the purpose of this component is to function as an entire… well, page. It just so happens that this is a relatively simple page, only containing some molecules.</p><p>Why isn’t it an organism? It probably would be an organism if it were orchestrating a section of the user interface, as opposed to a whole page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewJeBMj8q6JGb0qyntBIHg.png" /><figcaption>An example of a typical Page component</figcaption></figure><p>This component is the largest example yet, which is probably a giveaway that it is a clear-cut example of a page. Firstly, there are tons of stateful properties, a couple useEffects, a couple API calls, and a few helper functions. This should be the first indication that it’s probably not an atom or a molecule. The distinguishing characteristic here is that the components that are being consumed within this component are already organisms. Add that to the fact that the purpose of this component is to be a whole page, as discussed previously, and it should be clear that this component is categorised as a page.</p><p>Hopefully these examples help with classifying your own components within Atomic Design. I would be interested to hear other people’s strategy for organising components, within Atomic Design or not.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34c3c238003f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cinch-technology/atomic-design-a-practical-interpretation-from-one-developer-34c3c238003f">Atomic Design: A practical interpretation from one developer</a> was originally published in <a href="https://medium.com/cinch-technology">cinch Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dealing with Imposter Syndrome]]></title>
            <link>https://medium.com/cinch-technology/dealing-with-imposter-syndrome-50323d53e231?source=rss----dd91e4c4d50a---4</link>
            <guid isPermaLink="false">https://medium.com/p/50323d53e231</guid>
            <category><![CDATA[imposter-syndrome]]></category>
            <dc:creator><![CDATA[Farhanakhan]]></dc:creator>
            <pubDate>Thu, 14 Jul 2022 15:21:41 GMT</pubDate>
            <atom:updated>2022-07-14T15:21:41.767Z</atom:updated>
            <content:encoded><![CDATA[<p>This year I have decided to say yes to any and all public speaking opportunities. So when I came across one to be a guest speaker at our Ownership and Renewals Tribe day I said YES. I delivered a talk on the big bad wolf known as the Imposter Syndrome.</p><p>I had such a brilliant response from everyone present that I thought I should share it here as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LtxOrT1VGHoku6ObzefWOA.gif" /></figure><p>Close your eyes. I know an odd thing to ask while you are trying to read this.</p><p>Let me start over.</p><p>Imagine. Imagine you are sitting in a meeting (workshop/brainstorming session or something even social) and you come up with a brilliant idea. Just when you are about to say it out loud a teeny tiny voice inside of your head whispers, ‘are you sure you want to do that?’</p><p>[<em>I saw everyone present in the audience smile at this point- eyes closed and smiling. Promise it wasn’t as creepy as it sounds.</em>]</p><p>If you entertain that thought for even a fraction of a second that voice becomes louder and more forceful.</p><p>‘ Are you quite sure?? Remember the last time? Just remember how silly you felt afterward.’</p><p>More often than not you would decide against saying anything. Fast forward 5–10 minutes and there is someone in that group who says something that sounds awfully similar to what you had in mind. Aaannd... You end up feeling silly anyway.</p><p>You would be surprised (or maybe not) to find out that everyone in the audience raised their hands when asked if the situation sounded familiar.</p><p>This feeling where you think you are a fraud or that all that you have achieved is through sheer good luck which would eventually run out, and people will ‘find you’, that you are just not good enough no matter what you achieve. That nagging, anxiety-inducing feeling is known as the imposter syndrome.</p><h3>So what causes it?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*aBb4NoNfybLUhXVGSqIeew.gif" /></figure><p>The following four things:</p><ul><li>Personality traits such as perfectionism</li><li>Previous experiences. Maybe one of your ideas was shot down by someone or your hard work was brutally criticised. I was told by my high school English teacher that I wouldn’t be able to pass my English GCSE exam. Even though I know my English language skills are at an acceptable level, there are times when I start doubting myself because of my past experience.</li><li>New situations. I learn a new concept, product, or service and then I meet someone who talks about something that’s absolute gibberish to me.</li><li>Family background. If you could see me right now you would notice a smile on my face. Why? Because this hits too close to home.</li></ul><p>I belong to the South Asian community. We are a lovely bunch. We are very hospitable, love our food, and love to force-feed anyone and everyone that crosses our path. However, as parents, we are very competitive. Insanely intense. I say that with love and respect.</p><p>A couple of years ago I sat down to reflect upon why I was like that. Someone who couldn’t simply sit still. Someone who had a strong urge to be achieving big things all year round. I felt that at a time when I thought I wasn’t being ‘productive’ even though I had my hands full raising a premmie (premature baby) on home oxygen. I traced that need to my teenage years. Especially GCSEs. I still have the need to gain my parents praise and approval. I am married and have a child of my own but I still live in constant fear of disappointing my parents. These feelings can extend to authority figures such as mentors, line managers, and teachers as well.</p><p>Don’t get me wrong. Those feelings have motivated me to do and achieve all I have done so far but it can be overwhelming at times.</p><h3>….but why do we need to talk about it?</h3><p>It’s all good and well to know what Imposter Syndrome is and what causes it but why do we need to talk about it?</p><p>Well for starters, it can be exhausting and draining to project a strong image all the time. It’s important to identify and acknowledge how you feel beneath all that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*G_8M4hrXJG4Qc-wsBdtWRQ.gif" /></figure><p>Unless you do that we can’t start the conversation. Once you start talking about it you will find out that you are not alone. Our colleagues, family members, and people we look up to also battle with these feelings or have felt it at some point in their lives. There is no point in suffering in isolation. I find it very helpful to talk through these feelings because we work in an industry that has, historically, been male-dominated. Being one of the only female engineers on a Squad, and a newbie, can kick these feelings up a notch. Knowing that my colleagues who seem to know everything and are thriving in their roles also feel the same can help regulate these emotions.</p><p>Secondly, and in my opinion, most importantly, you will not get that seat at the table or that big promotion if you keep underestimating and undermining yourself. My dear friend, if you don’t feel you deserve it no one will feel that either.</p><h3>It’s not all doom and gloom.</h3><p>You CAN tackle this beast. It won’t happen overnight but all you need to do is to take that first step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*pR9P6svcXdR2QrSr6hyQtw.gif" /></figure><ul><li>Journal. Write down your past achievements. Reflect upon them. You will be surprised to find out how far you have come.</li><li>Read other people’s experiences and how they have dealt with Imposter Syndrome. I find reading autobiographies/memoirs very helpful. Listening to podcasts/talks also helps. Actually, watch Tall Girl 2. Please don’t judge my taste in movies based on this though.</li><li>Surround yourself with people who give positive vibes, motivate you, and inspire you.</li><li>Most importantly: be kind towards yourself. Celebrate your achievements. You deserve it!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50323d53e231" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cinch-technology/dealing-with-imposter-syndrome-50323d53e231">Dealing with Imposter Syndrome</a> was originally published in <a href="https://medium.com/cinch-technology">cinch Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are you sure that’s a Feature Toggle? ]]></title>
            <link>https://medium.com/cinch-technology/are-you-sure-thats-a-feature-toggle-37d58229bbbc?source=rss----dd91e4c4d50a---4</link>
            <guid isPermaLink="false">https://medium.com/p/37d58229bbbc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[feature-toggles]]></category>
            <category><![CDATA[trunk-based-development]]></category>
            <category><![CDATA[feature-toggling]]></category>
            <dc:creator><![CDATA[Greg Farrow]]></dc:creator>
            <pubDate>Mon, 04 Jul 2022 12:17:17 GMT</pubDate>
            <atom:updated>2022-07-04T12:17:17.697Z</atom:updated>
            <content:encoded><![CDATA[<h4>Feature Toggles are a simple idea, at first glance. But if you scratch below the surface there can be a lot of nuance to them.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*PyxDqktWOwJZIOXLX_07kQ.png" /><figcaption>Image from Martin Fowler</figcaption></figure><p>Martin Fowler has a rather brilliant post about this subject (well actually it’s <a href="https://blog.thepete.net/about/">Pete Hodgson</a>’s post). I make no apology for having used the article very much as the foundation for this writing:</p><p><a href="https://martinfowler.com/articles/feature-toggles.html">Feature Toggles (aka Feature Flags)</a></p><p>Maybe you should just click this link and read that article instead… seriously you should!</p><h3>Different Types of Flags</h3><p>As I inferred in the intro, simply saying “Feature Flag” can be a little bit dicey as there are several things that this can actually mean.</p><h4>Release Flag</h4><p>When we are developing code we usually want to get the code into production as soon as possible. Sometimes the code isn’t actually “production-ready”. We have a technique available to us to ensure that this code can both a) be deployed to production, and b) not ruin our Customers’ experience. We can hide this code behind a “Release Flag”.</p><p>Release Flags are especially useful when we are following Continuous Delivery principles and Trunk-based Development.</p><p>Release Flags should be short-lived (days or weeks). Once the code is complete, the flag should be removed.</p><h4>Experiment Flags</h4><p>At cinch we often run A/B tests to understand if a proposed change will positively affect Customer experience. When we perform A/B testing we will use an “Experiment Flag” in order to funnel Customers down the “A” or the “B” side of the experiment.</p><p>Experiment Flags should only stay in place for as long as is required to gain statistically relevant data and for a decision to be made (days or weeks). Once the decision is made, the flag and the “dead” side of the experiment should be removed.</p><h4>Ops Flags</h4><p>It may be desirable to control operational aspects of the product, these scenarios fall broadly into two categories, those which are short-lived and those which are long-lived. Either way, Ops Flags can be used to switch parts of the product on/off for operational reasons.</p><p>Short-lived Ops Flags may be used when a change is being made to the product which could be considered risky, e.g. it could introduce a performance problem. The Ops Flag can allow a fast cut-over from the problematic code to the original code, thereby limiting the impact on Customers.</p><p>Long-lived Ops Flags may be used to protect the product from uncontrollable circumstances For example if a 3rd party API because unresponsive, an Ops Flag would allow for the product to stop using the API and fallback gracefully.</p><p>Short-lived Ops Flags should be removed once the implementation they protect has proven reliable.</p><p>Long-lived Ops Flags will be few and far between but may be retained indefinitely.</p><h4>Permissioning Flags</h4><p>Many products will have areas that some Customers are not allowed to visit, for instance, the Premium features of a product which has a Freemium tier. Alternatively, there may be different parts of a product which are “Admin-only” for instance. To protect these restricted areas Permissioning Flags can be used.</p><p>Permissioning Flags are usually long-lived, and semi-permanent.</p><h3>Static vs Dynamic Flags</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CXzYdOZ6VHI8V5DP.png" /></figure><p>In some circumstances “hard-coding” the route is preferable, such as with a Release Toggle. Whilst code is still under development, there is no need for the Flag to be able to be switched “on”, so an elaborate toggling functionality would be overkill. This scenario requires a “Static Flag”</p><p>Whereas in other situations, such as with a Permissioning Flag, the decision about which route to follow must be made on a request-by-request basis. This type of toggle requires a “Dynamic Flag”.</p><h3>Long-lived and Short-lived Flags</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KLxImBcrVtmP1hOp.png" /></figure><p>Flags will usually either live for a few days/weeks or semi-permanently. It stands to reason that we should put more effort into the implementation quality of long-lived flags, than short-lived flags.</p><p>For instance, short-lived flags are probably fine to be implemented using a simple if/else based on a hard-coded value or environment variable. However, a long-lived flag, perhaps used as a kill switch for an unreliable 3rd party would need to be implemented in a much nicer way, perhaps using a for-purpose platform to manage it.</p><p>It is important to be mindful of the life-cycle of a flag when choosing the complexity/cleanliness of the implementation.</p><p>And there we have it. The humble Feature Toggle is in fact a many-faceted beast. So next time you are looking to use one, have a think, what’s it for? is it short-lived or long-lived? is it dynamic?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37d58229bbbc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cinch-technology/are-you-sure-thats-a-feature-toggle-37d58229bbbc">Are you sure that’s a Feature Toggle? 🤨</a> was originally published in <a href="https://medium.com/cinch-technology">cinch Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>