<?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 Pierre Renaudin on Medium]]></title>
        <description><![CDATA[Stories by Pierre Renaudin on Medium]]></description>
        <link>https://medium.com/@pierrerenaudin?source=rss-5481a400a4e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Aij990dnyx1shBWC.jpeg</url>
            <title>Stories by Pierre Renaudin on Medium</title>
            <link>https://medium.com/@pierrerenaudin?source=rss-5481a400a4e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:36:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pierrerenaudin/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[5 things we’re keeping in mind working in squads]]></title>
            <link>https://medium.com/slite/5-things-were-keeping-in-mind-working-in-squads-3fdbb116a1a9?source=rss-5481a400a4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fdbb116a1a9</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[squad]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Pierre Renaudin]]></dc:creator>
            <pubDate>Thu, 08 Nov 2018 15:08:29 GMT</pubDate>
            <atom:updated>2019-05-14T09:20:44.812Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zb_eV_9AwNh2fuc7CylDoQ.jpeg" /><figcaption>Slite team — October 2018</figcaption></figure><p>How many times have you iterated on your work organization? At <a href="https://slite.com/">Slite</a>, here’s our brief history:</p><ul><li>From 0–6 people we worked in 1-week sprints</li><li>From 6–10 we worked in <a href="https://blog.trello.com/how-to-accelerate-a-startup-with-team-culture">2-week sprints</a></li><li>From 10–14 we started working in 2-week squads made up of engineers and product designers</li><li>From 14-🤷 we’re now working in 5-week squad cycles, inspired by <a href="https://m.signalvnoise.com/how-we-set-up-our-work-cbce3d3d9cae">Basecamp’s model</a></li></ul><p>What first triggered us to work in squads? Our second product designer, Rob, and two developers, Charley and Guillaume, joined us. If you’re also a growing team, you know the dilemma: more manpower, more dysfunctions. To list a few: flawed decision-making processes, a top-down approach to building the product, not enough or irrelevant feedback.</p><p>So, we decided to work in 3–4 people squads of 5 weeks to:</p><ul><li>Give everyone more responsibility: each squad makes and drives product decisions. Improve our decision-making process: squads make calls and follow through with them</li><li>And plenty of other reasons we’ll happily share in a later article :)</li></ul><p>That was 5 weeks ago so we’re currently nearing the end of our first squad cycle. It got us thinking about the five foundations of teamwork: how have we applied them in this cycle? Where can we improve? Here are some thoughts 🤓</p><h3>#1: Trust</h3><p>Shopify CEO, Tobias Lütke, introduced the idea of “the trust battery”, also mentioned in Basecamp’s book, Calm. It’s the idea that at any point in a team, people’s trust batteries are more or less charged. In our case, at the beginning of each cycle, each squad member’s trust battery is half-charged. Unintuitive techniques charge it: be vulnerable and speak the truth when things aren’t working as expected; ask for clarifications for vague specs or unknown states of development; do regular check-ups within squads synchronously or asynchronously.</p><p>One of the squads’ goals was to release the mobile app but the timeline was tight. Thanks to honest communication and trust, all the squad members dropped what they were doing to help release the mobile app on time. At the end of a squad cycle, trust batteries should be charged 100%.</p><h3>#2: Feedback</h3><p>Feedback should be delivered directly, punctually and honestly. It should also be given by a limited group of people. It’s counter-intuitive but the more people give feedback, the less productive it becomes. Squads reduce the feedback loop, encouraging rapid prototyping and quick product iterations. In this way, feedback can be given along the way and mistakes can be diluted and less hard to admit.</p><p>Squad members aren’t just accountable for delivering features and feedback shouldn’t be limited to the product. Team members can help each other grow through 1:1s and honest communication (which relates back to Trust 👆).</p><p>When received, feedback is a powerful tool for improving ourselves and our work.</p><h3>#3: Commitment</h3><p>1/ Each person is dedicated to a squad, and committed to it by default. The squad’s flow is dependent on this commitment. For example, I was part of the squad working on our editor but I’m also in the middle of hiring for two positions. The flow broke because I was half in, half out. We should stay within our squads, remain focused on our squad goals, and help members if they’re stuck — right until the end of cycle.</p><p>2/ As Jeff Bezos said: “Learn to disagree and commit”. When things aren’t moving forward because of a disagreement, trust the person in charge (for example: the product designer). Express disagreement constructively, and then move on by committing to the squad’s decision.</p><h3>#4: High standards</h3><p>Having high standards is different to asking for perfection. A good way to achieve high standards is by making things that are simple, well designed and well thought out. Remove the clunky parts. Get rid of options. Focus on doing excellent work.</p><p>The size of squads make this possible. Everyone is responsible for the quality of a feature. All members are encouraged to speak out: developers can review designs, designers can challenge marketing decisions, product can question tech decisions. It becomes easier for everyone to set new standards</p><h3>#5: Results</h3><p>Attention to results is the most important part of squads. If goals can be reached early in the cycle, why not release that small improvement sooner rather than later? Is there a shortcut we can take now, and pay back later because a Cycle lasts for a whole 5 weeks?</p><p>Reporting these results encourages everyone to stay in line: squads send status updates to the entire team 3 times a week. For the next cycle, we’re going to put in place mid-term cycle reviews to realign and refine goals.</p><h3>Let’s focus on squad foundation for better team foundations</h3><p>These 5 foundations are widely known and almost obvious. It’s one thing to implement them in a small, five-person team. It’s a whole other story when your team grows. They become a little bit more complex to work on as each new employee joins the team, it can be disorienting.</p><p>In the last 5 weeks, we’ve found it more productive to work on these principles at the squad-level. The good news is that we’ve seen it affect the team as a whole.</p><p>Thanks for reading! Are you working in squads? What are your squad foundations? We’re curious!</p><p>‍</p><p><em>Originally published at </em><a href="https://slite.com/blog/post/team-foundations"><em>slite.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fdbb116a1a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slite/5-things-were-keeping-in-mind-working-in-squads-3fdbb116a1a9">5 things we’re keeping in mind working in squads</a> was originally published in <a href="https://medium.com/slite">Slite</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we’re building our remote culture as we build Slite]]></title>
            <link>https://medium.com/slite/how-were-building-our-remote-culture-as-we-build-slite-2b7a8365268?source=rss-5481a400a4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b7a8365268</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Pierre Renaudin]]></dc:creator>
            <pubDate>Tue, 12 Jun 2018 08:29:32 GMT</pubDate>
            <atom:updated>2019-05-14T09:21:32.431Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CXiJXQEC3gQkQRFcEEv6-g.jpeg" /></figure><p><em>This post was originally published on the </em><a href="https://blog.slite.com/post/how-were-building-our-remote-culture-as-we-build-slite"><em>Slite blog</em></a><em>.</em></p><p>I recently attended a meetup of CTOs of small and larger startups. When asked about our biggest challenge, we were all aligned: hiring the right people. Then, when asked about remote work, I was the only one open to building a distributed team.</p><p>At first, I couldn’t reconcile the fact that one of our biggest challenges as CTOs is recruiting and yet I was the only one open to hiring remote developers. Then, I started to get why:</p><ul><li>Even in the tech sector, prone to be open to new modes of management, hiring remote employees remains daunting for many reasons.</li><li>There’s a lot that’s been written about working as a distributed team but very little that’s been said about building one: hiring the right people, onboarding them the right way and figuring out your balance as a team.</li><li>Bottom line, when you’re the CTO of a &lt; 10 people startup, it’s tough to find tangible advice on where and how to start on this subject.</li></ul><p>At <a href="http://www.slite.com/">Slite</a>, we’re still figuring it out but hope our short experience of building a distributed team can provide some concrete tips and at least encourage people to ask themselves the right questions around this topic.</p><h3>Taking the leap: to remote or not to be?</h3><p>When we started out, Chris and I were in different cities for the first few months. By the time we started working in the same offices, we hired a third team member, Arnaud, our first full-remote developer. What it proved was that you don’t need to be physically together to innovate, work efficiently, and build team culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*54hSwaXsYpnOfn4Y.JPG" /></figure><p>But it’s not so obvious: launching a startup means having to think of 10000 things at the same time. Managing a distributed team feels like adding on top of that list. Starting out distributed meant that we naturally grew open to the idea of remote. It’s a mindset you must choose to have from the very beginning because it influences your entire team culture.</p><p>1.5 years into this venture, we’re a team of 9, of which 5 developers across three continents, and happy to share what we’re learning and asking ourselves daily about hiring remote, onboarding, and day to day teamwork as a distributed team. While this article is specifically about our experience hiring and working remote developers, they apply for all positions.</p><h3>Hiring: self-management, communication, and reporting skills are as important as technical skills</h3><p>We’ve learned that hiring remote requires a specific framework if it’s going to work long-term. Above all, we’re very transparent about expecting a specific work ethic and management, on top of technical skills, from the developers we hire in remote:</p><ul><li><strong>On point self-management</strong>: they basically need to micro-manage themselves.</li><li><strong>Excellent reporting skills</strong>: they must be prepared to show how well they micro-manage themselves and clearly report on tasks to establish trust.</li><li><strong>They must be experienced developers</strong>: the autonomy that comes with expertise is crucial for the first points to be true.</li><li><strong>They must have experienced remote</strong> before even if shortly or punctually: our second full-time remote developer, Alex, had been remote for one month in his previous job, enjoyed it and started actively looking for the opportunity to be remote full-time.</li><li><strong>It must be clearly stated in their contracts</strong>: to avoid miscommunication with other team members, we’ve always made sure there are specific clauses in remote contracts.</li></ul><h3>Onboarding: get new hires on board quickly to make them feel part of the product team</h3><p>Onboarding a new hire is hard so imagine when it’s someone you’ll be seeing more virtually than physically. The importance of making someone feel they have their to part to play in the product and team as quickly as possible is tripled. Here are some of the things we’ve progressively implemented in our onboarding process:</p><ul><li><strong>Avoid the “Full Stack Developer” myth</strong>: even as a small team, ensure everyone on your tech team has a specific role and that you hire for specific roles. It makes it easier to divide tasks and spread product ownership when someone new joins the team.</li><li><strong>Work in the same offices in the first week as if you’re working distributed</strong>: it makes it easier to set everything up and work out the first kinks.</li><li><strong>“First day = first code deployed” policy</strong>: every new hire deploys their first code on their first day at Slite. It creates an immediate feeling of autonomy.</li><li><strong>See each other regularly</strong>: the frequency depends on how far the team member is but we make sure they come to the Slite HQ at least once every two months.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DMolZbgxpjXvtZid.jpg" /></figure><h3>Management: solving organizational issues early on versus reacting to what happens at the office</h3><p>Finally, the day-to-day management: the part where most fears about remote teams stem. How do you trust your employees? How do you ensure goals are hit? How do you make sure there’s team cohesion?</p><p>Often, we’ve found these fears can be turned into opportunities that’ll benefit your team in the long run:</p><ul><li>Building team cohesion: as I mentioned earlier, employees need to feel they have their role to play in the team. <strong>Deciding to build a distributed team forces everyone to define their role and their scope of work.</strong></li><li>Reaching goals: a lot of times in startups, goals are unclear, unplanned and unreached. Overlaps and inefficiencies are more likely if your team isn’t together physically. <strong>Those risks force you to evaluate frequent goals (bi-weekly for us), write up short and long-term roadmaps.</strong></li><li>Efficient communication: cohesive teamwork in a distributed team depends on clear reporting and respecting each other’s focus. <strong>Nailing communication etiquette early on is a strength for the employee (learning the art of good reporting) and for the manager (avoiding micro-management).</strong></li><li>Ensuring your team members are growing and feeling fulfilled in their work: when you’re in the same office it’s easier to avoid having one-on-one conversations to address feelings of stress or unhappiness at work. If they’re far, those feelings will be exacerbated and you’ll risk losing some of your best talents. <strong>We hold regular one-on-ones every three weeks with remote and non-remote team members to talk about things that are not working and those that are.</strong></li><li>Creating a unique team culture: work is a huge part of social life and being in an office is full of social events from the coffee machine to lunches to after work drinks. It can feel isolating for those who are not there. We tried having an appear.in social room and using House Party to fill that distance but it hasn’t worked for us. <strong>What has worked is starting the day with a stand-up meeting: it can vary from taking 10 minutes to taking 30 minutes. T</strong>he idea is to report, talk about work issues, socialize and start off the day as a team. Slack also helps in small but meaningful ways: our #random channel is often most animated by the remote team members who share interesting and funny articles.</li></ul><h3>Go for it</h3><p>When I said earlier that choosing to build a distributed team will impact all your future organizational decisions, I wasn’t exaggerating. Our work rhythm and etiquette (few meetings, respect of each other’s focus, efficient 1–1 meetings, smart reporting…) derive from reflecting on “how do we make this distributed team thing work?”. So far, they’ve had amazing benefits on the entire team: remote and not.</p><p>I’ll leave you off with the acknowledgment that it’s definitely a leap of faith and requires you allocate time to reflect on issues that might not get you as excited as building your next cool feature. Still, I encourage you to take that leap: you’ll hire the best talent and you’ll fix important issues early on.</p><p><em>This post was originally published on the </em><a href="https://slite.com/blog/post/how-were-building-our-remote-culture-as-we-build-slite"><em>Slite blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b7a8365268" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slite/how-were-building-our-remote-culture-as-we-build-slite-2b7a8365268">How we’re building our remote culture as we build Slite</a> was originally published in <a href="https://medium.com/slite">Slite</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to grow with Firebase (and survive)?]]></title>
            <link>https://medium.com/slite/how-to-grow-with-firebase-and-survive-881397652f93?source=rss-5481a400a4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/881397652f93</guid>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[graphql]]></category>
            <dc:creator><![CDATA[Pierre Renaudin]]></dc:creator>
            <pubDate>Tue, 27 Jun 2017 15:49:10 GMT</pubDate>
            <atom:updated>2017-06-28T15:17:12.247Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uuCJlsy-XhCCPDXgvPJJHQ.png" /></figure><p>Over the years, I’ve developed something of a love/hate relationship with Firebase.</p><p>Sure, Firebase makes crafting new products and ideas a whole lot simpler. But it quickly becomes a burden…</p><p>At Slite, we decided to consider Firebase for what it is: an asset. Firebase gave us the ability to build a kick-ass product in under 10 months and to have it tested and used by 500 people — which would have been unthinkable 3 years ago.</p><p>And yet, planning for the transition from Day-1 is key to making the most out of Firebase. Knowing the limitations and preparing for the migration is pretty straightforward: you just have to stay rigorous, and do each step one at a time.</p><p>Firebase offers a full set of services, which aren’t free, but will save you a LOT of time:</p><ul><li>Hosting</li><li>Asset</li><li>Security</li><li>Database</li><li>Realtime updates</li><li>Offline resync upon reconnection</li><li>File storage</li><li>Authentication</li><li>Third-party authentication providers</li><li>Backups…</li></ul><p><em>I assure you that, when you don’t have all of that to deal with, you’ll have a much clearer mind to focus on the tech bits that really matter. To us, that was building a rich collaborative editor. 🛠</em></p><h3>How to initiate the move away from Firebase?</h3><p>The first thing to do is to replace the services you won’t be able to migrate later. Hosting or authentication are so tied up with Firebase that you need to migrate them right away. Just keep the realtime updates and database in Firebase, the rest should belong to you.</p><ul><li><strong>Hosting:</strong> We set up everything on Docker and hosted the service on App Engine.</li><li><strong>API:</strong> We started a small Node.js service to kickoff our API.</li><li><strong>Authentication:</strong> Thanks to our new API, we were able to generate JWT tokens for each user: one for our API and another for Firebase’s legacies.</li><li><strong>Database:</strong> We set up a Postgres to store users/organizations and invites which were in the first migration batch.</li></ul><p>And then you have to get your hands dirty: with your API in place, you can run a migration from Firebase back to your database, to ensure that all your data remains synchronized. Basically, we used Firebase as a “slave” to our new database. 🤠</p><blockquote>Choose to own your data</blockquote><p>We use Firebase REST API ( especially the <a href="https://firebase.google.com/docs/database/rest/retrieve-data#shallow">shallow query</a> only available with REST) to list objects and migrate them one at a time. Once the migration is performed, users will consume our fresh API and mutate objects in our database. We then keep them up to date by syncing back to Firebase.</p><p><em>Example migration snippet:</em></p><p><a href="https://gist.github.com/prenaudin/45d34a4df5a310cea93af39f1cfc163b">https://gist.github.com/prenaudin/45d34a4df5a310cea93af39f1cfc163b</a></p><h3>Keep growing / keep migrating</h3><p>At Slite, we’re bringing the future of knowledge to teams. Our core feature is a real-time collaborative editor. Its synchronization and storage were still on Firebase. It was inspired by <a href="https://firepad.io/">Firepad</a> in its design, but when we reached 50 users, we were stuck: 1GB database, without any possibility to restore a backup. In order to sync rich-text documents with operational transformation, you have to store each operation that occurred on the document.</p><p>As we had already started our hosting migration, we set up a new collaboration system based on ShareDB. Thanks to our Kubernetes and micro-services environment, we had the ability to host it pretty quickly.</p><p>Alongside, we migrated our search from a client-based custom solution to Algolia, with a hook on Firebase to sync on all object changes.</p><blockquote>Use the right service for the right job</blockquote><p>At this point, where are we?</p><p>✅ Hosting is provided by Google Cloud Platform with Kubernetes.</p><p>✅ Querying and mutating data is partially done via our Node.js API.</p><p>✅ Our collaboration system is hosted as a micro-service in Kubernetes.</p><p>✅ We own authentication by generating JWT for our API and Firebase.</p><p>✅ We tested our ability to migrate objects from Firebase to our database.</p><p>❌ Most of our business data still remains in Firebase.</p><p>❌ We are yet to set up a real-time system to publish updates to users.</p><h3>Finishing the clean up</h3><p>Now it’s time to finish the migration. We are currently developing our API with GraphQL and Node.js and are taking advantage of the fresh subscriptions system released recently (Kudos to the Apollo and GraphQL teams).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/0*qArN7qVgJhTWEhzo." /><figcaption><em>Actual migration schema with both system, GraphQL and Firebase</em></figcaption></figure><blockquote>Bootstrapping our fresh new API with GraphQL brought us great velocity and documentation<em>.</em></blockquote><p>From day one, we separated concerns by having the least amount of Express controllers possible and separated functions to query or mutate data (by doing permissions verifications, database queries…). Setting a new way to expose endpoints with GraphQL was easy and we can still support our REST API. The flexibility provided gave us confidence as we moved towards our future challenges (mobile and external integrations).</p><h3>Takeaways</h3><p>Here is some advice if you have to tackle such a transition:</p><p>🚦Define a roadmap with clear steps to ensure the migration suite.</p><p>👋 Ask for help and read a lot to be confident in your choices.</p><p>🛠 Don’t hesitate to build a POC (proof of concept) if you are not sure about a choice.</p><p>📊 Keep a spreadsheet with the migration status of all the mutations, queries and objects.</p><p>✨ Enjoy every step, it’s hard and painful but it can be vital for your business.</p><p><em>This story was made possible by the entire Slite team</em> (<a href="https://medium.com/@arnaudrinquin"><em>Arnaud Rinquin</em></a><em>,</em> <a href="https://medium.com/@christophepas"><em>Christophe Pasquier</em></a> <em>and</em> <a href="https://medium.com/@Brieuc1"><em>Brieuc Sebillotte</em></a><em>). If you fancy testing Slite, be sure to register at</em> <a href="https://slite.com/"><em>https://slite.com</em></a><em>.</em> And if you want to join the team building the future of collaboration, drop us a line at chris(at)slite(dot)com.</p><p><em>Thanks folks ✨ 👋 don’t forget to recommend the article if you liked it</em>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=881397652f93" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slite/how-to-grow-with-firebase-and-survive-881397652f93">How to grow with Firebase (and survive)?</a> was originally published in <a href="https://medium.com/slite">Slite</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech tips when starting a startup project]]></title>
            <link>https://medium.com/azendoo-team/tech-tips-when-starting-a-startup-project-ed5e5b650a62?source=rss-5481a400a4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed5e5b650a62</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Pierre Renaudin]]></dc:creator>
            <pubDate>Tue, 27 Sep 2016 12:23:52 GMT</pubDate>
            <atom:updated>2016-09-27T13:37:07.133Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*jApryltzBts86GSeAPCpQw@2x.png" /></figure><p>I started as a young developer at <a href="https://azendoo.com/">Azendoo</a>, a French startup located in sunny Bordeaux, about 5 years ago. At that time, I was fresh out of engineering school and had just started as a front-end developer at Azendoo. After two years on the same project, and dozens of new or abandoned features, the team was struggling with the lack of consistency in our code and process 🙊</p><blockquote>It’s one thing to code, it’s another to take a step back and try to improve how we are organized with regard to our code.</blockquote><p>In the past year, we have focused on improving our speed on feature release, whilst ensuring that our releases had as few regressions as possible. Here is some advice I would have liked to have received when we were starting out. 😊</p><h4>1. Apply solid and simple Git conventions</h4><p>As your team grows, you need to clarify how to organize your repository, name branches and write commits. Instead of trying to build a custom process, pick an existing convention.</p><ul><li><a href="http://nvie.com/posts/a-successful-git-branching-model/"><strong>Git Flow</strong></a> for our branching model and release organization.</li><li><a href="https://github.com/commitizen/cz-cli"><strong>Git Commitizen</strong></a> for commit conventions.</li><li><strong>Azbot</strong>, a homemade CLI (Command Line Interface), to release to staging or production ( we’re working hard to replace it with Docker 💪🏻 ).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*Mnvr5Yz5cRLMBZUcR7UeYg.png" /></figure><h4>2. Use tests and a CI (Continuous Integration) as early as possible</h4><p>You should write tests as soon as you start writing code. Even if you think that this small piece of code is going to be improved upon in the near future… Guess what? It won’t be. And that’s for sure. Writing high quality code won’t guarantee that it won’t break. It will do — and harder than you think.</p><p>To start with, write unit tests on your API and front-end, even if it’s just simple tests so as to reduce regressions in the future. You’ll feel a lot more confident. Then, right after that, add a continuous integration.</p><ul><li><strong>Use tests</strong> to reduce regressions and write high-quality code.</li><li><strong>Use CI</strong> to ensure that each new piece of code change doesn’t break the existing code.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*iqWtlSODgeScbosaoLUvRg.png" /></figure><h4>3. Learn to review code</h4><p>To ensure code quality and consistency, the best approach is to have e-v-e-r-y pull-request reviewed by one or two teammates. This will have a great impact, without requiring a lot of setup effort.</p><ul><li><strong>Consistency</strong>: by reading each other’s code, everyone will learn and teach the best patterns.</li><li><strong>Quality</strong>: by reviewing code, the team ensures that the code base is readable and clear.</li><li><strong>Pedagogy</strong>: new teammates or interns we will learn faster and have thoughtful discussion around code, not dogmas.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*Za8RSVhIkgscjXu7WMPVgw.png" /></figure><h4>4. Be a better developer by linting your code</h4><p>Setting code conventions is hard. Having to force every member of your team to follow them is even harder. That’s why using Linters with code conventions written by others is an easier approach. The whole team has to accept the conventions first, and then they just follow the rules. No more debates about the dangle comma, or spaces vs. tabs. 😊</p><p>We are using multiple tools to ensure our code grammar:</p><ul><li><a href="https://houndci.com/"><strong>Hound</strong></a>: a great online service wich reviews every pull-request on GitHub;</li><li><a href="http://eslint.org/"><strong>Eslint</strong></a>: library to lint our JavaScript and React.js code (we follow Airbnb’s conventions);</li><li><a href="http://editorconfig.org/"><strong>Editorconfig file</strong></a>: add an .editorconfig file to ensure indentation and last-line rule across your team.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dsRawtvk8zs3R_c-_cSCyQ.png" /></figure><h4>5. Use a project management tool</h4><p>This piece of advice might seem dead simple, but trust me when I say that many young companies forget to organize precisely their development. Having to write and organize tasks as a team gives you a lot of advantages:</p><ul><li>Each member in the team can see who is working on what;</li><li>You easily communicate with the rest of the team and set deadlines;</li><li>Prioritizing makes you more efficient and avoids not-so-useful stories.</li></ul><p>For all our development, we use Azendoo to schedule and assign tasks. In a subject called “Development”, we have four sections: Next, Code &amp; Test, QA &amp; Review and Feature Flag (available only for Beta users). Every new feature, polish and sometimes bugs will follow this process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*0qwDQn72DUNpnQl6R0mdjw.png" /></figure><p>To sum it up, here is a to-do list:</p><pre>- [ ] Use a version control hosted service (Github, Gitlab etc.)<br>- [ ] Run continuously your tests in a CI (Codeship, Gitlab etc.)<br>- [ ] Set up a lint config<br>- [ ] Set up an editor config<br>- [ ] Set up a Git commit messages and branches convention<br>- [ ] Review every pull-request by one or two teammates<br>- [ ] Deploy your app ( or service ) with a one line command<br>- [ ] Organize development around a clear to-do list</pre><p>Hope you liked these simple and basic tips. Don’t hesitate to recommend 💙 or share✌️.</p><p>Kudos to <a href="https://twitter.com/emilyfiennes">Emily Fiennes</a> for reviewing this article 😘</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed5e5b650a62" width="1" height="1" alt=""><hr><p><a href="https://medium.com/azendoo-team/tech-tips-when-starting-a-startup-project-ed5e5b650a62">Tech tips when starting a startup project</a> was originally published in <a href="https://medium.com/azendoo-team">Azendoo Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to use Immutable.js Records with React and Redux]]></title>
            <link>https://medium.com/azendoo-team/immutable-record-react-redux-99f389ed676?source=rss-5481a400a4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/99f389ed676</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Pierre Renaudin]]></dc:creator>
            <pubDate>Wed, 08 Jun 2016 07:08:12 GMT</pubDate>
            <atom:updated>2016-06-08T12:59:48.052Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s the small things that change your product. <a href="https://facebook.github.io/react/">React</a> and <a href="https://facebook.github.io/flux/">Flux</a> can be small things, but using them has changed our product like we could never imagined.</p><p>As we continue to improve our app, we struggled with the lack of consistency in our models, even if they were immutable. They were generic types (i.e. Map, Array), so we couldn’t precisely validated propTypes given to our components. 🌀</p><p>As <a href="https://facebook.github.io/immutable-js/">Immutable.js</a> was already in our project, we thought we could take advantage of the <strong>Immutable.Record</strong> to build our models to:</p><ul><li>export a clear type for each model;</li><li>define model attributes;</li><li>expose getters if needed.</li></ul><p>So, we can start be defining our first model, a <strong>Task </strong>record with default value and getters:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c1c897db37eb3d428bcd40c1d78adc47/href">https://medium.com/media/c1c897db37eb3d428bcd40c1d78adc47/href</a></iframe><p>Alongside this model representing a unique task, we define another record to represent tasks list, <strong>TaskMap</strong>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1b62bc94a90292ea7e1a7ecc39bf2729/href">https://medium.com/media/1b62bc94a90292ea7e1a7ecc39bf2729/href</a></iframe><p>We could now make the most of these two records and refactor our Redux Reducer to ensure that our store state is a <strong>TaskMap</strong> with only <strong>Task</strong> records as values ( keys are <strong>Task</strong> ids):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ee25db40c7056953713e5617073b5743/href">https://medium.com/media/ee25db40c7056953713e5617073b5743/href</a></iframe><p>Finally, we can create a container to present our data and connect it to our application state. We import the <strong>TaskMap model </strong>to validate our props:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fee39492e7c42cdbe665a9a82c739f40/href">https://medium.com/media/fee39492e7c42cdbe665a9a82c739f40/href</a></iframe><p>And we do the same in our <strong>TaskListItem </strong>children to ensure that this component receives a <strong>Task</strong> model:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bfb2a3d58472a7de21b6dca0f4a545e7/href">https://medium.com/media/bfb2a3d58472a7de21b6dca0f4a545e7/href</a></iframe><p>Now, if we mess up with the <strong>TaskListItem</strong> component, a clear message will pop up in our console. 👀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*gvnLrpfXdeoBVcPLHgDb7g.png" /><figcaption>Chrome console output if an invalid propType is given to our component</figcaption></figure><p>The message is clear enough to focus our attention on the wrong type given in the component container: it increases the component reusability and gives direct feedback if something in our app state is wrong. 👌</p><p>That’s all folks :) Easy to setup, great to use. We now have a consistent model representation for our data. Plus, the records are extendable and we can define on them… testing and debugging is easier now \o/ Next step could be defining types with Flow or Typescript… See you later!</p><p><em>Credit to </em><a href="https://github.com/facebook/draft-js"><em>Draft.js</em></a><em>, a project maintained by Facebook, and from where great ideas can be taken about Immutable data structure, tests, code clarity…</em></p><p><em>Leave email, sticky notes behind. Start tracking your work with your team, clients and partners in Azendoo (</em><a href="https://www.azendoo.com/"><em>https://www.azendoo.com</em></a><em>).</em></p><p>Kudos to <a href="https://twitter.com/AntoineHanriat">Antoine Hanriat</a> and <a href="https://twitter.com/emilyfiennes">Emily Fiennes</a> for reviewing this article 😘</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99f389ed676" width="1" height="1" alt=""><hr><p><a href="https://medium.com/azendoo-team/immutable-record-react-redux-99f389ed676">How to use Immutable.js Records with React and Redux</a> was originally published in <a href="https://medium.com/azendoo-team">Azendoo Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>