<?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[15gifts Engineering - Medium]]></title>
        <description><![CDATA[15gifts Engineering - Medium]]></description>
        <link>https://medium.com/15gifts-engineering?source=rss----9637e931be4a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>15gifts Engineering - Medium</title>
            <link>https://medium.com/15gifts-engineering?source=rss----9637e931be4a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:24:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/15gifts-engineering" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Scrum Project Management]]></title>
            <link>https://medium.com/15gifts-engineering/scrum-project-management-362e150b9f2d?source=rss----9637e931be4a---4</link>
            <guid isPermaLink="false">https://medium.com/p/362e150b9f2d</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Tasha B]]></dc:creator>
            <pubDate>Wed, 23 Oct 2019 14:10:49 GMT</pubDate>
            <atom:updated>2019-10-23T14:10:49.865Z</atom:updated>
            <content:encoded><![CDATA[<h3>Scrum Project Management: From Chaos to Calm</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohF3YG8IylxWv4_SO5a6Pw.jpeg" /><figcaption>Daily dev stand up at our physical scrum board (it’s a WIP!)</figcaption></figure><p>When I joined <a href="https://15gifts.com/">15gifts</a> as a project manager in 2016, there were 16 of us. The company was the epitome of a start up; the atmosphere was fresh, exciting, constant high energy, and there was a distinct feeling of camaraderie throughout the business — we were all in it and we were in it together. The evident lack of process almost added to the charm of the business, there was ample room for creativity, innovation and a natural aversion to corporate principles and practices. The issue, however, is that lack of process goes hand in hand with chaos, which isn’t sustainable and doesn’t pave the way for a happy, successful and scalable business.</p><p>So when I was tasked with implementing some kind of order to the chaos of our new build projects, I was daunted to say the least. I didn’t have a lot of confidence in our estimations or timelines and wasn’t sure where to start.</p><p>Fast forward to 3 years later and 15gifts now has over 40 employees, a reliable planning, build and delivery process, a scrum process for our development and UX teams, a kanban process for design and analytics teams, a release process… just to name a few. And guess what? We’re still that high energy, innovative and creative business with an aversion to corporate principles and practices. We still feel like a family, just a bigger one, with more successful projects under our belt and an even stronger culture. We are now at a place where our project deliverables are delivered on time and if we have delays we feel fully in control and prepared for them. In short, the inefficient chaos we were living in just three years ago feels like a distant dream.</p><p>All of our adopted processes have contributed to this, but for this post, I want to focus mainly on Project Management and Scrum, how we have approached them, and the Scrum Project Management role that we’ve carved, which has a number of advantages in successfully delivering software development projects for teams of a similar size.</p><h3><strong>Our Project Management Process</strong></h3><p>Using the <a href="https://www.prince2.com/uk/prince2-methodology">PRINCE2 methodology</a> as our basis, we took the relevant principles, themes and processes, adapted them to suit us and eventually found our own tried and tested framework for delivering new builds.</p><p>The biggest impact for us has been taking all <a href="https://www.prince2.com/uk/blog/the-7-principles-themes-and-processes-of-prince2">seven basic principles of PRINCE2</a> and applying them to our projects in a repeatable format. For example, we introduced ‘internal kick off’ meetings for everyone involved in the project internally in which the agenda is always the same:</p><ul><li>Project executive presents the <strong>business case</strong></li><li>Product owner presents a finalised <strong>scope of work</strong></li><li>Project manager presents the <strong>status</strong> of open items and <strong>next steps</strong></li><li>The team ask any questions and raise any concerns they may have about the project.</li></ul><p>This meeting alone addresses three of the basic principles, leaving the other four to be adopted throughout the build stages of the project. It also sets up the planning process nicely. The team now feel informed and invested in the project, leading to accurate estimations and a sensible project plan.</p><p>We also started mapping the PRINCE2 recommended processes to our own project management processes but quickly found that our stages didn’t exactly map to those recommended. We did, however, take the relevant activities and add them as part of our own defined stages, sprinkling in roles and processes from the Scrum framework as we went. The stages we now use for a new build are:</p><ul><li><strong>Project Scoping </strong><br>Key deliverable: A scope of work</li><li><strong>Project Kick off</strong><br>Key deliverable: Jira tickets covering all pieces of work, the project plan</li><li><strong>Development design</strong><br>Key deliverables: Finalised designs, relevant analysis, finalised Jira tickets</li><li><strong>Build</strong><br>Key deliverable: Final product live</li><li><strong>Project close</strong><br>Key deliverable: A project retrospective and handover</li></ul><p>Using a combination of the above, along with other changes to roles and responsibilities and the way we estimate and plan (I will cover this in more detail in a future post), our delivery has now gone from a year later than planned in some cases, to pretty much on the day, give or take a few days (we are a software development company after all!). If there are delays, we are now able to foresee and prepare to mitigate them. Most importantly, we’re now at a point where we feel confident in our project plans, confident in our estimations and confident in delivering new builds.</p><h3><strong>Our Scrum Process</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NTj1B680-0qYoJ4EK3Ca8Q.jpeg" /><figcaption>Sprint planning</figcaption></figure><p><a href="https://www.scrum.org/resources/what-is-scrum">Scrum</a> has become a vital framework for software development teams and we are no exception. Similar to what we did with the PRINCE2 framework, we took the core <a href="https://www.visual-paradigm.com/scrum/what-are-scrum-events/">Scrum roles, rules, events and artefacts</a> and introduced those relevant to the development team. We successfully embedded the principles and the team responded well to the framework initially, but then developed a little resistance and some elements became a slog.</p><p>After spending some time analysing why, we made some useful changes. We reinvented the core sprint meetings (sprint planning, retrospective and stand ups being the main culprits), to make them more efficient and useful. We also created some ground rules for our sprints, for example we established which tickets get accepted into a sprint and which don’t.</p><p>Once we had made improvements, we added a small incentive to keep the team invested in the process so we could keep improving. If the teams complete 80–100% of work in a sprint, 3 sprints in a row, they get cake and beer. Some people say that the introduction of cake and beer had the biggest impact on the process, but I choose to ignore those people.</p><p>It became clear that there was an obvious need for a role to manage the ongoing improvement of our sprints, and keep them ‘alive’. We wanted it to be someone who already knew the team and the processes well, so we decided to combine the roles of Scrum Master and Project Manager into one. Both roles are traditionally focused on improving processes, leading successful delivery, and working with similar teams so it felt like the right move. The role was an experiment for us; we weren’t sure if the combined role would work or would result in one person doing the work of two people. But as a company who enjoys new challenges, we decided to give it a go!</p><h3><strong>Scrum Project Management</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fANUPJzbBs6l060_G4QwdA.jpeg" /><figcaption>Daily dev stand up</figcaption></figure><p>I started the new role of Scrum Project Manager with two core objectives in mind. I wanted to help our sprint teams consistently achieve 80% of their sprints, and I wanted to deliver our new build projects on time and with minimal stress to the team. Not only did the role help us towards both of those things, but it came with added, unplanned benefits:</p><ul><li><strong>Project plans have become a lot more accurate</strong><br>With a stronger knowledge about individuals, departments and how they work together, it became clear where to add contingency in timelines and how to accurately convert story point estimations to chunks of time, down to the individual developer.</li><li><strong>Common, recurrent dependencies are more familiar</strong><br>As well as helping with accurate planning, this has made highlighting, communicating and explaining dependencies internally and externally a lot easier.</li><li><strong>Project progress is more visible<br></strong>Being able to see tickets move through the sprint, and hearing about its progress during stand up means progress is easier to gauge. In combination with the ground rules we’ve implemented into the sprint, there is now clarity on how each piece of work is progressing, and what the hold up is if there is one. Having the visibility and knowledge of our sprint release processes also helps with planning client-facing releases and communicating any delays ahead of time.</li><li><strong>No more nagging!</strong><br>With the increased visibility, there’s less of a need to disturb team members about the progress of work. If a blocker is at risk of causing a delay to the plan, it’s visible right away and it’s easier to coordinate unblocking that piece of work without having to ask someone for the details. Delays and risks are much easier to foresee and mitigate in advance.</li><li><strong>Developers are more involved in project delivery</strong><br>Developers have context around why tickets are in sprints in a particular order and there’s more knowledge around dependencies of each piece of work. The timeline is put together with a lot of input from the team, meaning they have been a part of deciding their own deadlines. There is also plenty of opportunities to raise any concerns or questions about the project during the scrum meetings.</li><li><strong>Project plans get more investment internally</strong><br>The Scrum PM manages scoping, estimation, planning and delivery of the final product along with the developers, so they have that constant bridge to the project’s deadlines, goals and stakeholders. This means that communication becomes a lot smoother, and eventually this great communication has led to increased trust and buy-in from the team.</li><li><strong>Retrospective feedback influences project planning<br></strong>A lot of points (both positive and negative) arise at sprint retrospectives which have informed the way we plan and run projects. The Scrum PM gets an insight into what stresses out the team and can see if there are any persistent trends in feedback which relate to project process. The Scrum PM is able to action relevant feedback and make immediate, beneficial changes to the process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3aQNe9cSyNPT_TE9o39bWQ.gif" /><figcaption>One of our new build launches last year!</figcaption></figure><p>So far, these changes, along with introducing the Scrum Project Manager role, have made a positive impact to the overall delivery process. We sent out a survey and 100 percent of our dev team felt that the merging of roles had a positive impact to the scrum and delivery process. However, we still have plenty of improvements to make and it has become clear that we need more Scrum Project Management resource. As we get busier, the attention to the finer details is getting lost, and our scrum rituals are getting a little less love.</p><p>We now face decisions on how to hire for the next role in this team. Do we split it back into the traditional Scrum Master and Project Manager roles? If we do, do we lose a lot of the benefits we’ve gained from the combined role? Do we hire more Scrum PMs and how do they sit within the current structure of three sprint teams? Or do we take on scrum project administrators who can provide support to the processes and maintain the finer details? We’d love to hear your thoughts, let us know in the comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=362e150b9f2d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/15gifts-engineering/scrum-project-management-362e150b9f2d">Scrum Project Management</a> was originally published in <a href="https://medium.com/15gifts-engineering">15gifts Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Attending my first TestBash]]></title>
            <link>https://medium.com/15gifts-engineering/attending-my-first-testbash-1786caf40342?source=rss----9637e931be4a---4</link>
            <guid isPermaLink="false">https://medium.com/p/1786caf40342</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[testbash]]></category>
            <dc:creator><![CDATA[Jovita Griskenaite]]></dc:creator>
            <pubDate>Tue, 23 Jul 2019 12:24:55 GMT</pubDate>
            <atom:updated>2019-07-23T12:24:55.878Z</atom:updated>
            <content:encoded><![CDATA[<p>Early this spring I attended TestBash Brighton 2019 conference, organised by Ministry of Testing — a global software testing community. I knew about TestBash before I was offered my first position as a tester. So to me, it always seemed like ‘It would be the best thing in the world if I could participate in one’. My dream came true after I joined 15gifts. As if having tickets to the workshop and main talk day wasn’t enough, I was also offered a chance to volunteer on one of the other days! Needless to say, I was very excited.</p><p>Volunteering experience gave me an insider’s perspective. My main task was to meet and greet attendees, register them and give them the almighty goodie bag. I met the organisers and the whole bunch of other volunteers who were absolutely amazing individuals.</p><p>Seeing the inner cogs and gears of the event was great. After all, testers love knowing how things work!</p><p>The workshop was about how to improve feedback from automated tests, using approval testing. The technique seems valid, although test automation is new to me and the implementation of the technique might take a while. But I would be happy if I succeeded in implementing it.</p><p>All of the talks were great too. From topics such as pair testing, performance and security to machine learning and all the way to diversity and testing culture — they all had ideas worth noting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xFspUaj9BAstl2Eha63aig.jpeg" /><figcaption>Ash Coleman’s talk on Diversity thought me a way to re-evaluate the level of diversity in my closest environment</figcaption></figure><p>Also, the workshop and the main talk day provided me with lots of new ideas, basic or advanced understanding on various subjects, led me to conversations with testers from different backgrounds and even from different countries!</p><p>Someone at the conference gave me some advice: instead of burning out of motivation to complete 15 noted ideas from the conference, pick 1–2 and implement them 100%. So I’ve chosen to try pair testing session with another tester, who would have knowledge in a specific area and from which I could learn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sAmIuj3hT5RvYkM-rWX1JA.jpeg" /><figcaption><a href="https://twitter.com/lisihocke">L</a>isi Hocke telling her inspiring paired testing journey</figcaption></figure><p><strong>Some of my notes</strong></p><p><strong>Retrospective Prime directive </strong>— a reminder by Norm Kerth (<em>Project Retrospectives: A Handbook for Team Review</em>), to not to play the blame game</p><blockquote>“Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.”</blockquote><p><strong>Books, advised by other testers:</strong></p><ul><li><em>Power of the Habit</em>, by Charles Duhigg</li><li><em>Thinking, Fast and Slow</em>, by Daniel Kahneman</li><li><em>Influence: The Psychology of Persuasion</em>, by Robert Cialdini;</li></ul><p><strong>TestPhere </strong>—<strong> </strong>A deck of cards featuring testing concepts</p><p><em>Each card explains the concept with a slogan and three examples that were designed to have you think about them in different ways. Testers brainstorm, coach, share knowledge and experiences by using these cards.</em></p><p><strong>Better work-life balance tips</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bnvap1QGtvnsM8K7EoH7Ew.jpeg" /><figcaption>Attendees sharing their suggestions on better work-life balance</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1786caf40342" width="1" height="1" alt=""><hr><p><a href="https://medium.com/15gifts-engineering/attending-my-first-testbash-1786caf40342">Attending my first TestBash</a> was originally published in <a href="https://medium.com/15gifts-engineering">15gifts Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Placement Year at 15gifts]]></title>
            <link>https://medium.com/15gifts-engineering/my-placement-year-at-15gifts-2d5d80f10d98?source=rss----9637e931be4a---4</link>
            <guid isPermaLink="false">https://medium.com/p/2d5d80f10d98</guid>
            <category><![CDATA[placement]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Joshua Harrowell]]></dc:creator>
            <pubDate>Mon, 17 Sep 2018 10:23:48 GMT</pubDate>
            <atom:updated>2018-09-17T10:23:48.181Z</atom:updated>
            <content:encoded><![CDATA[<h4>After a brilliant 18 months, I thought it would be time to reflect on my experience at 15gifts as their first placement student.</h4><p>This month I’ll be heading back to the University of Brighton to the final year of my Computer Science degree.</p><p>I went into university with two years experience as an <strong>Apprentice Web</strong> <strong>Developer, </strong>whilst placements are great to see if this is the industry for you, I used my placement to see what area of software development I wanted to potentially specialise in, 15gifts gave me that opportunity and I’ve been able to work in both <strong>Front End </strong>and <strong>Back End</strong> development and both client facing and internal projects.</p><p>Rather than leaving after a year, I’ve offered the <strong>opportunity</strong> to complete my dissertation for the company and continue working in a part time capacity around my <strong>studies </strong>in addition to a clear path of <strong>progression</strong> for graduation and beyond with the company.</p><h3>More Than Just a Year on Your CV</h3><h3>Culture</h3><p>The company <strong>atmosphere</strong> is definitely one of the most attractive parts of the company and what has led to me having a <strong>great experience</strong>. I was invited to Friday drinks a few months before I was due to start which gave me a chance to meet everyone in a <strong>relaxed environment</strong>.</p><p>We have <strong>Food for Thought </strong>sessions where people will present internal or external topics over a <strong>free lunch</strong> ranging from story telling, how we present data and getting to know new team members.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mT7z2pIltmPsXbnO0jc4sg.jpeg" /><figcaption>Post victory after ‘chubby bunny’ — Musical Bingo @ Komedia</figcaption></figure><p>We also have quarterly reviews where we <strong>reflect</strong> on the quarter just gone and what our <strong>strategy</strong> is for the next 12 weeks, we then have a <strong>team bonding</strong> exercise like raft building, volleyball or bowling.</p><p>Everyone is really <strong>accessible</strong> and even as a placement student I’ve been able to get stuck right in with <strong>contributing</strong> to and developing <strong>critical</strong> <strong>systems</strong>, that faith on the employees really promotes a <strong>supportive environment</strong> that breeds personal growth.</p><p>Whilst I’m excited to go back to university, I’m definitely going to miss being in the <strong>office</strong> everyday, especially as we’re due to move into some pretty awesome new digs soon!</p><p>If you’re looking to join a <strong>growing</strong> company with a great <strong>product</strong> and <strong>culture</strong>, head over to our <a href="http://15gifts.com/join-the-team/">jobs page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d5d80f10d98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/15gifts-engineering/my-placement-year-at-15gifts-2d5d80f10d98">My Placement Year at 15gifts</a> was originally published in <a href="https://medium.com/15gifts-engineering">15gifts Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Successfully Implementing Clean & Functional Javascript]]></title>
            <link>https://medium.com/15gifts-engineering/successfully-implementing-clean-functional-javascript-377fed75f7b4?source=rss----9637e931be4a---4</link>
            <guid isPermaLink="false">https://medium.com/p/377fed75f7b4</guid>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[functional]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[James Fowler]]></dc:creator>
            <pubDate>Mon, 25 Jun 2018 13:23:50 GMT</pubDate>
            <atom:updated>2018-06-29T08:52:19.505Z</atom:updated>
            <content:encoded><![CDATA[<h4>An introduction to how we used clean and functional concepts to help build our new full-stack Javascript codebase at 15gifts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*PfaBsuBcwj3QQIpSvwIk1g.png" /></figure><p>For a while now we’ve been working on re-building our <strong>legacy back-end</strong> codebase at <a href="http://15gifts.com/">15gifts</a> <strong>from Perl into Node.js</strong>, and one of the main factors that we wanted to achieve when undertaking this challenge was <strong>code readability</strong> and <strong>code shareability,</strong> allowing our front-end team to be able to understand, modify and work with our back-end code base, and where possible, be able to <strong>use code either on the back-end or the front-end</strong> (Which we have now successfully achieved!). Here are some of the conventions that we decided upon, along with examples of how we achieved them:</p><ul><li>Well defined, clearly named files</li><li>Using variables and functions with meaningful names</li><li>Immutability, and reducing side-effects</li><li>Statelessness and pure functions</li><li>Composition over inheritance</li></ul><h3>Well defined, clearly named files</h3><p><strong>Small file sizes<br></strong>Small file sizes, optimally less than 100 lines, allow developers to quickly see the intention of a file and what it was designed to do at a glance. It also helps with solving diffs in merge conflicts.</p><p><strong>Naming files based on what they do<br></strong>Naming files explicitly by what they do helps developers to be able to see at a glance what their intention is. e.g <em>question-finder.js</em> is better than <em>question-logic.js</em>.</p><p><strong>Easy to locate in the file structure<br></strong>By naming files using a clear convention like this, it should be easy for anyone to find a certain file as they should all follow a similar format.</p><p><strong>Only one or two public functions in each file<br></strong>Inside the file, public functions should always be listed at the top, and there should only ever be one, or in some cases, two. Private functions should be listed underneath prefixed with an underscore.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/37d75157ca4f1a02a9025582913d358a/href">https://medium.com/media/37d75157ca4f1a02a9025582913d358a/href</a></iframe><h3>Using variables and functions with meaningful names</h3><p><strong>Variables<br></strong>Giving variables meaningful names helps developers to understand why they exist.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0de9c493608d779a188d56700e1aac55/href">https://medium.com/media/0de9c493608d779a188d56700e1aac55/href</a></iframe><p><strong>Functions<br></strong>Naming functions by what they do, in as much detail as possible, helps developers to understand why functions exist and what they have been built to do.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/873552cf10437143d67bd1e901378a86/href">https://medium.com/media/873552cf10437143d67bd1e901378a86/href</a></iframe><h3>Immutability, and reducing side-effects</h3><p><strong>Use const instead of var or let<br></strong>Using const guarantees that a variable’s binding cannot change after it has been set. Using const in a codebase also implies to developers that a variable’s value cannot change. If all developers working on a codebase are aware of this, then it makes it easier to modify code with confidence. <em>We do sometimes use let in our codebase, when we know that a variable may change. This is very rare though.</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1c8153c2664d26ee30ff7281c78ddfba/href">https://medium.com/media/1c8153c2664d26ee30ff7281c78ddfba/href</a></iframe><p><strong>Use filter, map and reduce over forEach</strong><br>Using filter, map and reduce instead of forEach makes it easier to ensure that a variable cannot change once it has been set.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7171a73fddbb0d0b3d78a8ce36a584fe/href">https://medium.com/media/7171a73fddbb0d0b3d78a8ce36a584fe/href</a></iframe><h3>Statelessness and pure functions</h3><p><strong>No global state<br></strong>By avoiding the use of global variables and ensuring that our local variables have the correct scope, we can be confident that they are only created and initialised when they are needed. This makes it clear to developers what the intention of a variable is, suggesting that it’s value cannot change.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d5bf00de613e3ad3f59a06ed493ec951/href">https://medium.com/media/d5bf00de613e3ad3f59a06ed493ec951/href</a></iframe><p><strong>Where possible, avoid calling out to the database or external services<br></strong>Pure functions which contain only logic and no calls to retrieve data from a database or external services are much easier to understand than functions which need to do this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ada1452aef5d80de1f0ae9094deced42/href">https://medium.com/media/ada1452aef5d80de1f0ae9094deced42/href</a></iframe><p><strong>Sharing pure functions with the front-end<br></strong>If a file only contains pure functions then we know that it can be shared with the front-end and it’s logic imported and used whether it is being run on the server or the client. This greatly helps with code re-use and speeding up development time.</p><h3>Composition over inheritance</h3><p><strong>No classes<br></strong>Not using classes means that functions can just be imported from files and called directly, rather than needing classes to be imported and instantiated. Instead of inheritance, common code can be separated into it’s own file and imported where it is needed.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8e60ffc39004723a856d503ff7c93121/href">https://medium.com/media/8e60ffc39004723a856d503ff7c93121/href</a></iframe><p><strong>Plugins<br></strong>Using a plugin based architecture means that code can be dynamically injected at runtime, depending on certain parameters. This helps us to share our codebase between different clients and channels with relative ease.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ac161ae6fc163c7085d5586628690772/href">https://medium.com/media/ac161ae6fc163c7085d5586628690772/href</a></iframe><h3>Summary</h3><p>This article showed an overview of some of the conventions we have chosen to use to successfully produce readable code in our full-stack javascript codebase. This has helped us to develop our code more quickly, maintain it more easily, and share a lot of our code between the back-end and the front-end.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=377fed75f7b4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/15gifts-engineering/successfully-implementing-clean-functional-javascript-377fed75f7b4">Successfully Implementing Clean &amp; Functional Javascript</a> was originally published in <a href="https://medium.com/15gifts-engineering">15gifts Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>