<?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 miki lior on Medium]]></title>
        <description><![CDATA[Stories by miki lior on Medium]]></description>
        <link>https://medium.com/@mikilior?source=rss-d022ff4794aa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*49m56qNOUur2PQFFqnpPEQ.jpeg</url>
            <title>Stories by miki lior on Medium</title>
            <link>https://medium.com/@mikilior?source=rss-d022ff4794aa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:27:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mikilior/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[Full-stack: fiction or real?]]></title>
            <link>https://medium.com/ironsource-tech-blog/full-stack-fiction-or-real-90a51530d4bc?source=rss-d022ff4794aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/90a51530d4bc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ironsource]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[miki lior]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 08:56:48 GMT</pubDate>
            <atom:updated>2022-01-13T15:44:28.262Z</atom:updated>
            <content:encoded><![CDATA[<h3>Full-stack: fiction or fact?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*ZMtywyUMQVR5MZw9UI8gTg.png" /></figure><p>Let’s start with the bottom line — Yes, there are real full-stack engineers out there with the capabilities to handle challenges both from server-side and from the client-side. But (and it’s a big but…) finding a true full-stack engineer who can handle both sorts of challenges is so hard that some refer to them as unicorns.</p><p>One of the most important roles as an engineering leader is the ability to scale and build your team fast. Building such a team can be a hard task when trying to find rare unicorns (ask any recruiter you know).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M6FQnnj7efJjF6bl-Kyf3A.jpeg" /></figure><p>But wait…. Why do I need my team to be a full-stack team? If those full-stack guys are so hard to find, why should I insist on building these cross-functional teams? And what is, in fact, a full-stack developer?</p><p>One of my favorite resources for backing a statement is<a href="https://www.quora.com/"> Quora</a> and one of the most popular discussions on<a href="https://www.quora.com/What-does-the-term-full-stack-programmer-mean-What-are-the-defining-traits-of-a-full-stack-programmer"> what are the traits of full-stack developer</a> quotes a never-ending list of technologies and frameworks you need to master to qualify as a true full-stack developer.</p><p>But technologies and frameworks are ever changing, especially in the world of web development. I remember a time in which to be a true full-stack developer all you needed to know was C# and a bit (and no more than a bit) of applicative database administration. By that — you could control all 3-tiers and the SOA world. Full-stack developers existed long before the term was coined, so I prefer a more generic definition: a full-stack developer is a developer who masters or at least controls a variety of skills that can be used to independently develop features or products that are mostly distributed in nature (meaning they have both frontend and backend components)</p><p>Now that we all agree on what this “unicorn” is — why do we need it? Why can’t we just settle for a backend developer (or a backend team) working with a frontend developer to bring a product to fruition?</p><p>After several years of building such teams, I’ve noticed multiple advantages to preferring full-stack developers over the classic backend/frontend teams.</p><p><strong>Reducing bottlenecks</strong></p><p>As developers, one of our primary objectives is to deliver fast and high quality products. This is why the agile methodology was evolved — the ability to respond and respond fast, and you need to build your team so it responds quickly to the product team’s needs. When building a team of engineers, you should measure efficiency by employing KPIs.</p><p><strong>Cycle time</strong> , which is defined as the amount of time needed for a feature to be shipped and provide customer value, is a favorite of mine. Let’s not argue about when cycle time starts and when it ends, and agree that measuring cycle time forces us to address features in small batches and address <strong>capacity bottlenecks</strong>.</p><p>Our world of web development can be chaotic at times. In a specialization focused team (backend/front/QA team), or even specialization focused engineers in the same team, focus can change from backend requirements (“Hey, I’ve got demand from customer X to change API Y”) to frontend requirements (“API Y works great! Why don’t we build a dashboard?”) very quickly.</p><p>Not only do you need to plan the product roadmap according to your team’s specialization, but you also need to sync it with your recruitment plan (and probably more often than you would want to).</p><p>If you’re getting stuck at bottlenecks, it means your team structure isn’t scalable, which is a problem that can be solved by minimizing specialization and using resources that won’t limit capacity — AKA full-stack engineers.</p><p><strong>Reducing relays in the relay race</strong></p><p>Bringing business value as an engineering team is very much like a relay race. Taking a feature from an idea until the finish line (someone is using my feature! Yay!) is usually a team effort that involves product owners, developers, QA, DevOps and more.</p><p>This race needs to be synced and to do that, we use different practices. First, there are practices that include the agile methodology ceremonies like dailies, planning and retrospective which their main goal is to keep everyone synced. Second are technical practices like code reviews, tooling (version and test management system). Last but not least, there are cultural practices like recruiting engineers without egos and with the ability to collaborate, transfer knowledge and more. Each of these practices are meant to minimize syncing and handover activities — otherwise, a lot of effort is invested in managing and timing them.</p><p>But wouldn’t it be easier to reduce the number of relays in the race? A full-stack engineer can transform a relay race into a single race with no management effort. It’s the dream of every leader, a team member with all the abilities to take on full ownership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*pfrF3wLFawWZyytl0HUJ3Q.jpeg" /><figcaption>Sample of relay race done perfectly</figcaption></figure><p><strong>Why not go for it?</strong></p><p>It looks like any leader’s dream — to create an autonomous, bottleneckless (is that a word?) and easily manageable team. So why doesn’t everyone go for the “full-stack dev” solution?</p><p>A few reasons:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F143279985%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F143279985&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F540826777_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/bb05b178fc50138f7b1de50ae05ad986/href">https://medium.com/media/bb05b178fc50138f7b1de50ae05ad986/href</a></iframe><p>1.<strong> Master of none </strong>— It’s not just the name of a <a href="https://www.youtube.com/watch?v=BHODdNs8vSo">great tv show</a>. In today’s world, it’s hard to keep up and master both the world of backend and frontend development and just by reading the post “<a href="https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f">How it feels to learn javascript in 2016</a>,” which describes the ecosystem of JavaScript (which its evolvement in the latest years in frontend frameworks allowing building web applications and in the backend side allowed developers build an end-to-end web and mobile solution while mastering one language) I understood how fast this ecosystem changes. And this was only in 2016!</p><h3>Brian Holt on Twitter</h3><p>Fullstack&quot; developer.</p><p>That said, you don’t always need to draw a perfect horse. Sometimes it’s enough just to paint an ear or the horse’s tail. In other words, you just need to know basic backend well enough to write a simple endpoint in an existing service or have enough knowledge in React to create a button invoking the amazing microservice you created. Put simply, it’s ok for a full-stack developer to have a <strong>tendency</strong> for a specific domain — here is no need to strive for a 50–50 domain knowledge. Depending on the product, you need to have just enough knowledge to draw the horse’s tail.</p><p>2. <strong>Recruitment challenges </strong>— Finding top-performers in today’s community is challenging, and trying to find them in a community that requires more knowledge and expertise makes it even harder to build your dream team.</p><p>One of the difficulties in finding a good full-stack developer is assessing the expertise of such an engineer. Moreover, defining the type of engineer you need on your team becomes much more challenging in a full-stack ecosystem.</p><p>There are various ways of dealing with such a challenge. But you should view it as an opportunity. Building such a team requires people who are collaborative (to transfer knowledge and for mentoring), innovative (tech-wise and as a result more and more product innovative) and willing to learn. Therefore, usually these teams are more productive and successful due to the characteristics of their members — <strong>A-players will form an A-team</strong>.</p><p>The passion to learn and evolve should be a strong indicator in the recruitment process, even trumping knowledge and experience.</p><p>One more opportunity is that by removing the technical knowledge barriers in the team there are more options for personal growth of its members which in turn leads to more satisfied team members which leads to a more engaged team. I call this state of mind — “drop the walls” culture.</p><p><strong>Cracking the challenge</strong></p><p>How do we overcome these challenges and still enjoy benefits like removing bottlenecks and getting a more independent team? My way of tackling this was to move the focus from full-stack developer to a <strong>full-stack team</strong>.</p><p>What’s the difference?</p><p>Instead of working hard to find those unicorn full-stack developers, create a team made of developers that complement each other’s abilities and build a full-stack capable team. The focus then shifts from the individual to the team’s ability to deliver a product or a feature, giving you, the leader more flexibility with whom you hire and when. No more looking for the perfect all-in-one developer and instead focusing on the perfect all-in-one team. HR funnels usually need to work harder in creating this cross-functional team — every new team member needs to have capabilities that will balance the tech needs of the team. It’s ok to have a senior backend developer in the team without frontend/DevOps/data abilities as long as they balance the full-stack abilities of the team. Pay attention that this can be done not only by recruitment but also by personal growth and knowledge transfer processes.</p><p>A side note, this kind of team needs to be “closer” in more than one sense. Physically, the team has to sit in proximity to each other for collaboration. Culturally, the team has to embrace ego less people to allow mentoring and working together approach, and methodologically, meaning — all the practices that can support this approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/1*xduTwIUUcjTkA6W3jXZfjQ.png" /><figcaption>Balancing the perfect team</figcaption></figure><p>Last words to conclude, Balancing the team and focusing on creating a full stack team isn’t enough and it can become a great cross-functional team that can be independent but will be challenged by resources according to road map focus. To keep the team independent and autonomous, you always need to encourage the <strong>“drop the walls” </strong>culture in which everyone in the team knows that they can conquer areas and techs even outside their expertise and knowledge with the right mentorship and practices ( pair programming, pull request process, code convention and more)</p><p>Go create the perfect team!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90a51530d4bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ironsource-tech-blog/full-stack-fiction-or-real-90a51530d4bc">Full-stack: fiction or real?</a> was originally published in <a href="https://medium.com/ironsource-tech-blog">ironSource Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technical backlog- A way to encourage innovation]]></title>
            <link>https://medium.com/@mikilior/technical-backlog-a-way-to-encourage-innovation-9728301b4eab?source=rss-d022ff4794aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/9728301b4eab</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[technical-debt]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[miki lior]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 07:23:55 GMT</pubDate>
            <atom:updated>2018-06-28T07:23:55.083Z</atom:updated>
            <content:encoded><![CDATA[<p>Innovation has to be encouraged continuously and finding ways to do that successfully are one of the challenges of engineering leaders. Defining culture -which I surely have to write a post about, Is great to show people the path to be taken, but setting innovation as one of the main values of the culture isn’t enough. Giving people the right tools to practice innovation is a focus of you as an engineering leader and technical backlog (or known as sometime technical debt) is one of the great tools you have to keep your engineering department innovative at all times.</p><p>Agile is a feature oriented methodology and finding time for technical improvements (such proof of concept for new technology or upgrading your FrontEnd to the latest framework or even fixing a bug in your infrastructure) is hard mainly because it doesn’t bring an immediate business value, which is one of the mantras agile is based on. But you can use a lean methodology in order to continuously maintain and execute your technical backlog. Yes, technical backlog is not the product’s backlog but you can use the same methodology — Maintain a backlog and always prioritize it with your technical leaders (architects? team leaders? technical leaders? CTO?)</p><p>Declaring a technical backlog which contains not only bugs left behind but a real path for innovation is a way to say that our culture is not only values written on a sign in the office’s kitchen and a way to increase motivation in your engineers.</p><p>Few guidelines that helped me keep a running technical backlog:</p><ol><li><strong>Present your team the concept of technical backlog</strong> or technical debt. Explain the motivation and importance of the technical backlog for the organization and for them as technical owners of the product. Explain that the technical backlog is a practice of innovation and serves the company’s innovation culture that will give an actual meaning to company’s value.</li><li><strong>Create a routine and make a plan</strong> — Give them the time for building and executing the technical backlog. The product backlog is important since it gives business value which is why we here and there will be always a short of time so to make time — create a constant time in the sprint (If agile is your thing). One of my routines was to dedicate 10% of the sprint to technical backlog issues. Every few sprints a “technical vision” meeting occurred to plan the “release” (same as we plan a release of a version with a number of features we want to set a set of technical improvements we want to add) of issues we wanted to promote with the technical owner and CTO\Architect.</li><li><strong>Create ownership</strong> — Make sure that the responsibility of building and maintaining the technical backlog is under your team leaders’s responsibility so they own the responsibility of the technical innovation in your team .If you have architect or CTO roles in your engineering department — Use these roles as tools for the engineering teams to find new ways to improve the product under their responsibility but not as the owners of the technical backlog. The responsibility for delivery has to be the team leaders so ownership will be emphasized. Encourage that all the team will be involved in creating and working on the technical backlog so they will understand the importance of executing the technical backlog and will be committed to its delivery.</li><li><strong>Experiment with new technologies</strong> -Use POC as a tool that will help you to rough estimations of your technical backlog.This You gave your engineers another approach to a new technology and justify your support in innovation. it’s a boost for engineer’s motivation when experimenting with new technologies.</li></ol><p>Remember — a technical leader is not only about executing the organization’s product pipeline but also creating a technical vision and keep you engineers always into cutting edge technologies. With a tool like technical backlog you can serve these goals and by the way keep your engineers motivated and innovative.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9728301b4eab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secrets for building and hiring great teams]]></title>
            <link>https://medium.com/@mikilior/secrets-for-building-and-hiring-great-teams-af2e938ba7f1?source=rss-d022ff4794aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/af2e938ba7f1</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[growing-teams]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[miki lior]]></dc:creator>
            <pubDate>Sat, 23 Jun 2018 12:26:41 GMT</pubDate>
            <atom:updated>2018-06-25T21:11:01.744Z</atom:updated>
            <content:encoded><![CDATA[<h4>First, no secrets here.</h4><p>I learned over the years that recruiting great engineers is a process that needs a continuous engagement and needs to follow some basic steps and principals (AKA “secrets”) that allow you to recruit the best people for your team and build the team that will make you leap happily on your way to work every morning.</p><p>Just to make clear — Team is your direct surroundings and doesn’t refer to the classic term of team. It can be your group managers, team leaders or anyone reports to you.</p><p>Have fun!</p><ol><li><strong>Allocate time for recruitment or your recruitment process</strong></li></ol><p>One of any leader’s roles is not only handling the day to day routine and focus on the delivery and execution aspects of the team but also spend time on “planting the seeds” for the perfect team and in order to do that you need to keep a constant percentage of your time for that.</p><p>In some places ,where the team is growing in scale, I Invested about 20% precent of my time in team building , But there is no thumb rule for this principal — I found myself always examine and fine tuning this amount of time — more than that can affect your main activities as a leader and less than that can kill the main pipeline that feeds your team.</p><p>If you won’t allocate time for the building process (And it can be interviews, engaging to potential candidates on the phone or even organising meetups to attract the right team members) you will find yourself struggling with your team in a survival mode without vision and ways to handle the future challenges that your team should handle.</p><p><strong>2. Determine which are the right people to your team</strong></p><p>Ok. There is a decision that the team needs to grow, a new team needs to be opened or we need a new superhero to save the day. It always starts with sitting and deciding on the role definition — requirements, advantages and capabilities which is super important — Well, if it’s a fronted team the new guy needs to know his javascript, no? But the key for getting the right guy into the team is mainly to understand what kind of a team member he/she should be. It’s the same like finding the next piece of the puzzle — every piece is different but takes us closer to the perfect puzzle.</p><p>What are the characters your new team member needs? It depends on the current state of the team, the culture and values of the organisation and the future roadmap awaits. If it’s one of the first team members you should expect him to be independent, self learner and maybe with some mentoring capabilities for future on-boarding for new team members. Roadmap of the team has tight milestones and a long backlog? You maybe need more of a “feature oriented” personalty — fast executioner, with high ownership qualities is what you need.</p><p>It’s easy to define your perfect candidate by measurable characters as years of experience, education and so on but setting the right qualities for any team member you want to join to the team will ensure your team will be well balanced. Always ask yourself — Which is the right guy I need <strong>now</strong> for the team.</p><p><strong>3. Create your recruitment funnel</strong><br> Each role you need for your team needs a different funnel and one thats needs to be built from some building blocks like — an interview with the hiring manager, interview with the HR in your organisation, hands on code challenge and so on. If you hire an architect for your team it may be best that a short phone interview in which you present him the role and the challenges in it may raise the chances for him to accept the job and for you to find a better fit, but if it’s a junior QA engineer you look for sometime it’s better that an conducting first an HR interview that will ensure a cultural fit might be better.</p><p>During the years I found that maybe the order of the building blocks maybe differ from role to role but there are a few that I find them most important -</p><ol><li>Kick off — Can be with all the participants of the process ( If known ) but at least with the direct manager and the one responsible on the funnel ( probably HR manager? ). In this kickoff you define the best funnel for getting the right member along ( culture fit is the most important? Maybe placing the HR interview in the beginning of the process may save your engineers time ).</li><li>Code challenge — people will respect and will prefer organisations that test their skills better and know that you screen your candidates in a proper way and what better way to do that than a real life problem or something similar to your day to day challenges.</li><li>Decision committee — If the candidate reached the end of the funnel get together with all the stake holders of the process and decide.Remember, Final decision is always the direct manager’s one.</li></ol><p>But the most important principal is <strong>make it lean </strong>— recruitment process should be handled as an agile process and needs a retrospective from time to time in order to improve it but even from candidate to candidate you <strong>can</strong> change it and make it more fit to the candidate. If you identify the candidate as a star in the beginning of the process or he\she has some impressing projects in his past, sometime changing or shorten the process can raise the chances of him joining the team.</p><p><strong>4. Teach how to recruit</strong></p><p>Identify all the people involved in the recruitment funnel (team leaders? senior developers?) and teach them how to recruit which is one of the important skills as a technical leaders. I keep passing on key principals in recruiting (“the art of technical recruiting” — let’s wait for another blog post?) for every member in my team that is engaged in the recruitment process and uses it as one of the ways to improve technical leadership skills of my leaders.</p><p><strong>5. Always preach for zero-ego</strong></p><p>Every leader dreams on a functional team acting in a collaborative way and the most important quality you should aspire to in order to achieve that in your team is <strong>no-ego</strong>. A team without ego can accept new members with no difficulties and can function properly when a team member needs help with no need of you as a leader being involved often in solving conflicts. In a team that has the culture of zero-ego you can see senior members sitting for mentoring sessions even on account of their own tasks and you will enjoy the advantages of an independent team.</p><p>Remember, Even one rotten fruit can spoil the fruit basket — even one member that will prefer his own interests and won’t act as an <strong>enabler</strong> for the team can be toxic for your team.</p><p><strong>6. Make your team happy</strong></p><p>Wow. It’s a complete blog post. But making your team happy is not about pizza in late working hours deploying a version or not even about giving them a raise ( it’s important also. I know) . But making your team happy is about continuous feedback and not waiting for annual feedback with a good word on slack when solving a challenging bug or a pad on the shoulder when acting according to your team’s culture ( someone said zero-ego?). Making your team happy is let them know that their <strong>personal growth</strong> is as important as the challenges the organisation is facing and it is even one of them. So investing, and all the time, in personal growth will ensure your team that they are in the correct path for their career and will them know they are in the right place for them.</p><p>Let’s continue on the next blog post?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af2e938ba7f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linting our way to continuous deployment]]></title>
            <link>https://medium.com/@mikilior/linting-our-way-to-continuous-deployment-ea2d0490e7de?source=rss-d022ff4794aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea2d0490e7de</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[miki lior]]></dc:creator>
            <pubDate>Fri, 22 Jun 2018 20:33:44 GMT</pubDate>
            <atom:updated>2018-06-22T20:33:44.380Z</atom:updated>
            <content:encoded><![CDATA[<p>Scrum is great. It brings order to the developer’s life and brings a lot of visibility to the lives of project managers all around. It becomes almost the magical solution for leaders of development groups all around- can’t deliver on time? use scrum. Need visibility for management? use scrum. Quality issues? use scrum. communication among the team problems? well. you got the idea…</p><p>Here in RapidAPI, As developers developing for developers it’s not enough. We need to deliver fast and most important continuously. Working in sprints gives value product wise but we need to wait 1–3 weeks ( Yes. The debate on the length of the optimal sprint will never end. Let’s settle on 2 weeks.) But why wait if we can do it now and always?</p><p>Sprint tend to end and there for you have to settle if you want to deliver the content you’ve committed to develop in the planning (scrum ceremonies. Remember ? we will talk about them soon) so as a developer and even as a leader you find yourself giving up on content making your technical debt bigger and bigger with no chance of closing it anytime in the future. There for your code base turns to legacy code more quickly — un maintainable and untestable. Refactoring phases are needed sooner than you want them.</p><p>Personal note — I love scrum. I loved it as a developer and as a team leader. today, as VP R&amp;D for the last years I still see the good sides it gives to R&amp;D engineers but I’ve seen teams using the retrospective for evolution of the initial methodology set and it becomes hard to set one unified methodology across the departments since each team set its own methodology. It’s great but hard to control management wise.</p><p>Convinced all ready? We in RapidAPI started the journey to continuous deployment which is more than just a development methodology — it’s a state of mind which makes it even harder to implement from other agile methodologies.</p><p>There is no 0 to 100 in setting your development methodology continuous methodology. If I can set it to milestones it would look something like that:</p><ol><li><strong>Culture shift</strong> — Usually you need to adjust your R&amp;D department’s culture to the organization culture. But moving to continuous deployment needs an ecosystem of <strong>fearless, egoless and independent </strong>engineers but not only engineers, and you need to encourage this culture shift by first talking about it .Rewarding those who are adopted the culture needed for such a change is a way to continue and encouraging the culture shift needed.</li><li><strong>Adopt technical practices and fast.</strong></li><li><strong>Stop thinking on the little things — make time for the important things </strong>— If you have stuff the takes unnecessary time from your crew- fix them. Identify and improve bottlenecks, reduce time of different flows in your current processes. Support tickets keep coming ? invest time in building tools for support so they can do it by themselves.</li><li><strong>Make the change in steps</strong> — You can’t move all your system to continuous deployment on one day. try to plan a strategy to build trust in the process (minor services to be deployed first, make pilot feature to test the flow, move to staging environment first and not directly to production and so on)</li></ol><p>Adopting technical practices is a must even if you don’t adopt a dynamic and time-to- market methodology but we found out that in order to allow an independent process for each feature and not a joined one same as scrum — unit testing, code review, real time monitoring abilities (applicative and infrastructure) , stable automation must be implemented.</p><p>One of the successful implementations of technical practices was the implementation of peer code-review. the first phase of implementing it was to agree on the way our code base supposed to be — framework, language , and structure wise. this was translated to a code review checklist that even if you don’t use it physically it defines the way we are doing code review.</p><p>Next phase was to enforce review policy on our GitHub repositories and just start. A small gathering in which we declare</p><p>It’s a known fact that most of the time Code reviews are about code convention in which you comment about naming variables, functions and the indent of your code ( 2 or 4 indention? one of our most loved debates in the office) so the first improvement to our peer code review was adding code convention enforcement tool — linting — to allow us to debate on more important stuff like best practices, data flow, and how smart you components should be .</p><p>Since RapidAPI codes most in JS stack our natural choice was ESLint which we based it on (like many) and applied it to both our BackEnd and FrontEnd layer which reduced our code reviews time and allowed the team focus on making our code better and not only more readable (which is important also as it allow quicker debugging and development).</p><p>To summarize, Adopting technical practices allowed the team to be more independent and allowed us to move forward one more step in becoming continuous deployment adopters and linting was a major factor in reducing the flow to production.</p><p>What about you?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea2d0490e7de" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>