<?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 Aviva Peisach on Medium]]></title>
        <description><![CDATA[Stories by Aviva Peisach on Medium]]></description>
        <link>https://medium.com/@avivap?source=rss-bbb3208464f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*-uLeZrLbAPxZEqaGBH1Tlg.jpeg</url>
            <title>Stories by Aviva Peisach on Medium</title>
            <link>https://medium.com/@avivap?source=rss-bbb3208464f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:17:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@avivap/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[The Craft of Troubleshooting — From Art, to Science, to Automation]]></title>
            <link>https://medium.com/wix-engineering/the-craft-of-troubleshooting-from-art-to-science-to-automation-31a028a0836a?source=rss-bbb3208464f------2</link>
            <guid isPermaLink="false">https://medium.com/p/31a028a0836a</guid>
            <category><![CDATA[resilience]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <category><![CDATA[sre]]></category>
            <dc:creator><![CDATA[Aviva Peisach]]></dc:creator>
            <pubDate>Fri, 18 Nov 2022 11:27:20 GMT</pubDate>
            <atom:updated>2022-11-20T14:36:26.481Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Craft of Troubleshooting — From Art, to Science, to Automation</h3><p>Those who read my <a href="https://medium.com/wix-engineering/triumphing-postmortem-killers-188f09df80fc">previous post on postmortems</a> know that resilience is a subject close to my heart.</p><p>After all, at <a href="http://www.wix.com/">Wix</a> we deal with thousands of microservices and hundreds of deployments a day, with a multi -cloud environment and with numerous internal and external dependencies, which are being used by hundreds of millions of users. Improving resilience is the backbone (among others) of a stable and a growing engineering products and environment.</p><p>A couple years back in our quest to improve resilience we measured our MTTR (median time to resolution of production incidents) and found that a lot of this time is invested in troubleshooting.</p><p>So the challenge at hand was “How do we optimize and minimize troubleshooting time across the company?”.</p><p>At first, this seemed a bit of an impossible mission due to the following assumptions:</p><ol><li>We tended to view production troubleshooting as an art rather than a science — where only the “tribe’s eldest”, the senior and most experienced members master troubleshooting — ones that achieve that after spending nights dealing with production issues and knowing the system inside and out.</li><li>Wix is split into dozens of groups each with their own infra and architecture. Thus we assumed each one is a unique snowflake with their own flows, issues and, therefore, different system knowledge and troubleshooting practices.</li></ol><p>Nothing masks reality better than making assumptions… So our first step was to map our actual different troubleshooting practices.</p><h3>Reality check</h3><p>We brought together these troubleshooting veterans from different groups and mapped on paper (or more accurately in a Google Sheet) the troubleshooting steps they tend to typically take. Put to “paper” how they map and rule out immediate suspects, how they decide on what to do next, and what are the common root causes.</p><p>You can imagine our surprise when we found out these different practices are not that different at all! We found that ~80% of the troubleshooting steps are very common across all our different products.</p><p>They all start with similar alerts and continue with drilling deeper into similar paths to rule out similar immediate suspects, and onto mapping the root cause and fixing the issue — all in very similar ways.</p><p>Here are several examples:</p><p>1) The first thing developers should and would check is whether there was a recent GA of the misbehaving service or a change in a <a href="https://www.wix.engineering/post/building-and-open-sourcing-wix-s-a-b-testing-system">corresponding experiment</a> in proximity to when the issue started occurring. If so, the first thing to do is to do a version rollback or revert the change in the experiment.</p><p>2) Developers would also drill in to check if most of the errors can be attributed to specific pods / sites / callers or callees and if so, continue to drill in on these suspects.</p><p>Yay! We struck gold! Commonality meant that it was easier to solve, improve and make a cross company impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Dv5s98W5Gtr8KpLV.png" /></figure><h3>Action plan</h3><p>We decided to address &amp; leverage these commonalities in 4 parallel paths:</p><ol><li><strong>Training</strong> — we built a training kit simulating the common root causes and allowing trainees to practice their troubleshooting skills in a safe and quiet environment</li><li><strong>Improved Monitoring </strong>— since we mapped the common suspects and root causes, we improved our dashboards to include high-level views of these areas to detect things at a glance</li><li><strong>Automation</strong> — since we mapped common practices and next steps, we’ve also built automation around drilling in and providing additional metrics where needed and auto-suggesting next steps</li><li><strong>Self healing</strong> — we’re not there yet, but this is our plan for the future: find the most useful and reoccurring practices, definite root case and resolutions, and fully automate both the troubleshooting and recovery steps — removing the need for a person in the middle</li></ol><h3>Hands-on troubleshooting training</h3><p>The best way to learn how to troubleshoot is to do it hands-on. <br>However, the cost of having each developer experience the vast range of actual production issues in real-time is high and lengthy. <br>Also it is hard to build, maintain and use very detailed troubleshooting guides and cookbooks.</p><p>When you’re awakened in the middle of the night with the CEO / CTO breathing down your neck to solve the issue at hand, following a cookbook (no matter how detailed and well maintained) is not an easy task.</p><p>Thus we decided to create a hands-on training kit: We built a “trouble-maker” service which stimulates production issues on a synthetic service.</p><p>The trainee needs to monitor and troubleshoot in real time until they identify the root cause and fix it. We simulate memory issues, faulty pods, misbehaving dependencies (calling or being called by our synthetic service), and much more. <br>That way the trainee gets to experience actual troubleshooting practices in a safe environment, which prepares them and increases their confidence when they face the real thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vHn2Br54A6VzcqiT.png" /></figure><h3>Monitoring — seeing is troubleshooting</h3><p>Since we mapped the common suspects, we now know what to look for — thus we improved our dashboards to include high level distribution histograms of these areas to detect problematic ones at a glance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/0*OVRpH_vQIAoZ9TNm.png" /></figure><p>These high-level dashboards include error distribution across user agent, by site, by DC, by POD.</p><p>This way you can see at a glance what are the dominant contributors to errors and continue to drill down to relevant traces — specifically on them, quickly closing in on the actual root cause.</p><h3>Automation — if you map it, you can automate it</h3><p>Since we mapped common troubleshooting paths, we wanted to find a way to automate them as much as possible.</p><p>We’ve built the “Alert Enricher” — a system listening in on our alerts (which are published to dedicated Slack channels), checking for immediate / less immediate suspects, and enriching the Alert with more insights and metrics, suggestions for root cause, further investigation and possible remediation.</p><p>A few examples:</p><ol><li>We check and display the recent GA / Experiment change of the misbehaving service and allow to quickly rollback / revert</li><li>We check if a specific POD is misbehaving — and allow to quickly reboot it if needed</li><li>We check if a large % of our traffic is triggered by automation tests and if so — provide an option to block the specific automations</li><li>We also specify top 5 exceptions — which usually spot the “culprit” right there and then, since the top 1st usually has a ratio of 90% above all others.</li><li>If a new exception was introduced (that was not raised before) in the recent timeframe — we also specify it. In many cases it is the root cause for a new alert.</li></ol><p>We’ve started off by having these rules and enrichments hardcoded in the system, but have since extended the system to allow developers easily script their own rules, enrichments and suggestions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y7BDfeElRCvdEzxW.png" /></figure><h3>Self healing — automation: the next frontier</h3><p>The next automation step would be to fully automate the troubleshooting process from detection to verification of root cause to fixing the issue and verifying the fix.</p><p>Some of this process we’ve automated via our home-grown automatic deployment system which is based on our A/B test infra (<a href="https://github.com/wix-incubator/petri">Wix Petri</a>) which checks for any changes in metrics, comparing the old and the new version and automatically rolling back upon finding a match.</p><p>However, before automating the troubleshooting &amp; the fixing of the fully production-deployed version we need to gather much more stats on our semi-automated process to find the high probability root causes and fixes, since otherwise we may cause more harm than good.</p><h3>The outcome — fruits of our labor</h3><p>The steps we’ve done so far have significantly reduced our overall troubleshooting times.</p><p>We’ve seen a<strong> 27% decrease </strong>in median time to resolution between 2020 and 2021.</p><p>Many teams confess that they don’t know how they previously managed without it!</p><p>We’ve reduced human single points of failure as more/all members of any given team are capable of performing production troubleshooting, or at least reduced the fear factor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*VPkb5s2qwW9ePx9E.png" /></figure><p>We’ve also streamlined the training kit to our standard onboarding (3 months after initial onboarding) plus enhance the Alert Enricher with more scripting and customizations, we expect to see an even more dramatic impact going forward.</p><h3>Takeaways and lessons learned</h3><p>This journey taught us yet again to make no assumptions and to base our decisions on research and data rather than gut feelings. It also reminded us that there’s no one silver bullet solution when it comes to resilience.</p><p>Resilience is an ongoing journey with no finish line. One where you need to work on multiple fronts with the goal of continuous learning and improvement in mind.</p><p>As this journey continues, stay tuned for more revelations on this front. Want to join us or consult on the resilience journey? Don’t hesitate to <a href="https://www.linkedin.com/in/aviva-starovolsky-peisach-a24a7925/">reach out</a>.<br>Note: This article (amongst many others) is also posted in the <a href="https://www.wix.engineering/post/the-craft-of-troubleshooting-from-art-to-science-to-automation">Wix Engineering Blog</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31a028a0836a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wix-engineering/the-craft-of-troubleshooting-from-art-to-science-to-automation-31a028a0836a">The Craft of Troubleshooting — From Art, to Science, to Automation</a> was originally published in <a href="https://medium.com/wix-engineering">Wix Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The No Process Process — 6 Tips for Reducing Process Overhead and Increasing Developer…]]></title>
            <link>https://medium.com/wix-engineering/the-no-process-process-6-tips-for-reducing-process-overhead-and-increasing-developer-702a1358d35?source=rss-bbb3208464f------2</link>
            <guid isPermaLink="false">https://medium.com/p/702a1358d35</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <dc:creator><![CDATA[Aviva Peisach]]></dc:creator>
            <pubDate>Sun, 06 Nov 2022 08:04:01 GMT</pubDate>
            <atom:updated>2022-11-06T08:19:06.500Z</atom:updated>
            <content:encoded><![CDATA[<h3>The No Process Process — 6 Tips for Reducing Process Overhead and Increasing Developer Independence, Velocity &amp; Innovation</h3><p>As (engineering) managers, we sometimes tend to believe that our role is to “create order in the chaos” and that the best way to achieve it is by bringing in a clear set of standards, rules &amp; processes.</p><p>While a good process / standard can have a positive impact on clarity and order, when excessively used, it can kill innovation and even hinder velocity &amp; motivation.</p><p>Process is a bit like a salt, when used sparingly, it will spice up your dish, balance it and accent other unique flavors, but when excessively used, it will override all other flavors, pickle and ruin your dish all together.</p><p>To clarify: by “Process” or “Standard” I mean any set of rules on how to perform a specific task, so that we don’t only dictate what to do, but how it should be done (e.g., coding standards, design guidelines, protocols for delivery to production, production incident management processes etc.)</p><p>So, How can we balance standards &amp; processes with developer independence?</p><p>In other words, how can we have the cake and eat it (with our pinch of salt :)</p><p>Below are 6 tips that can help you create this balance:</p><h3><strong>1. Build standards bottom up</strong></h3><p>Standards are there to resolve some kind of pain. Developers are typically the ones feeling the pain — therefore they should be the ones building the solution.</p><p>Create an ad hoc team of developers, to map the issue and suggest a solution or a standard.</p><p>This will also allow the standard to be tailor-made for the developers, and make them much more engaged, rather than trying to apply a new rule / process top-down while detached from the problem at hand.</p><h3><strong>2. The need for standard / process needs to be well reasoned, documented and communicated</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/0*bpq7aVjoPOXCz7Su" /></figure><p>You should have a very good explanation of the motivation (i.e., pain the standard comes to resolve), and how it introduces less overhead and negative impact than without it.</p><p>Document the explanation so it’s referable to future generations.</p><p>This explanation also needs to be defined bottom-up, and should be clearly communicated and discussed when applying it across the organization.</p><p>By “discussed” I mean actually discussed (rather than preached). You need to be willing to hear feedback, pushback and challenges to verify it will actually achieve the expected ROI. And be willing to drop it, when strong, genuine &amp; justified pushback arises.</p><p>Note that applying a new standard is a <strong><em>change </em></strong>to the status quo that was applied thus far.</p><p>Developers (as most human beings) don’t like <strong><em>change</em></strong>, and therefore a default reaction to change may be pushback, so you need to listen carefully and impartially to the pushback in order to distinguish between auto-pushback (the natural reaction to any change) and a genuine one.</p><h3><strong>3. Don’t fall in love with your process — be ready to kill it or change it when needed</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CilWyTOfq-B8zfVt" /></figure><p><strong><em>Standards are there to fulfill a purpose. The purpose is not to fulfill the standards.</em></strong></p><p>You need to remember this, keep reviewing the standards on an ongoing basis, verify that it stands the test of time and still fulfills the original purpose. And if not, be able to change and adjust, and sometimes completely eliminate it.</p><p>Standards tend to become a habit, and habits may turn into <a href="https://en.wikipedia.org/wiki/Cargo_cult">cargo cult</a>, where people just follow the standard without knowing or questioning what it’s there for and without checking if it actually archives the purpose.</p><p>Or even worse, if people don’t understand or agree with the purpose and don’t feel comfortable to voice their opinion, they may try to workaround the standard. They might end up either ignoring it or blindly ticking the box missing the original intent and thus creating meaningless red-tape &amp; frustration.</p><p>A few techniques you can use to keep standards to the test and avoid this slippery slope:</p><ol><li>Set reminders in your calendar, for 3/6/12 months since the standard/ process was introduced, to check its efficiency. It can be a check you do on your own, with some team representatives or with all engineers. <br>I try to include it in a periodical survey to all engineering teams gathering feedback on efficiency of all our main standards and ways of working.</li><li>Create an <strong>open </strong>and <strong>trustful </strong>culture where people are encouraged to give sincere feedback and voice their opinion when they feel something doesn’t work or doesn’t make sense (best way to achieve it is by actually listening to feedback, acting upon it and communicating back the actions based on the feedback. This is how people will know they are heard and can make an impact, and therefore, are also accountable for things not changing if they don’t voice their feedback)</li><li>Do just that :) communicate back the aggregated feedback, and the actions you’ve taken based on it. If a process failed, communicate and celebrate it’s extermination. If the feedback is positive, celebrate the process continuation based on it’s continual efficiency. In any case, be transparent and celebrate :)</li></ol><h3>4. <strong>Minimal (to none) enforcement</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_cIp8EbWkfjj68jV" /></figure><p>If we envision a spectrum of enforcement levels — varying between no enforcement whatsoever, to full enforcement (with ramifications of failing the enforcement), you would want the vast majority of your standards to not be enforced.</p><p>In general, you should <strong><em>favor facilitation over enforcement</em></strong>. <br>Invest your time in making the standard as accessible, well known, understood, and easy to use, rather than in chasing everyone to follow it or penalizing teams that don’t.</p><p>Roughly speaking, I try to have the following split of our standards</p><ul><li>40% no enforcement whatsoever</li><li>10% enforced</li><li>50% somewhere in between</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/0*6HyauYg2TS69xcQE" /></figure><p>Let’s drill down a bit to understand best practices and examples (we apply at Wix) for each</p><ol><li><strong>Enforced</strong> — these are the business critical standards, where not following the rule may have a significant and immediate negative business impact (e.g., regularity requirement, cost related guidance). In these cases, we have to enforce adherence to the standard. (<strong><em>examples </em></strong>where we do apply enforcement: GDPR and PII adherence, wasteful resource utilization)</li><li><strong>No enforcement whatsoever</strong> — these are the cases where we fully trust the team’s judgment to apply (or not apply) the standards that fit them. In these cases we still need to provide <strong>guidance</strong>, <strong>training</strong>, <strong>documentation </strong>on best practices for the standard, making the documentation accessible and <strong>discoverable </strong>to all, but not enforcing adoption of the standard. <br>An <strong><em>example </em></strong>where we do not apply any enforcement is <strong><em>design guidelines</em></strong>. At Wix, we created comprehensive guidelines and documentation of design tradeoffs and recommendations (based on our collective lessons learned from designing large scale, performant and resilient systems). We also created design templates and provided intense training on both. <br>But each team decides whether and how to do their design, and whether to use the guidelines.<br>Each team is entitled to make their own design “mistakes” or discoveries, and update the overall guideline if they find any new design lesson learned.<br>Teams are also encouraged to request a design review if they feel it is beneficial for them.<br>The overhead of enforcing design guidelines (e.g., having architects review &amp; approve designs) would have created bottlenecks and frustration, kill exploration and innovation, and not have been worth the ROI.</li><li><strong>Somewhere in between</strong> — these are the places where not adhering to the standard would create an impact (important but not a critical one) and we trust the team’s engagement in fulfilling it without the need to apply further enforcement. In this case, in addition to standards &amp; guidelines, we also need to provide communication on the motivation, importance and expected timeline (where applicable) and expect teams to provide visibility on when and if they will adhere.<br>An <strong><em>example </em></strong>for such a standard are the dev languages and platforms we support( e.g., in Wix for backend engineering, we decided to provide support for Scala and Node.JS only). A team that wishes to develop in a different language can do so, after they’ve consulted with the guild, explained their unique needs (and why they feel it can’t be supported with the given frameworks) and confirmed they understand the overhead they’re taking on themselves (which is to support the Wix infra on their own including multi DC deployment, CI, CD, failover and reliability) and still expect to have a positive ROI.<br>This is how we can make educated decisions on exceptions to the standard, and also get a good sensing on whether the standard needs to be changed or extended (e.g. if we’ll see an increasing number of justified requests to use a new language, we may decide to expand our standard and framework support to it as well).</li></ol><h3><strong>5. Automation Automation Automation</strong></h3><p>Did I mention automation? Since we want the process and standard to work for us, rather than us working for the process — the best way to achieve it is by taking away the overhead of the process as much as possible and automate anything that can be automated.</p><p>A few examples for standard automation we’ve built in Wix:</p><ol><li>We expect teams to conduct post mortems including measuring the impact the incident has on production. To avoid a big manual overhead, we’ve automated filling the impact by linking incidents to business KPIs and automatically collecting the impact at the time of the incident (from opened till resolved).</li><li>We’ve built a system called “CI buddy” that provides visibility to any team on their code adherence to any rule. In some cases, the system also provides an auto PR allowing to automatically fix the code and adhere to the rule.</li><li>Since compliance to regulatory requirements (via PII encryption, getting and deleting PI information) is a cross company / service concern, we’ve incorporated support for it in our platform and frameworks. Developers get it out of the box, do not need to remember it or reinvent the wheel each and every time they build a new solution.</li></ol><h3><strong>6. Always Allow Exception to the rule</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bqYd0evxcnZ7Bsy0" /></figure><p>Even if we apply rules, process and enforcement, we always need to make sure we allow exceptions to the rule to allow for innovation and self-check.</p><p>Here are 3 examples of where you’d want to make sure you have rule free playgrounds:</p><ol><li><strong>Hackathons</strong> — where the innovation aspect is critical and easily killed when applying processes.</li><li><strong>POCs</strong> — where we’re looking to prove added value or fail fast we can not afford (and shouldn’t invest) in adherence to standards if it comes with a significant overhead. Once and if the POC is successful, productizing the offering will need to adhere back to the standards.</li><li>Where the process / standard does <strong>not solve the problem</strong> it was originated for. (see my example of Wix backend supported languages standard above)</li></ol><h3>Have your cake and eat it (Too)</h3><p>So, in order to reach the balance between process and developer independence, we, as managers, need to focus our efforts on: deciding which standards are actually needed, forming &amp; revisiting them collectively and continually, and facilitating their automation &amp; ease of adherence as much as possible.</p><p>By doing this, we significantly increase our chances to achieve what we aimed to achieve in the first place: velocity &amp; motivation without hindering developer independence.</p><p>Have questions? want to share your thoughts and experience on engineering culture? feel free to reach out <a href="https://www.linkedin.com/in/aviva-starovolsky-peisach-a24a7925/">via linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=702a1358d35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wix-engineering/the-no-process-process-6-tips-for-reducing-process-overhead-and-increasing-developer-702a1358d35">The No Process Process — 6 Tips for Reducing Process Overhead and Increasing Developer…</a> was originally published in <a href="https://medium.com/wix-engineering">Wix Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Be Humble, Listen and Offer a Perspective: 7 Power Tips for Your Next Mentorship Session]]></title>
            <link>https://medium.com/wix-engineering/be-humble-listen-and-offer-a-perspective-7-power-tips-for-your-next-mentorship-session-3d5c86d2473e?source=rss-bbb3208464f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d5c86d2473e</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <dc:creator><![CDATA[Aviva Peisach]]></dc:creator>
            <pubDate>Fri, 28 Oct 2022 18:48:44 GMT</pubDate>
            <atom:updated>2022-10-28T18:48:44.055Z</atom:updated>
            <content:encoded><![CDATA[<p>Six months ago, <a href="https://www.wix.engineering/">Wix Engineering</a> initiated a speed, <a href="https://www.wix.engineering/post/wix-engineering-book-a-session-with-us">open mentorship program</a>, where a handful of our engineering leaders offered their time for mentorship and consultation to anyone, out there in the world, who desires to leverage it.</p><p>Since knowledge sharing in all its shapes and forms, and particularly mentorship, is one of my passions, I gladly onboarded the initiative and offered mentorship on self and organizational growth, dev culture, engineering excellence and anything in between…</p><p>After six months into the program with dozens of mentorship sessions under my belt, I’d love to share my lessons learned so far.</p><h3><strong>Speed mentorship and ongoing mentorship are not the same beast</strong></h3><p>The first thing I realized, as one might expect, was that a one-off, 30-minute mentorship session is very different from an ongoing mentorship program you give your mentees inside your organization.</p><p>You have no former knowledge of the mentee, their background, their position and what they are looking to achieve.</p><p>It’s a one-off session — no time to build a relationship and trust, no time for trial and error, or trying out and building techniques that suit you both.</p><p>On the other hand, since there’s no prior acquaintance, there’s also no bias or assumptions, nor potentially conflicting agendas. It’s a “no strings attached” experience, which allows for an Immediate and more open discussion with the mentee.</p><p>Once we (mentor and mentee) committed to these 30 minutes — there’s only something to gain, and nothing to lose from engaging in an open conversation.</p><p>Although very different, I feel that speed mentorship is a more condensed, objective playground to mentorship as a whole, hence the lessons learned from speed mentorship can be applied back on an any ongoing mentorship.</p><h3><strong>Mentorship is a two-way street</strong></h3><p>With my 25 years of experience in engineering management in global organizations &amp; startups, I felt I had a pretty good exposure to different types of engineering cultures, challenges, growth paths &amp; dilemmas out there, and the chance to surprise me with new dilemmas would be pretty slim.</p><p>Well guess what, I was wrong! There was something new and different to learn from each one of the mentees.</p><p>Whether it’s a different culture, organization structure, base assumptions and background of the mentees themselves, each of the mentees revealed a new and interesting world to which I didn’t get a chance to be exposed before.</p><p>I’ve eaten my humble pie and recalled once again that everyone and anyone is it’s own unique self, and has something interesting to share with me and to learn from.</p><p>And that in every mentorship session, we serve both as mentors and mentees, learning something new about the world and about ourselves.</p><p>So here come my tips and lessons learned:</p><h3><strong>1. Be humble</strong></h3><p>You don’t know it all! No one does and no one needs to.</p><p>You have added value as a mentor -not necessarily because you have all the answers and encountered all possible situations and dilemmas, and know the perfect recipe to resolve them all.</p><p>But because you’re wise, experienced, and ideally a good listener. You know how to help get to the real root cause of a problem/ dilemma and provide confidence and guidance to the mentee to carve a path on their own.</p><p>You are a facilitator in their journey, not a problem solving machine.</p><h3><strong>2. Spend more time listening than speaking</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n9pDggoEv9x8PerA" /></figure><blockquote><em>“If your mouth is open, you’re not learning.”</em> — Buddha</blockquote><p>You only have 30 minutes to get to know the mentee, understand together what it is that they are trying to achieve, and pave a way together that can assist them in achieving their goals. That’s a lot of learning you need to do in a very short time, and the only way to achieve that is to truly listen.</p><p>Remember that this session is about them, not about you. So don’t jump in telling your stories and giving concrete advice until you’ve truly listened and heard…</p><h3><strong>3. Don’t make assumptions</strong></h3><p>You don’t know anything about the mentee, their background and past experience.</p><p>Do not hurry and correlate their challenge to yours (it’s never the same) Don’t make assumptions on their past experience, abilities or constraints, nor on their interfaces or organization culture — just ask rather than assume.</p><h3><strong>4. Prefer asking questions over giving answers</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C60YUkZGG1qwwE05" /></figure><p>Although, and sometimes since the session is short, mentees tend to come in with prepared questions / targets in mind after they spend time thinking about the problem, making a lot of assumptions about what are feasible options, what’s doable, and what’s not.</p><p>Therefore, in many cases, the question they ask at the beginning of the session is often not the actual problem they are trying to solve, or the goal they are looking to achieve.</p><p>You need to carve out the root cause, dissolving unrelated assumptions. And you can achieve this by asking questions. If you just answer the original question, most chances are, you didn’t address the real issue at hand.</p><p>One of my mentees came into the session with a question of “How to be a good architect”? After probing a bit with questions, it turned out that he was actually looking for a way to be more impactful in the organization while gaining better engagement from teams. While we were carving out the journey, he found that it was not actually via an “architect role”, but with a combination of a trainer and individual contributor.</p><p>We would not have gotten to this path if we didn’t go through the additional questions to clarify what it really was that he was looking to achieve, and why.</p><p>So here’s a list of questions which can help take your there:</p><ul><li>What are you trying to achieve?</li><li>Why? (as many times as needed)</li><li>What have you tried thus far? What succeeded, what failed, and why?</li><li>Describe an ideal world</li></ul><p>Once you believe you found the root goal together, echo it back to the mentee to verify it is indeed the actual goal.</p><h3><strong>5. Offer a perspective rather than an answer or advice</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wyewk5P6hHUVjf-W" /></figure><p>Once you’ve asked clarification questions (and truly listened to the mentee) and feel that you have a good grasp of the situation and the mentee’s goal, you can now help them pave a path to fit their needs and desires.</p><p>At this point, beware of giving them “an answer” — there’s never one correct answer, and remember that you had very limited time to understand the full complexity of the situation.</p><p>What you can offer instead, is a perspective from your personal understanding and past experiences.</p><p>Try avoid phrases like:</p><ul><li>“What you should do…”</li><li>“What works / doesn’t work in this situation…”</li></ul><p>Instead you can use:</p><ul><li>“Let me share what worked &amp; didn’t work for me in a similar scenario”</li><li>“An approach you can try…”</li><li>“ if I was in your shoes. I believe that what I would try…”</li></ul><p>It is also good to explicitly state that this is your perspective and that they will need to do trial and error to find out what best works for them.</p><h3><strong>6. The best advice is the one that comes from within</strong></h3><p>The most impactful conclusions are typically the ones that the mentee will reach on their own (with your guidance).</p><p>This is much harder to achieve in such a limited timeframe, as it requires a more in-depth process. However, you can try and help the mentee get there by asking guiding questions and helping them to see the situation from a different perspective.</p><p>You can use the following type of questions:</p><ul><li>How does your manager see the situation? What are their motivations?</li><li>What is your interface motivation? Where do your motivations meet?</li><li>What stops you from doing [something specific] today?</li><li>What would you have done if this would have been a different organization / manager / position? (anything to exclude fear of implications from the equation)</li><li>What would be a win-win in this case?</li></ul><h3><strong>7. Get feedback</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GRTGv2WXIQRXMKuM" /></figure><p>Most chances are you won’t meet again to hear what of the realizations of your conversation the mentee will take forward and try and apply in real life, and whether they fail or succeed. Hence, no time like the present (last minutes of your chat) to get the mentee’s feedback on the session you just had, so that you can improve as a mentor.</p><p>What I usually ask:</p><ol><li>What are your takeaways from this chat?</li><li>How was the session for you?</li><li>I want to continually improve my mentorship, so would greatly appreciate your feedback on anything different / additional you suggest I do in future mentorship sessions.</li></ol><p>The last one may be harder to ask since asking for sincere feedback takes courage on both sides. but keep in mind that the ”No strings attached” approach, allows the mentee to “pay back” in contributing to your growth. The more sincere the request, the more sincere (I believe) the answer will be.</p><h3><strong>Conclusion</strong></h3><p>Looking back at these 6 months of speed mentorship sessions, despite the fact that speed mentorship is completely different from an ongoing one, I believe that the lessons I’ve learned will make me a better listener and mentor. And I truly hope that you can leverage some of these tips as well in your next speed or regular mentorship session.</p><p>And if you’d like to chat about mentorship, engineering growth, engineering culture or anything in between, just go ahead and <a href="https://www.wix.engineering/post/wix-engineering-book-a-session-with-us">book a speed mentorship session</a>, I’m always happy to chat, grow and learn together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d5c86d2473e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wix-engineering/be-humble-listen-and-offer-a-perspective-7-power-tips-for-your-next-mentorship-session-3d5c86d2473e">Be Humble, Listen and Offer a Perspective: 7 Power Tips for Your Next Mentorship Session</a> was originally published in <a href="https://medium.com/wix-engineering">Wix Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Triumphing Postmortem Killers]]></title>
            <link>https://medium.com/wix-engineering/triumphing-postmortem-killers-188f09df80fc?source=rss-bbb3208464f------2</link>
            <guid isPermaLink="false">https://medium.com/p/188f09df80fc</guid>
            <category><![CDATA[resilience]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <category><![CDATA[scale]]></category>
            <category><![CDATA[postmortem]]></category>
            <category><![CDATA[wix]]></category>
            <dc:creator><![CDATA[Aviva Peisach]]></dc:creator>
            <pubDate>Wed, 23 Oct 2019 05:35:50 GMT</pubDate>
            <atom:updated>2019-10-23T05:59:36.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FRBJn6LY8x_QSEoaV1v2nw.jpeg" /></figure><p>One of my (Jewish) new year’s resolutions is that every moment of revelation I experience, I will try and turn into a blog post, to share this knowledge or perspective with the world.</p><p>It’s been almost three weeks after new years and 2 blog posts under my belt, so I’ve been keeping my word. So far :)</p><p>If you want to catch up on my previous blog post on <a href="https://medium.com/@avivap/continually-growing-your-engineering-skills-while-scaling-the-organization-the-unique-wix-596536b857ff">wix engineering culture and growth</a> read <a href="https://medium.com/@avivap/continually-growing-your-engineering-skills-while-scaling-the-organization-the-unique-wix-596536b857ff">here</a>.</p><p>Current revelations I’d like to share are in regards to postmortems. Less about what they are and how important they are — since I assume this is common knowledge by now, or at least highly accessible knowledge. Instead I’d like to focus on what kills postmortems (pun intended) and how we at <a href="http://www.wix.com/">Wix</a>, battled these silent killers, to make postmortems great and effective again!</p><blockquote><strong><em>“You can’t go back and change the past, so look to the future and don’t make the same mistake twice”</em></strong></blockquote><p>At <a href="http://www.wix.com/">Wix </a>we deal with thousands of micro-services and hundreds of deployments a day, a multi cloud environment, and numerous internal and external dependencies being used by hundreds of million users.</p><p>Things are bound to go wrong and thus, they actually do. Breaking production is part of our daily routine and is almost inevitable.</p><p>What is a must though, is learning from these issues, not repeating similar mistakes and continually improving our resilience, otherwise issues and instabilities could repeat and grow bringing us to a halt.</p><p>This learning could be achieved mainly by postmortems.</p><p>Postmortems allow us to objectively, review the trail of events, find pitfalls and gaps in our procedures, knowledge, products and tools and map ways to improve going forward by either avoiding similar issues or improving detection and resolution time for future issues.</p><p>With this being the common knowledge, you would expect everyone to simply conduct constructive postmortems and move on.</p><p>Right?</p><p>Well, not exactly.</p><h3><strong>When postmortems die</strong></h3><p>With good intentions (as well as smaller scale and less production issues) in mind, we used to have a fairly rigid, comprehensive, long template for conducting postmortems. We expected every postmortem to be performed in a meeting with all stakeholders, people involved in the incident and other representatives.</p><p>What we found was that these full fledged postmortems rarely happened in reality. The effort required to gather all relevant people, and fill this long template, pushed people away from actually conducting it.</p><p>I call postmortem killers ‘silent’, since it’s just one of those things that you figure out without anyone actually telling you about it. They dwindle, and then they die. And that’s bad for your production resiliency.</p><h3>And the silent killers are…🥁</h3><ol><li>When postmortems become a practice of <strong>finding the person or team to blame</strong>, they quickly become an ugly spectacle of defensiveness and finger pointing. That does not allow the trusting, open atmosphere that allows you to objectively review the events and map (together) what can be learned and improved.</li><li>If postmortems are <strong>perceived as red tape</strong>, i.e. when they’re done just to tick the box without the intent of actually learning, people will avoid them or perform the sub-minimal must. By the way, both cases — perception or reality — will result in the same negative outcome.</li><li><strong>Ineffective postmortems</strong> — when a postmortem stays on the surface of the issue and immediate fix, without drilling into the root cause, how it could be avoided or how handling could have been improved, no action items are taken or pursued, it’s as if the postmortem did not happen at all, or even worse as it has been a waste of participants time…</li><li><strong>Lack of visibility</strong> — when a postmortem falls in a forest, and no one hears it. Did it actually occur? Not really. If it only stays in the minds of those who participated in the postmortem, not documented or shared anywhere, the knowledge is lost, and the issue or root cause is likely to occur again (and again).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vTSIr3w_vHeml_80" /></figure><h3><strong>Keep Calm and …</strong></h3><p>Looking at all these killers, I guess most of them can develop in the multi-participant meeting we had in mind to fill out the template. When we reviewed the process with the teams, we understood that they have been conducting postmortems, but these could take the shape of a team sync on the following daily meeting, a corridor chat, or even happen in the mind of the person who fixed the issue.</p><p>Then came the “A ha!” moment — we realized that either of these different postmortem forms is good and achieves the original goal, as long as it’s:</p><ol><li><strong>Visible </strong>— for others to read and comment</li><li><strong>Effective </strong>— i.e. maps the actual root cause(s) and action items that can help avoid recurring incidents or shorten the time to fix</li></ol><p>So rather than pushing more enforcement over the original procedure, that would probably result in a short lived impact and long lived frustration, we decided to make postmortems easier, more accessible and adaptive to the actual day-to-day of our developers.</p><h3><strong><em>Focusing on the “what” rather than the “how”</em></strong></h3><p>We decided to focus on making postmortems more visible and effective and less about the format or form in which they were actually conducted.</p><h3><strong>Automation Automation Automation</strong></h3><p>Whenever a production issue occurs (e.g., rollback, downtime, user complaint), an incident Jira ticket is automatically opened with all known incident details. The production incident can be closed though only after a postmortem has been conducted and updated.</p><h3><strong>Conduct them however you choose to</strong></h3><p>Here was the main change — this is entirely your choice. You can decide if you’d like to hold a big meeting, have a few 1:1 chats, or put your own thoughts on paper.</p><p>You have to fill basic fields on the Incident Jira ticket, such as:</p><ul><li>Description — high level trail of events</li><li>Detected by — testing / monitoring / wix employees/ user complaints</li><li>Resolved by — Rollback / restart / fix / miracle ;) / other</li><li>Duration — time to detection, time to resolution</li><li>Impact</li><li>root cause</li><li>Postmortem — lessons learned &amp; action items</li></ul><p>Once closed it’s automatically published, notifying all subscribers and postmortem angel on call (more on angels in a bit).</p><p>The only exception are high impact incidents, for which we expect the full procedure to take place. We’ve set thresholds of impact and number of teams involved to identify these “high impact incidents”. And they are a fairly small fraction of the overall incidents.</p><p><strong>Visibility Visibility Visibility</strong></p><p>All postmortems are published in a central online board accessible to everyone. Everyone can read and comment.</p><p>Interesting outages and postmortems of large impact are updated in our company weekly newsletter.</p><p>In addition stats on number of postmortem conducted vs open incidents are also tracked and published weekly.</p><h3><strong>Blameless</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bGR31tyWrL7W7KaK" /></figure><p>Creating a blameless culture, just like building trust is an evolution rather than a revolution and takes time and care to build.</p><p>What helped make rather than break blameless postmortems is reiterating the following assumption:</p><blockquote><em>“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.” — </em>Norm Kerth, Project Retrospectives: A Handbook for Team Review</blockquote><p>By reiterating, I mean we reminded this in our company wide training, as well as in the postmortems themselves.</p><p>To make sure this mantra is not just lip service, and becomes the reality, we either appointed a postmortem facilitator (mainly for large meetings) — they facilitate the meeting and makes sure it does not divert to casting blame or finger pointing.</p><p>Another useful practice was teams who agreed on a common team gesture (e.g. waving or shouting “hot potato”) when anyone feels the conversation turns onto a blaming tone — they can shout and help steer the conversation back to it’s blame free, constructive mode.</p><p>But most importantly, in my mind, is for this spirit to be applied top-down in addition to bottom-up — i.e. leadership has to walk the walk and openly talk about their mistakes, as well as congratulate teams for taking ownership of a mistake or issue and it’s mitigation. Rather than condemn teams or individuals for mistakes.</p><p>After a while of encouraging blamelessness and discouraging blame, trust started to build and people became more willing and happy to share and discuss issues.</p><h3><strong>Postmortem Angels</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yZ06_ckGSW1immnP" /></figure><p>Although postmortems are published in a central board, the amount of postmortems was becoming too large for one / few people to review.</p><p>Therefore we set up a special squad of postmortem angels. These are production enthusiastic developers, that in addition to their day job have an on call rotation of reviewing new postmortems published, commenting or having a chat with the relevant team when they have insights, questions or comments on any specific postmortem.</p><p>In many cases, postmortem angels share info across teams on similar issues found and how to tackle them effectively. You can also invite the postmortem angel to your postmortem — so they can assist in real time.</p><p>In addition all postmortem angels meet on a bi-weekly basis to share interesting postmortems, and map common issues and company wide mitigation.</p><p>Common issues could be:</p><ul><li>Lack of tools for troubleshooting / monitoring specific areas</li><li>Recurring issues with external or common internal dependencies</li><li>Lack of knowledge of specific infra setup / behavior</li></ul><p>And mitigation will typically be either a push for a fix or enhancements of our tools, documentation and infrastructure, or training and sharing sessions we conduct across the relevant <a href="https://www.wix.engineering/life-at-wix">guilds</a>.</p><p>Here are a few interesting recent examples mapped by postmortem angels:</p><ul><li>a memory leak in one of our 3rd parties</li><li>recurring mis-configuration of our db clusters</li><li>lack of knowledge / documentation on taking memory dumps/ thread dumps on k8s.</li></ul><p>The angels are not officers, they are facilitators who help you continually improve the quality and efficiency of your postmortem and help spread common lessons learned across the company. They are not enforcing the implementation of the derived action item — this is the responsibility of each team.</p><p>We found that teams do tend to follow up on their own postmortem action items. The reasoning behind it is quite simple: the result of not applying lessons learned is recurrence of incidents and downtime inflicted back at the team and its quality of sleep :) which tends to be the best motivation for improving resilience.</p><h3><strong>What Happened as a Result</strong></h3><p>It took a couple of months for new automation to kick in, and the postmortems angels squad to formalize and start efficiently and collaboratively operating, after which we soon started seeing very positive results:</p><ul><li>Significantly more postmortems were conducted. And the incident to postmortem ratio keeps rising</li><li>Postmortem angels activity initially grew commenting on postmortems, and than (positively) lessened since teams learned to perform more effective postmortems.</li><li>Common issues are more effectively highlighted and addressed.</li></ul><p>And most importantly:</p><p>Teams report a decrease of recurring issues, hence a <strong><em>higher resilience</em></strong> which is what we were all looking to achieve in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*XZD0Og1OcZeAmTZoVRWPHQ.jpeg" /><figcaption>Postmortem KPIs 2018–2019</figcaption></figure><h3><strong>What we’ve learned:</strong></h3><p>For me, this was another reassurance of a leadership-life lesson I truly believe in: that in order to achieve a common goal across the organization we (as leaders) need to enable rather than dictate. hence:</p><ul><li>We need to focus on the “what” rather than the “how” and leave the “how” to the responsibility of each of our talented teams.</li><li>Provide facilitation in the form of tools, training, people and automation aimed to make the process effective, yet seamless and easy so that teams could focus on growing their knowledge and improving product resilience rather than in following resilience procedure.</li></ul><h3><strong>What’s next</strong></h3><p>Although the results have been very promising — we keep scaling (in people and products) and the challenge grows. We need to remain on our toes to verify we don’t stagnate and ensure postmortems are happening and happening effectively.</p><p>Together with our postmortem angels we’re currently drilling into our troubleshooting practices, and looking for ways to improve knowledge and automate more of our troubleshooting &amp; recovery (rollbacks, auto suggested mitigation and automatic mitigation).</p><p>So I don’t know what’s coming next yet- but following my new year’s resolution will definitely keep you all posted.</p><p>Want to share thoughts on postmortems? learn more about <a href="https://medium.com/@avivap/continually-growing-your-engineering-skills-while-scaling-the-organization-the-unique-wix-596536b857ff">Wix’s unique culture</a> or want to join in on the fun, challenge &amp; growth?</p><p>Feel free to reach out to me on <a href="https://www.linkedin.com/in/aviva-starovolsky-peisach-a24a7925/">avivap@Linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=188f09df80fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wix-engineering/triumphing-postmortem-killers-188f09df80fc">Triumphing Postmortem Killers</a> was originally published in <a href="https://medium.com/wix-engineering">Wix Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continually Growing Your Engineering Skills While Scaling the Organization — The Unique Wix…]]></title>
            <link>https://medium.com/wix-engineering/continually-growing-your-engineering-skills-while-scaling-the-organization-the-unique-wix-596536b857ff?source=rss-bbb3208464f------2</link>
            <guid isPermaLink="false">https://medium.com/p/596536b857ff</guid>
            <category><![CDATA[knowledge-sharing]]></category>
            <category><![CDATA[wix]]></category>
            <category><![CDATA[scaling-up]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Aviva Peisach]]></dc:creator>
            <pubDate>Wed, 02 Oct 2019 12:29:27 GMT</pubDate>
            <atom:updated>2019-10-02T12:29:27.031Z</atom:updated>
            <content:encoded><![CDATA[<h3>Continually Growing Your Engineering Skills While Scaling the Organization — The Unique Wix Engineering Culture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*_lnJGgyXj5MZjAAWac9tTQ.jpeg" /></figure><blockquote><strong><em>When you’re part of something extraordinary on a daily basis — you tend to forget, how extraordinary it actually is…</em></strong></blockquote><p>This is why I’ve decided to put on paper, or in a blog post in this case, the story of the <strong>extraordinary Wix Engineering culture</strong>, which I feel lucky to be part of and have helped shape over the last 3 years.</p><p>I’m Aviva Peisach, Head of backend engineering at Wix. With over 20 years experience of Engineering management and VP R&amp;D roles in various startups and enterprise size organizations I can fully appreciate Wix’s unique investment in engineering and want to share some of our secret sauce with you.</p><p>I will not cover all of our engineering practices, since there are too many to fit in a blog post and since they are continually changing and evolving to adapt to our growth and needs.</p><p>Instead, I want to focus on our unique formula for investing 20% of our engineering time in professional and community growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jJlF29pif5goljen" /></figure><p>Not familiar with Wix? Haven’t heard of our amazing website building platform, helping over 160M users fulfil their dream online presence? Visit us <a href="http://www.wix.com/">here</a></p><p>Want to learn more about guilds and our org structure? Read <a href="https://www.wix.engineering/">here</a></p><h3><strong>20% of your time to grow your professional skills</strong></h3><p>Wix is an engineering-focused company: Our founders are engineers and about 50% of Wix’s staff is R&amp;D. Since engineering is the heart and soul of Wix (as well as most of our muscle and brain power), we significantly invest in keeping our engineering in the best shape, by allocating <strong>20%</strong> of every developer’s time to enhance their software engineering skills and build a strong, innovative and collaborative engineering community both within and outside of Wix.</p><p>Can you imagine having 1 day a week, every week, allocated to growing your engineering skills? We do so since we genuinely believe, and also see daily proof that investing this time, makes us better engineers, and significantly increases our velocity, productivity and daily joy of creation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0q2T2o_JIMgXGexh" /></figure><p><strong>So how does it work? How do we invest this valuable time allocation?</strong></p><h3>Guild days</h3><p>Every Thursday, all engineers per site and profession (e.g. Server, Front End, Mobile, Data science, and QA) meet for half a day of training, knowledge sharing and community building activities.</p><p>If we zoom into the server guild for example, which happens to be the guild I head, every guild day is different, but will typically include:</p><p><strong>Project spotlights</strong>: where developers share their recent projects, product, architecture, technologies and challenges they faced and talk about their lessons learned.</p><p><strong>Themed trainings:</strong> every 3–6 months we select engineering topics we’d like to focus on, for example in 2019 we picked <em>Performance, API first, JVM Internals, and TDD</em>.</p><p>Every topic then evolves into a full syllabus which includes talks, workshops, live coding sessions and related use-cases demonstrations.</p><p>Taking the <em>Performance training</em> for example — we had:</p><ul><li>Talks about Performance-oriented design</li><li>Performance pitfalls demos</li><li>Discussed eventual consistency, product tradeoffs, and scale issues to consider for high performance</li><li>Shared tools for monitoring and performance tuning</li><li>Shared war stories on Performance related issues and lessons from our day-to-day</li></ul><p>Now everyone are more of a performance expert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n8wPbwHbBEz-U5JH" /></figure><h3><strong>By engineers, for engineers</strong></h3><p>All guild activities are created by our engineers for our engineers,<strong> </strong>hence every developer gets to contribute content to our guild days. You do not necessarily need to be an expert of a specific subject, you just need to be passionate about learning and sharing your gained knowledge.</p><p>Then we have <strong>Tracks</strong>: this is an hour and a half where we have dozens of different activities you can choose from. Typically, in every guild day you get to select one of 4 different track options. A few examples of the variety of our tracks:</p><p><strong>Mob programing</strong> (pair programming on steroids) — where you get to code in a group and get to hear and voice your coding standards, refactoring practices, Intellij tricks and incremental thinking, and finish off with a working program.</p><p><strong>Design track </strong>— where you share a design dilemma (typically one you’ve faced and solved for one of your products) and do a group design for it, discuss considerations, debate on tradeoffs, provide new perspectives and reach suggested design alternatives.</p><p><strong>Town Halls</strong> — these are mini unconferences where you can raise any issue / dilemma on your mind, e.g. Mocks vs Stubs, how do I effectively estimate my tasks? how should we effectively enforce deprecations? and have a group discussion to hear other people’s experiences and insights, town halls will often suggest guidelines or areas to be addressed by the guild.</p><p><strong>Building your professional brand track</strong> — where you get to invest and consult on your brand presence — this is a sounding board for your next idea for a tech talk or blog post. Where you get feedback from other engineers helping to shape your idea into reality and get more tips on how to grow your engineering brand presence.</p><p><strong>Learn a new coding language — </strong>where you get to learn (group guided or self guided) together. We had Node, Python, GO, Haskell and more to come.</p><p><strong>Pairing &amp; sharing </strong>— where you pair with a developer who’s not in your team and share a recent dilemma or recent project and either do mutual code review, design brainstorming, or prepare for post mortems. The point is to gain and provide a fresh perspective on your day-to-day dilemmas.</p><p>And since tracks change on a weekly basis — so much more, any dream you have on something you’d like to learn and practice together — easily becomes a track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-nUj_V3RSpuJmz5V" /></figure><h3>Guild weeks</h3><p>Every quarter you get to go on a guild week. This is a week away from your team — where you get to pair with engineers who are not in your group and work together on tasks and initiatives outside of your regular backlog.</p><p>You can pick a guild week track, a few examples for popular tracks are:</p><p><strong>Infrastructure track </strong>— where you get to contribute and build the next generation Wix infrastructure, framework &amp; tools, thus both helping to boost overall dev velocity, give your perspective on usability of the framework — adjusting it to actual needs while becoming more proficient and knowledgeable on how Infra works under the hood.</p><p><strong>Join a team</strong> <strong>track </strong>— where you join a different team and work with them for a week. This allows you to gain and provide a different perspective on code, developer practices design and production challenges. Learn another part of our huge product &amp; gain new friends in the guild.</p><p><strong>OSS track </strong>— Where you help open source our products and infrastructure to contribute to the entire engineering community.</p><p><strong>Academy track</strong> — where you get to work on your next guild talk / workshop or next conference talk (many Guild talks tend to become talks you give in global tech conferences) or work on your blog post. Accompanied by our Wix Academy great minds and mentors — helping to boost your talk graphics, stage presence &amp; delivery skills, dry-run and create stunning outcomes.</p><p><strong>Bring your own</strong> <strong>track </strong>— Have an idea or initiative you’re dying to work on and never got the time for? You can bring it to a guild week, pair up with someone and make it happen.</p><p>So many options to choose from, so many worlds and perspectives to explore, all allowing us to break the routine, grow our engineering skills and experience while innovating, contributing and helping others. A perfect Win-Win-Win.</p><p>— —</p><p>The Wix Engineering community and guilds live and evolve beyond the scope of guild-days and guild weeks — with active slack channels, newsletters, shared boards and more — we continually share knowledge and lessons learned. People are always willing to help and consult which eliminate the fear or uncertainty about who or where to ask.</p><p>Having a lively and vibrant engineering community gives each and every member an opportunity to grow and have access to the brilliant minds and experience of our hundreds of talented and passionate engineers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bLTISiQjactaeTti" /></figure><p><strong>Want to learn more about Wix’s unique culture? Want to join in on the fun, challenge &amp; growth? Feel free to reach out to me on </strong><a href="https://www.linkedin.com/in/aviva-starovolsky-peisach-a24a7925/"><strong>avivap@Linkedin</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=596536b857ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wix-engineering/continually-growing-your-engineering-skills-while-scaling-the-organization-the-unique-wix-596536b857ff">Continually Growing Your Engineering Skills While Scaling the Organization — The Unique Wix…</a> was originally published in <a href="https://medium.com/wix-engineering">Wix Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>