<?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 Karen Cohen on Medium]]></title>
        <description><![CDATA[Stories by Karen Cohen on Medium]]></description>
        <link>https://medium.com/@karen_meep?source=rss-8bb3e404f750------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*n28nsTRJhbNtRBEN.jpg</url>
            <title>Stories by Karen Cohen on Medium</title>
            <link>https://medium.com/@karen_meep?source=rss-8bb3e404f750------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:08:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@karen_meep/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[Be A Lover, Not A Fighter]]></title>
            <link>https://medium.com/@karen_meep/how-to-work-with-people-you-hate-5232c4a1eb5b?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/5232c4a1eb5b</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Fri, 03 Jan 2020 08:33:52 GMT</pubDate>
            <atom:updated>2020-01-03T09:17:01.312Z</atom:updated>
            <content:encoded><![CDATA[<h4>In life, you may find yourself in a situation where you need to work with a person you don’t like, let alone hate.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B9pSWM0ENJkBHz6xGj8A0Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@frankbusch?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Frank Busch</a> on <a href="https://unsplash.com/s/photos/fight?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>You could always leave, but how many times will you leave a good paying job, an awesome team or a role that could jumpstart your career when things become uncomfortable with one person?</p><p>(This isn’t to say that you should suffer toxic behavior at work, there’s no excuse for that.)</p><p>Given you want to stay, let’s talk about some tools to help you deal in this situation.</p><h3>Clean Slate</h3><p>Most often, when people work on themselves, they keep it to themselves. Change happens slowly, whereas first impressions happen very quickly.</p><p>Once you’ve made up your mind about a person it’s very hard to break the picture you have about them. As the popular saying goes “a first impression takes seconds to form and years to break”.</p><p>Your challenge is to start a clean slate with this person. Assume they’re doing the work to better themselves a little every single day, and allow them a proper chance to repair their relationship with you. Disregard old experiences and try working with them again. Give them room to be likable and assume good intentions.</p><h3>Look Twice</h3><blockquote>“I do not like this man. I must get to know him better” — Abraham Lincoln</blockquote><p>Things are never black and white, our world is not composed of villains and superheroes. That person you hate has people who love and admire them, they have boons. Make a list of the things you admire about them, look at this list before you see them next.</p><p>Little by little you make an effort to build rapport with them. Say hello and good morning. Initiate short conversations regarding good experiences you know they’ve had recently, ask open ended questions you’re sure will lead to positive answers.</p><h3>Here to Work</h3><p>Repeat after me “I’m here to work”.</p><p>Whatever they’re dealing with is not your problem. You came here to work.</p><p>Put aside their behavior and keep your distance when possible, focus on the work and check out <a href="https://link.medium.com/t1zEC6GwW2">this hack</a> to make your day brighter by focusing on the people you enjoy working with.</p><h3>But Even Though</h3><p>There are some people that make us cringe. Whether we’ve suffered some trauma related to them or they simply rub us the wrong way. Given you’ve decided to keep working within their vicinity, you should keep trying. So that your work environment remains pleasant, and your advancement stays on path.</p><h3>Not for them, for you.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5232c4a1eb5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Quick Turnaround Habit]]></title>
            <link>https://medium.com/@karen_meep/my-quick-turnaround-habit-db08c3ddb4b8?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/db08c3ddb4b8</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[people]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Thu, 05 Apr 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-04-05T06:57:39.226Z</atom:updated>
            <content:encoded><![CDATA[<p>I work with people. A lot of people. Some are an absolute pleasure to work with, others… not so much.</p><p>I’ve developed a habit that helps me recover quickly after a bad experience with a coworker.</p><p>If I find myself feeling drained following a conflict, I go to a colleague I enjoy working with and give them good feedback. I tell them how much I enjoy working with them and why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9AhwBSgvlrIeI6WQeBWNpA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/vCzh1jOyre8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Eli DeFaria</a> on <a href="https://unsplash.com/search/photos/breathe?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This simple act results in two things:</p><ol><li>I quickly shake off any frustration or angst leftover from what happened earlier.</li><li>My colleagues get unsolicited and positive reinforcement for the work that they do.</li></ol><p>If my positive feedback goes towards a coworker who was with me enduring that draining experience, it also signals to them what my beliefs are on acceptable and non-acceptable behavior.</p><p><em>Originally published at </em><a href="https://karenmeep.github.io/peopleware/2018/04/05/quick-turnaround-habit.html"><em>karenmeep.github.io</em></a><em> on April 5, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db08c3ddb4b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GDPR Mastery Guide For Product Managers]]></title>
            <link>https://medium.com/@karen_meep/gdpr-mastery-guide-for-product-managers-1765d6309465?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/1765d6309465</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Sun, 04 Feb 2018 19:32:45 GMT</pubDate>
            <atom:updated>2018-02-13T02:26:03.406Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XQ-Jm8pc0HAsF_hJw0eFhA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/u5Zt-HoocrM?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dayne Topkin</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The General Data Protection Regulation (GDPR) is a European regulation that aims to unify data protection for all. Businesses that are not compliant may get sanctioned up to 4% of the annual worldwide turnover or fined of up to € 20M (the higher of the two), per infringement. If your company processes any information of EU citizens you should start paying attention.</p><p>TLDR; When you collect data linked to a citizen of the EU, they are entitled to know what data is kept, for what purpose, and for how long. Users are entitled to access (“Right To Access”), export (“Right to Data Portability”), change, and permanently delete (“Right To Be Forgotten”) all their data from your systems (<a href="https://medium.com/@GDPR_alliance/the-general-data-protection-regulation-gdpr-in-a-nutshell-2f02290dbd0d">read more here</a>). They should be able to access their data as easily as they entered it in the first place.</p><p>Given the complexity and nuances of the regulation as well as the implications of failing to comply, this is far from an ordinary task for anyone in the company to lead, be it a Product Manager or an Engineer. But fear not, I have written a guide for you.</p><h3>Work closely with a legal team</h3><p>This is where it all starts. Your organization’s legal team must understand the regulation, the product AND the tech. They will decide how to approach the regulation and to what extent.</p><p>You’ll need to master your translation skills. From one end, you should familiarize yourself with all relevant legal terms and communicate them to your colleagues who are unfamiliar with the regulation. From the other end, you’ll need to explain the product and the tech details to your legal team so they can make the tough calls.</p><h3>Research and look for inspiration</h3><h4>Know Your Domain</h4><p>When handling cross-system product tasks, one of your most important assets is domain knowledge. Knowing where possible pitfalls lay will save you a lot of time.</p><p>You can start by documenting anything and everything you can about user data in your system:</p><ul><li>Do you have users who may be EU citizens? Note that the user’s location is by no way an indication of their citizenship and therefore rights.</li><li>Where is data stored? Is the data stored in the EU region? Make an effort to search for unknown data stores such as logs, research data sets, backups and replications, and abandoned services.</li><li>What is the purpose of storing the data? GDPR addresses data minimization, meaning, don’t keep what you don’t need.</li><li>Does your product store Personally Identifiable Information (PII)? (e.g. name, address, birth date, Social Security number)</li><li>Does your product store personal data? (e.g. photos, comments, blog posts, transactions)</li><li>What third party service providers are used? Do they store user data on their databases? Your legal team must make a decision on how to react in case third parties are not compliant.</li><li>What are the product implications of deleting data? Are there UX adjustments that need to be made?</li></ul><h4>Competitor Research</h4><p>As you would for any other product, look into what other companies are doing. However, this may be a challenge if you’ve started working early, as all companies share a similar release deadline.</p><p>When there isn’t a live product you can look at, you should try looking for:</p><ul><li>Support forums: customers will post questions about the upcoming regulation and how said company will be dealing with them. (See <a href="https://ecommerce.shopify.com/c/shopify-discussion/t/gdpr-data-portability-399647">Shopify</a>)</li><li>Support articles: sometimes these go public before the actual product is released to ease customers minds. (See <a href="https://support.wix.com/en/article/general-data-protection-regulation-gdpr">Wix</a>)</li><li>Blog posts and Public Relations announcements: some companies share information on their commitment to abide by regulations (See <a href="https://slack.com/gdpr">Slack</a>).</li><li>Conferences, talks and panels (See <a href="https://www.usenix.org/conference/srecon17europe/program/presentation/mcgarr">SRECon</a>)</li></ul><h3>Decision Time</h3><p>It’s now time to decide what your solution will look like. As usual, first the product aspect and then the tech and architecture. Some questions you should be asking yourself include:</p><ul><li>Which parts can be manual and which must be automatic?</li><li>What does the support model look like?</li><li>If you’re dealing with a large integration project you should also ask: Whose job is it to make sure that the full integration flow works properly?</li></ul><h3>Kickoff</h3><h4>Combined Ownership</h4><p>Depending on the size of the organization, it may be very hard for you to delve into details of each product. This is why you should identify domain owners and empower them to make decisions on their own. You can do this by supplying them with clear guidelines and motivation. Work with security experts to establish security guidelines. Your company should have a policy on how to deal with data breaches and general security guidelines when handling PII.</p><h4>Guidelines</h4><p>Your job is now to guide domain owners on how to implement the regulation. Let your legal team explain what the interpretation and company policy is going to be for each part of the law. This will help owners from different teams make decisions on their own.</p><h4>Communication</h4><p>Use the right channel, medium and most importantly language and terminology when communicating with different personas. Developers may use Slack, while UX, PMs and support agents may use Hangouts, and upper management uses emails. Shared documents are also not a “one size fits all” solution, for example, lawyers would prefer not to use shared documents for fear they may agree to content that will later be changed.</p><p>All the above mentioned personas are needed to make this effort happen, each of them focus on a different part of the picture and bring in different views and knowledge. You’ll need to adapt and practice superb presentation and communication skills.</p><h3>Execution</h3><h4>Communication</h4><p>Have yourself and your team available for questions, on all communication channels, no exceptions. Edge cases will rise and some hard legal decisions will have to be made. You will need to keep translating between the legal team and whoever is on the other end.</p><h4>Keep A Paper Trail</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F6R34rqTupBQxrVe7GS4fw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/8EzNkvLQosk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Maarten van den Heuvel</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Document all slides, documents and decisions made. This is a best practice for running any project, but especially important when there are regulatory related products. It will help you run your project better and later on in understanding the thought process that was made for reaching decisions.</p><p>The research you did when you started is great. Let’s recall the key elements we described there:</p><ul><li>Who generates and processes data.</li><li>What data is stored: PII and Personal Data.</li><li>Where data is stored: Both logical location (BI, logs, databases) and physical location.</li><li>What third party service providers are used?</li></ul><h3>Pre-Release</h3><h4>Support Protocol</h4><p>Work with your support agents to define a protocol for handling requests, as well as complaints and errors in the system. Establishing clear identification and verification process is critical in this case, personal data could be shared with the wrong person in case of an ill defined method. Allow your support agents ample time to practice following this protocol.</p><h4>Content</h4><p>Part of being GDPR compliant is helping the people whose data you hold understand what you’re doing with it. Depending on what your legal team decides, this might mean you’ll have some support articles discussing the types of data you’re collecting and your purpose. Make sure the legal team thoroughly reviews any content that comes out, so as not to be misleading or make your company legally liable.</p><h4>Operations</h4><p>The GDPR Right To Access article states that data shall be supplied in 30 days. You should think about:</p><ol><li>How will you know there’s a problem? Discuss monitoring and alert solutions with your dev team.</li><li>How will problems be dealt with and in what timeframe? An escalation policy for failures in the system must be discussed in advance.</li></ol><h3>Good Luck</h3><p>Exactly what will happen when the regulation goes into effect is still speculatory. There are many interpretations to the regulation and a matching wide range of solutions being implemented as we near the deadline on May 25th, 2018. We’ll get a gradual understanding of the true implications of the regulation as audits and sanctions arise.</p><p>My hope is that this post will help you make sense of GDPR and how you can push such an effort within your organization. I believe that caring for user’s data privacy is a noble mission and that we should all be thankful that the EU is promoting a healthier, safer ecosystem. Hopefully, more countries will follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AcbuHPeMQbwkhxu23HGkIw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/ykKS3a0iutM?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Danka &amp; Peter</a> on <a href="https://unsplash.com/search/photos/journey?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>This story is published in </strong><a href="http://blog.usejournal.com/"><strong>Noteworthy</strong></a><strong>, where 10,000+ readers come every day to learn about the people &amp; ideas shaping the products we love.</strong></p><p><a href="http://blog.usejournal.com/"><strong>Follow our publication</strong></a><strong> to see more product &amp; design stories featured by the </strong><a href="https://usejournal.com/?/utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post&amp;utm_content=karen_cohen"><strong>Journal</strong></a><strong> team.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1765d6309465" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hearts and Minds: Shaping dev culture through technical training]]></title>
            <link>https://medium.com/@karen_meep/hearts-and-minds-shaping-dev-culture-through-technical-training-3c9c6ed49ce6?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c9c6ed49ce6</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <category><![CDATA[onboarding]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Fri, 14 Jul 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-07-16T12:12:57.023Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*FW8ckHsy9j5awpef.jpeg" /></figure><p>Culture is a set of norms, implicit rules and values that a group of people live by. It entails what is right or wrong, acceptable or unacceptable in people’s behavior. Culture is a living, breathing thing, constantly changing and evolving. Wix Engineering is proud of its <a href="http://www.aviransplace.com/2013/10/28/dev-centric-culture-breaking-down-the-walls/">dev-centric culture</a>. It puts us at an advantage in recruiting and retaining top developers.</p><p>As our company grows, we have to make sure we don’t lose our culture. Left unattended, it will turn into ‘<a href="https://kateheddleston.com/blog/the-null-process">null culture</a>’. It’s what happens when no formal culture is put into place. It leaves people guessing what is socially acceptable and creates an impossible environment for those who guess wrong. It’s not the type of environment that makes employees want to stick around.</p><p>One of the ways in which we actively influence and strengthen our culture is through Kickstart, an onboarding course for junior server developers (a similar course exists for junior front-end developers).</p><p>There are more junior developers than there are senior ones yet; most juniors aren’t measured by how they influence a company’s culture. Instead of treating them like influencers and sending them out as agents of the culture a company wants, they end up learning whatever culture is around them, which is not necessarily the culture the company wanted to instill.</p><p>Because we understand the dramatic effects culture can have on our organization, Kickstart is produced with three elements in mind: professional training, culture, and psychological safety.</p><h3>Professional training: the easy part</h3><p>We help new employees learn practical skills so they can start contributing as soon as possible.</p><p>These skills are:</p><ul><li>Scala (our primary programming language)</li><li>Common dev tools &amp; frameworks (CI system, wix-framework, monitoring, etc)</li><li>Dev methodologies (TDD, clean code, etc)</li><li>Wix product &amp; high level architecture</li><li>Where to get help (documentation sources, people to talk to, information channels)</li></ul><h3>How we do professional training</h3><h4>Open specs</h4><p>Deliberately open specifications for features encourage Kickstarters to ask questions and explore trade-offs. This is a recurring theme in the course.</p><h4>Variety of learning materials and techniques</h4><p>Online resources (not tailored), lectures and workshops given by company employees (tailored).</p><h4>Personal mentorship</h4><p>Design reviews, code reviews, and 1-on-1s for setting and following-up on Kickstarters’ personal goals. Read more about this <a href="https://medium.com/@karen_meep/it-s-not-business-it-s-personal-7ed5803be871">here</a></p><h4>Independent long term project</h4><p>A ״nothing-to-production״ project.</p><p>Must haves:</p><ul><li>Simple and clear (but open-ended) product requirements</li><li>Clear definition of done (what)</li><li>Clear guidelines (how): Test first, small commits, deploy often</li><li>Clear expectations and goals</li><li>Challenge: Task should not be too easy — we want to provide a sense of accomplishment, task should not be too hard — as to prevent frustration</li></ul><h3>Culture: the (un)written rules of our organization</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/0*EDIP2tupw_JIXQFb.jpeg" /></figure><p>New employees come in with a load of questions, most of them not about technology at all. Some questions can be anticipated and have well-defined answers (usually around salary, ESPP and other legal factors). Other questions may not have an obvious answer or may have an answer that’s inconsistent throughout the organization. It is up to us to help new employees discover what questions to ask and where (and how) to get answers.</p><p>We invest time and resources into creating an environment of knowledge sharing and personal growth so everyone is informed and can work toward their goals.</p><p>Common questions include:</p><ul><li>When am I expected to show up / leave? How long is lunch time?</li><li>How available do I need to be for production issues?</li><li>How do I communicate with other developers? (Slack) How do I communicate with non-devs? (Hangouts)</li><li>How do I get someone from another team to do something? (usually, a Jira ticket, sometimes personally following-up)</li><li>Can I plan a vacation for 6 months from now?</li><li>How do I make sure I don’t suck at my job?</li><li>Stigma vs Reality: address rumors about your company</li></ul><h3>Techniques for unveiling culture elements</h3><h4>FAQ pages</h4><p>FAQ pages, knowledge bases, readmes and cookbooks — these cover the well-defined questions and answers, anything with company policy.</p><h4>Panels led by course staff</h4><p><strong>A panel with Kickstarters from previous cycles</strong>. Examples of questions asked:</p><ul><li>Describe your group / product / team. What are the main challenges you face in your role?</li><li>How was your onboarding process after Kickstart? Were you assigned a buddy / mentor?</li><li>How much did the course prepare you for working in your teams? How similar is the material to real work?</li><li>Tell us about a bad experience you’ve had since joining the company</li><li>Tell us about something you do at Wix that has nothing / little to do with your role</li><li>Describe workflow, code review process in your teams</li></ul><p><strong>A panel with team leads.</strong> Examples of questions asked:</p><ul><li>What are the main challenges your team faces?</li><li>What kind of tasks do the server devs on your team work on? Who do they work with? (PM? FED?)</li><li>What is the onboarding process for a new team member?</li><li>How do you define success for a new team member?</li><li>What is the process a new task goes through from idea to production?</li><li>How are code reviews done?</li></ul><h4>Informal Q&amp;A</h4><p>Impromptu and informal Q&amp;A with several server guild members during meals, happy hours and coffee breaks.</p><h4>Someones to ask the “stupid” questions</h4><p>Course staff takes notice of terms that may be unfamiliar/unclear to Kickstarters and asks “stupid” questions.</p><h3>Psychological safety: creating a safe space to learn</h3><p>Psychological safety is ‘‘a sense of confidence that the team will not embarrass, reject or punish someone for speaking up, it describes a team climate characterized by interpersonal trust and mutual respect in which people are comfortable being themselves.’’ <a href="http://web.b.ebscohost.com/ehost/detail/detail?sid=e55fd191-97da-4b52-a54d-d1ae6abb0a6e%40sessionmgr111&amp;vid=1&amp;hid=115&amp;bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#AN=2003235&amp;db=bth">Edmondson, 1999</a>.</p><p>Kickstarters come in from different backgrounds and experiences. We rely on feedback from Kickstarters to let us know if and when they don’t understand something or if they’re missing prerequisites for a subject we want to cover. This feedback loop cannot exist without them feeling safe enough to express themselves freely, without being judged.</p><h4>Creating psychological safety</h4><p>Course staff — managers, teammates, mentors, lecturers — need to communicate the following:</p><blockquote><strong>We are Inclusive</strong></blockquote><p>We try our best to make everyone feel included and important.</p><blockquote><strong>We acknowledge our faults</strong></blockquote><p>We are open: we disclose our mistakes and failures, and gain insights from them.</p><blockquote><strong>We ask for feedback</strong></blockquote><p>We explain that we make mistakes and need help. We encourage Kickstarters to ask for help, clarifications, feedback or information.</p><blockquote><strong>We are comfortable with mistakes</strong></blockquote><p>We are comfortable with the idea of failure. Mistakes are inevitable. We can fix what’s broken and learn from our failures. We share and discuss errors and failures.</p><blockquote><strong>We ask questions</strong></blockquote><p>We supply autonomy through questions. Kickstarters are pushed to think for themselves and to propose solutions.</p><p>And, most importantly,</p><blockquote><strong>We are accessible</strong></blockquote><p>In person, by text, Slack, Hangouts, phone call, carrier pigeon, whatever works.</p><p><strong>Repeat, repeat, repeat</strong>: our entire staff — managers, teammates, mentors, lecturers — is on board and communicates these messages through both actions and words.</p><h3>Strength in numbers</h3><p>Developers coming into Kickstart have one clear advantage: they are part of a group, part of a team. Left alone, this team would create their own culture organically, and once the course ends, they would enter the greater fabric of Wix, and continue to affect our engineering culture in unexpected ways. In order to make sure we instill and strengthen the core values of Wix Engineering, teaching Wix’s tech stack and development methodologies must go hand in hand with setting the cultural narrative and establishing psychological safety.</p><blockquote><em>Karen Cohen heads the Wix Kickstart program for server developers.</em></blockquote><p><em>Originally published at </em><a href="https://karenmeep.github.io/onboarding/2017/07/14/Shaping-dev-culture-through-technical-training.html"><em>karenmeep.github.io</em></a><em> on July 14, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c9c6ed49ce6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s not business, it’s personal]]></title>
            <link>https://medium.com/@karen_meep/it-s-not-business-it-s-personal-7ed5803be871?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ed5803be871</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[onboarding]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Tue, 09 Feb 2016 00:00:00 GMT</pubDate>
            <atom:updated>2017-07-15T15:36:11.904Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the second post in a series about my involvement in the developer onboarding program where I work. The first one can be found <a href="https://karenmeep.github.io/on-boarding/2016/01/01/more-than-an-office.html">here</a>.</p><p>This post will focus on three aspects:</p><ul><li>Picking mentors for our program</li><li>Coaching mentors and setting expectations</li><li>Data collection</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*U4ex7GLaNdDb_Jrh.png" /></figure><h3>How we choose mentors</h3><p>Following<a href="https://kateheddleston.com/blog/onboarding-and-the-cost-of-team-debt"> Kate Heddleston’s advice</a>, we select mentors who have been at the company for roughly a year, based on the assumption that they remember what it’s like to be new. This increases the likelihood that they can easily recall any bootstrapping issues or ‘Aha!’ moments they experienced during their onboarding process. Having those memories fresh, we hope would result in them being humble, nice and helpful.</p><p>If that profile cannot be found we then search for an empathetic and kind senior developer or team lead who is equipped with good social and communication skills. Someone we love interacting with on a regular basis and has the bandwidth to dedicate him/herself to the program.</p><p>Bonus: Mentorship is an excellent platform for employees to test the waters of leadership roles. It also pushes forward employees who have not had the chance to shine within their current teams.</p><h3>Coaching mentors and setting expectations</h3><p>All of our mentors go through a week-long mentorship workshop that helps them define their roles, prepare for code reviews and pair programming, develop developers, and most importantly, soft skills.</p><p>Examples of things we discuss during this workshop include:</p><ul><li>Providing feedback: How, when and prerequisites</li><li>Collecting data about the students and the program, as it progresses</li><li>Defining their time commitment</li><li>Showing rather than telling (through code reviews and pair programming)</li><li>Creating a safe learning environment.</li><li>Nurturing critical thinking.</li></ul><h3>Assigning mentors to mentees</h3><p>At the start of the course pairings are made based on members’ CVs and mentors experience. Mentees coming in with more experience will get mentors that have more experience. One on ones start on the first week of the course.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*GveIB4ennhb94zHa.jpg" /></figure><p>Following basic content (Scala, TDD, ..), the group is split into pairs for a three week long project (nothing-to-production). By that time we will have collected enough data about our mentors and Kickstarters. At this milestone we may decide to make changes in the pairings.</p><p>We ask one question:</p><blockquote><em>“How can we make this person better and more powerful than they already are?”</em></blockquote><p>We address the Kickstarters’ strengths and weaknesses, and pair them with mentors that can help bring out the best in them and push them forward.</p><p>Experienced group members are paired with more experienced mentors. Members who receive praise often will be assigned to mentors who do not dispense praise as easily (but provide feedback and further learning opportunities). Members who we think would make larger leaps as a result of positive feedback will be assigned to mentors who give more of it.</p><h3>Data collection (through mentoring sessions)</h3><p>For us, mentors don’t just help their mentees, they also help us identify and fix issues with our program and environment.</p><p>Mentoring sessions are formatted in a way that help us collect data for both short-term and long-term actions:</p><ol><li>Session prep with one of us. This is a quick 2–3 minute summary of what the group worked on since the mentor last visited, with special attention paid to difficult issues that arose during the program, such as good questions or topics that were discussed, but not necessarily understood by everyone. (Lately we’ve been doing this using a Slack channel)</li><li>Private 1:1 with the mentees. This is to get their mentees talking and asking questions they wouldn’t ask in a group setting. We expect our mentors to have a 1:1 with their mentees for one hour every week.</li><li>Code review, held in the shared workspace, preferably with the mentee’s teammate listening. An important note is that most of the work is done in pair programming. We encourage open discussions between mentors, course leads, and anyone who comes into our workspace so mentees hear several opinions and options to solving a problem.</li><li>Lastly, a 5–10 minute checkout process with a course lead to collect feedback concerning issues that require our immediate action. (Lately we’ve been doing this using a Slack channel)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/0*9bGcbXutDEOsdAc7.jpg" /></figure><blockquote><em>Karen Cohen heads the Wix Kickstart program for server developers.</em></blockquote><p><em>Originally published at </em><a href="https://karenmeep.github.io/onboarding/2016/02/09/on-mentors.html"><em>karenmeep.github.io</em></a><em> on February 9, 2016.</em></p><p><em>Originally published at </em><a href="https://karenmeep.github.io/onboarding/2016/02/09/on-mentors.html"><em>karenmeep.github.io</em></a><em> on February 9, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ed5803be871" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to start speaking (in tech conferences)]]></title>
            <link>https://medium.com/@karen_meep/how-to-start-speaking-in-tech-conferences-f64a9f3a84a6?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/f64a9f3a84a6</guid>
            <category><![CDATA[speaking]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[women]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Tue, 19 Jan 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-08-20T15:08:49.207Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been running into too many smart, interesting and opinionated people who want to start speaking but are unsure where to start. At some point I noticed I was repeating myself so I decided I’d write down what I have to say in hopes that it could be helpful to people outside of my immediate social circle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*41SCvPYgEZmPdo_IA1gB3A.jpeg" /></figure><p>Just like no one has life “all figured out”, <strong>no speaker has it “all figured out”. </strong>It takes work.</p><h4>A basic checklist:</h4><ol><li>Decide on a topic</li><li>Write an abstract</li><li>Get your speaker information in order (bio, picture)</li><li>Find conferences with open CFP (call for papers / proposals)</li><li>Submit CFPs</li><li>Follow through and prepare your full talk</li><li>Show up and give an awesome talk</li></ol><h3>Topic</h3><p>Here are a few questions I like to ask in order to jump-start my topic picking process:</p><ul><li>What was a hunch that you had that turned out to be correct? Is there research that backs it up or occurrences of others following the same pattern? Can you explain where your idea came from?</li><li>Same for a hunch that turned out to be incorrect. What led you to that notion? What was the story behind it? What lessons did you learn from the process?</li><li>Is there a tool / library / service that you built or use that makes your life significantly easier? Can it be applied for solving other problems?</li><li>Describe the source and solution for a few bugs that you encountered recently.</li><li>Is there a principle from another discipline that you feel can be applied in your field? (I read a post about an MVP for airlines which I thought was pretty nifty)</li><li>Are you frustrated at work? What would it take to make you happy? What would have to change and why? Happy at work? What exactly makes you happy?</li><li>Lastly, is there a buzzword that you’d like to understand? Run a benchmark or try out a new product / service to help people learn about this new technology.</li></ul><p>Now, I know what you’re going to say (because that’s what I used to say), you’re going to say that you have nothing new to add, that &lt; topic &gt; is simply common sense. Well..</p><blockquote><em>“Common sense is not so common.”</em></blockquote><blockquote><em>– Voltaire, A Pocket Philosophical Dictionary</em></blockquote><p>What makes sense to you will not necessarily make sense to someone else and vice versa. Get over that feeling.</p><h3>Submitting a CFP</h3><p>Most conferences require the following:</p><ul><li>A short bio (make it short and quirky)</li><li>Title and abstract of the talk. The abstract is where you “sell” your talk to conference organizers and attendees of the conference.</li><li>Define the talk format (workshop / lightning talk / 20min / 40min / etc)</li><li>Define the target audience (junior engineers / intermediate / product managers / any / …)</li></ul><p>This is a very basic list. Some conferences may ask you for more information.</p><p>What has worked best for me is sharing a Google Doc of my submission with a few of my friends and have them make suggestions and comments.</p><p><strong>Conferences are constantly looking for fresh speakers.</strong> Some even offer workshops or personal assistance (props to <a href="http://austin2015.apistrat.com/schedule/">APIStrat</a>, <a href="http://scotlandjs.com/cfp">ScotlandJS</a>, <a href="http://lastcall.jsconf.us/call-for-speakers.html">JSConf</a>). <strong>There is no shortage of people wanting to help.</strong></p><h3>Finding places to speak</h3><p>This is a question that comes up often. Here are a few Twitter accounts I follow to find open Call For Proposals:</p><ul><li><a href="https://twitter.com/calltospeakers">Call To Speakers</a></li><li><a href="https://twitter.com/callbackwomen">Callback Women</a></li><li><a href="https://twitter.com/techspeakdigest">Technically Speaking</a> (and mailing list!)</li><li><a href="https://twitter.com/devopsconfs">DevOps Conferences</a></li></ul><p>If you’re interested in a specific conference, you should follow their account. Most conferences have accounts of their own <a href="https://twitter.com/yglfconf">YouGottaLoveFrontEnd</a>, <a href="https://twitter.com/apistrat">APIStrat</a>, <a href="https://twitter.com/statscraft">StatsCraft</a>, <a href="https://twitter.com/elaconf">ELAConf</a>, and <a href="https://twitter.com/signalconf">Signal</a> to name a few.</p><p>I also use <a href="http://lanyrd.com/">Lanyrd</a> to find conferences I may have missed on Twitter, and for tracking <a href="http://lanyrd.com/profile/karencohen/">my speaker history</a>.</p><h3>Content and delivery</h3><ul><li>I like to start with the “Why”. Why did you choose this topic? What makes it interesting (for you and for others)?</li><li>Continue with a basic outline of what you want to say. Start thinking about what your key take-aways are.</li><li>Define the problem / ecosystem / thing before talking about it. Make sure everyone is on the same page and will be able to follow.</li><li>Search for (and reference) existing work. What has been done before? Use the information your find to either summarize it (and add your point of view) or combine a few approaches to arrive at a conclusion.</li><li>Adjust your talk according to who your target audience will be. Your talk may have to change depending on the demographics of the conference. Some conferences share their demographics, with others it’s fairly straight forward, and with some you simply have to either make assumptions or ask.</li><li>Tell a story. Make it interesting, add some drama, excitement and humor. Make your story relatable. Add Add memes, gifs and pop culture.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wC0c63cdgQENZxb0uRB3gA.jpeg" /></figure><h3>Show up and be awesome</h3><p><strong>Everyone wants you to give an awesome talk.</strong> No one comes to (and pays for!) conferences hoping that speakers will suck or give uninteresting talks.</p><h4>Do your thing, even if your thing is weird.</h4><p>The thing about tech conferences is that they’re full of tech people. We’re weird people. We like weird things. You’ve been on the internet, right? You won’t surprise anyone if you act like you normally do. Not only that, you’ll be more at ease not having to act like someone you’re not, you’ll probably even be more relatable (not to mention memorable).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6Egcu-DEXRY%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6Egcu-DEXRY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6Egcu-DEXRY%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/56eadfbfe505a0a1b7a918ee33a7599b/href">https://medium.com/media/56eadfbfe505a0a1b7a918ee33a7599b/href</a></iframe><p><strong>You have something to say. I’m sure of it.</strong></p><p>Need more convincing? Check out <a href="http://weareallaweso.me/">weareallaweso.me</a> and <a href="http://missgeeky.com/category/geeky-2/">How I Got Into Conference Speaking</a>.</p><p><em>Originally published at </em><a href="https://karenmeep.github.io/speaking/2016/01/19/how-you-start-speaking.html"><em>karenmeep.github.io</em></a><em> on January 19, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f64a9f3a84a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2015: A year of speaking, traveling and fooding.]]></title>
            <link>https://medium.com/future-travel/goodbye-2015-1aafa07be796?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/1aafa07be796</guid>
            <category><![CDATA[food]]></category>
            <category><![CDATA[travel-writing]]></category>
            <category><![CDATA[speaking]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Mon, 18 Jan 2016 21:46:24 GMT</pubDate>
            <atom:updated>2018-06-18T19:57:48.890Z</atom:updated>
            <content:encoded><![CDATA[<p>I wrote this post a few weeks ago when everyone on the internet was writing their own year review, I decided I would join in.</p><p>It’s hard not to be a pessimist when I’m constantly looking at how I can get better and achieve more in life. I have to force myself to stop and think about how far I’ve gotten to truly appreciate my accomplishments and be proud of myself.</p><p>Overall, a good year. 4/5 stars, would live it again.</p><h3>My dog died</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*lXLzENVCEYWbSvA2Y9CqeA.jpeg" /></figure><p>This year would have gotten 5/5 had my dog not died.</p><p>Dogo was awesome.</p><p>He was fluffy and cute and gorgeous. He always made me feel better. He died of old age.</p><p>Every now and again I think about him and it makes me smile.</p><h3>I cooked and ate good food</h3><p>My husband and I are at the point where going to restaurants is mostly a let down. Our food is just so much better. I assume that somewhere down the road when we have kids they’ll prefer some god-awful fast food place, as I did when I was a child. When I was in the first grade, my favorite dish was ketchup with a side of Egg McMuffin… or ketchup with a side of anything.</p><p>That being said, here are some restaurants I enjoy eating at again:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xaZkYZtBoioJfRAW8lqn9g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*_tO2nSqsUsWhVAWEYLkIwA.jpeg" /></figure><ul><li><a href="http://www.yelp.com/biz/insomnia-cookies-new-york-11">Insomnia Cookies</a>, NYC. Best chocolate chip cookies I’ve ever had, paired with the best ice cream I’ve ever had (Birthday cake). Ice cream with frosting, genius.</li><li><a href="http://dalidatlv.co.il/">Dalida</a>, Tel Aviv. Favorite dishes are the Polenta, the bone marrow French toast.</li><li><a href="http://www.yelp.com/biz/eiji-san-francisco">Eiji</a>, San Francisco. Probably the best Japanese meal I’ve ever had.</li><li><a href="http://www.tripadvisor.com/Restaurant_Review-g293984-d7788379-Reviews-Truck_de_Luxe-Tel_Aviv_Tel_Aviv_District.html">Truck Deluxe</a>, Tel Aviv. I loved the pulled pork pancakes.</li><li><a href="http://sweetmaplesf.com/">Sweet Maple</a>, San Francisco. OMG THAT MILLIONAIRE’S BACON.</li><li><a href="http://www.tripadvisor.com/Restaurant_Review-g293984-d6762361-Reviews-Nam_Restaurant-Tel_Aviv_Tel_Aviv_District.html">Nam</a>, Tel Aviv. My favorite weekday restaurant. I love their soups.</li><li><a href="http://www.yelp.com/biz/nansen-berlin">Nansen</a>, Berlin. Recommended to me by a local, this place surprises me with it’s unique combinations and tasty food in the land of pork and potatoes.</li><li><a href="https://www.dintaifung.com.au/">Din Tai Fung</a>, Hong Kong (or any other location). Best Xiaolongbao ever.</li></ul><h3>I spent a lot of time traveling</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*jbQgnnLDKXl5gPcecO4gWA.jpeg" /></figure><p>3 x San Francisco</p><p>2 x Stockholm</p><p>2 x Berlin</p><p>1 x New York</p><p>1 x Hawaii</p><p>1 x Amsterdam</p><p>This list seems rather short now.</p><h3>I spent time with friends from all over the globe</h3><p>I’m so grateful to have befriended all these weird, wonderful people. I love that I can point to a country that I’ve been to and say “Yeah, I know &lt;enter name here&gt;, they have some crazy stories / their kid is adorable / they’re a great &lt;enter profession here&gt;”.</p><h3>I went from 0 to keynote speaker in 4 months</h3><p>It all started with my wanting to go <a href="http://apidaysberlin2015.apistrat.com/">APIStrat in Berlin</a>. My boss suggested we both send in talks so the company would be motivated to pay for it. I had my most eloquent friend help me with my abstract, I had my harshest critics review my talk and slide deck.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*EizkdJD-qRhPgfJje2D92g.jpeg" /><figcaption>Wix celebrated the fact employees who submitted CFPs to this big Israeli conference.</figcaption></figure><p>My boss’s boss suggested that I send in CFPs for conferences in Israel as well, which I was hesitant to do as I view Israelies as the toughest audience. I sent in CFPs to all the conferences I wanted to go to and assumed nothing would happen, but most of them got accepted.</p><p>When I was in Berlin, after APIStrat was over I had an idea for a talk. It was one of those moments when everything suddenly clicks and makes sense. Luckily I had my computer with me so I could take advantage of it and write down all of my ideas. I was done with my abstract within 15 minutes, had my husband and a friend review it, then sent it in for Endpoint conference.</p><p>That talk got me the Keynote speaker spot. I nearly peed my pants when I got the email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Ml5IvMzOAEGOy8FiGO-JCw.jpeg" /></figure><p>The conferences I spoke at in 2015:</p><p><a href="http://integratecon.com/">Integrate 2015 Conference + EXPO</a>, <a href="http://endpointcon.com/">Endpoint 2015</a>, <a href="https://www.twilio.com/signal/2015">Signal</a>,<a href="http://apidaysberlin2015.apistrat.com/">APIDays Berlin &amp; APIStrat Europe 2015</a>, <a href="https://devcontlv-march2015.events.co.il/">DevCon TLV</a> , <a href="http://www.seladeveloperpractice.com/">Sela Developer Practice</a></p><p>I’m proud to say that I’m already booked to speak at more conferences in 2016.</p><p>Of course, there were a bunch of other little things that made this year awesome but mentioning them all would have made this post very long.</p><p>Anyway, there’s more to come, that’s for sure.</p><p>Goodbye 2015, you’ve been great.</p><p><em>Originally published at </em><a href="https://karenmeep.github.io/reflection/2015/12/30/year-review.html"><em>karenmeep.github.io</em></a><em> on December 31, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1aafa07be796" width="1" height="1" alt=""><hr><p><a href="https://medium.com/future-travel/goodbye-2015-1aafa07be796">2015: A year of speaking, traveling and fooding.</a> was originally published in <a href="https://medium.com/future-travel">Future Travel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[More than an office]]></title>
            <link>https://medium.com/@karen_meep/more-than-an-office-ea3487ef9ab7?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea3487ef9ab7</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[peopleware]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Mon, 18 Jan 2016 19:21:24 GMT</pubDate>
            <atom:updated>2016-01-19T17:58:49.646Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been interested in culture and on-boarding for a while now, but only recently has my obsession gotten to the point where I am actively doing something about it. An example of this is I started helping out with the developer on-boarding program where I work. This on-boarding program is a 6-week intensive training course focused on product-to-production work-flows and peer &amp; team collaboration, run in a sandbox environment.</p><p>I came in to help run this chapter approximately 3 days before it started. The person running the course was overloaded with production tasks and needed help. We had to make tough decisions fast: Syllabus, learning materials, structure, mentors, …</p><p>The day before the course started I went into the office that was to be the chapters home for the duration of the course. The space was previously used for storage and still felt that way after we cleaned it up. It felt cold, dark and unhappy. Not quite the atmosphere that matches our company’s spirit.</p><p>Our goals for this training course are:</p><ul><li>Promote self learning, self sufficiency</li><li>Team and peer collaboration and learning</li><li>Assimilation into the company culture</li></ul><p>Having read <a href="http://www.amazon.com/Peopleware-Productive-Projects-Second-Edition/dp/0932633439">Peopleware</a>, I hypothesize that the way we arrange their first office directly affects their state of mind and whether or not we are successful in achieving our goals.</p><p>Our most basic possible options are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hh62eq3ADkdX5WD8.png" /></figure><p>The first option suggests there is a hierarchy, it suggests that there is one person (usually standing at the head of the room) that you should learn from. We want to encourage attendees of the course to learn from each other. This setup has the added affect of immediately associating this experience to that of a classroom where you’re bored and unchallenged. That’s not an association we wanted to make.</p><p>The third option is completely out of the question. Attendees of the course are employees from day 1. We trust them to do their job, which currently is learning and growing. Furthermore, having their backs face their teammates promotes self learning but will make it difficult for them to communicate and collaborate with one another.</p><p>We are left with option #2. It provides enough personal space and privacy, while enabling a clear line of vision for collaboration. As an added bonus, it simulates the environment attendees will join once the course is over, it attests that they are treated equally.</p><p>At the end of the 3rd day, post general employee on-boarding (using the product, payroll etc), attendees moved into their first office.</p><p>Watching them move in was a treat. Oddly enough, it worked just as I hoped it would (things never do, so naturally I was surprised): They set up their workstations, some laughed at the web-comics I had so meticulously picked out and hung on the walls, then came the statement I was hoping to hear “I’ll bring some of my things tomorrow to make this spot my own”. <strong>Ding!</strong></p><p>Success. They’re making this their second home.</p><p><em>Originally published at </em><a href="https://karenmeep.github.io/developer%20experience/2016/01/02/side-effects.html"><em>karenmeep.github.io</em></a><em> on January 1, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea3487ef9ab7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Side Effects]]></title>
            <link>https://medium.com/@karen_meep/side-effects-e9dfe4dca05a?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9dfe4dca05a</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[sdk]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Mon, 11 Jan 2016 19:54:48 GMT</pubDate>
            <atom:updated>2016-08-20T14:59:17.623Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*zeE3Rz6CJU2qkd1mHdaS1Q.png" /></figure><p>The “Do One Thing and Do It Well” Unix philosophy is known for being helpful for big product dilemmas, but it is rarely used in our day-to-day when we design the small features that make up our product. One of the first decisions I made as Wix’s SDK product manager is one that haunts us till this day. In order to understand why what I did was so bad I’ll have to explain our ecosystem.</p><p>A Wix website is made out of 3 views: The editor, where a site is created and edited, the My Account section of the site, which is a back-office with tools for managing one’s business, and the viewer, which is accessible to the public only after saving and publishing the site. Wix’s funnel always starts with the editor, where our users create the website their users will see. Up until the first save, the site technically doesn’t exist, there is no back-office and the site is inaccessible to anyone other than the owner.</p><p>On top of the above views lay applications that have parts in each and every view, for example an e-Commerce application, which has the public facing store front that can be modified in the editor, and a back-office portion which lives in the My Account section of the site. These applications use our SDK to interact with the site.</p><p>We got a request from a few applications for an SDK function that returns the URL of the application within the My Account section of the site. They needed this URL so they could easily refer their users to the exact location of the app within the back-office. Once the site has been saved, getting the URL for the application within the back-office is no biggie. The question is, if the site is not yet saved (when a URL cannot be provided) what value should the SDK return? There are a few options:</p><ul><li>Return nothing (undefined).</li><li>Return undefined, have the app register to receive a ‘save site’ event once the user actively choses to save the site, then the app can ask for the URL again (or deliver it via the event information).</li><li>Silently save the site with a temporary name, then return the URL. Back when this feature was requested, the ability to save the site silently and under a temporary name was not available, so this option was out of the question.</li><li>Pop up a window asking the user to save their site, then return the URL.</li></ul><p>Thinking back, what I should have chosen was option #2. However, I made the mistake of choosing option #4, which looks like this:</p><pre>getDashboardAppUrl(function(url) {</pre><pre>    // do something with the URL</pre><pre>});</pre><p>Why was the choice that I made so bad?</p><blockquote>“Rule of Least Surprise: In interface design, always do the least surprising thing.”</blockquote><blockquote>– Unix Philosophy</blockquote><p>I surprised my users. They thought they were doing one thing (getting a URL) when in fact they were (also) doing another (opening a dialog for the user to save their site). I created a bad developer experience.</p><p>Developers using the SDK quickly caught on to the fact that the function also forces the user to save the site, and abused it. They used it to create flows that badly effected our overall user experience. For the longest time (as we avoided making breaking changes) we had to put up with what I had put out.</p><h4>I argue that an SDK function should do one thing and nothing else. It should have no side effects.</h4><p>In the practice of SDKs and APIs, <strong>functions and endpoints that have side effects should be defined as dangerous</strong>, as they are unreliable. It’s risky to rely on code that maybe also does this other thing.</p><p>I am happy to say that a few months ago when I was approached with a similar request, I shot it down.</p><p><em>Originally published at </em><a href="https://karenmeep.github.io/developer%20experience/2016/01/02/side-effects.html"><em>karenmeep.github.io</em></a><em> on January 2, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9dfe4dca05a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should care about engineering culture, even if you’re not a developer]]></title>
            <link>https://medium.com/@karen_meep/why-you-should-care-about-engineering-culture-even-if-you-re-not-a-developer-4708773cd9d?source=rss-8bb3e404f750------2</link>
            <guid isPermaLink="false">https://medium.com/p/4708773cd9d</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Karen Cohen]]></dc:creator>
            <pubDate>Wed, 06 Jan 2016 06:13:40 GMT</pubDate>
            <atom:updated>2016-08-20T15:04:38.918Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*vYeIdsMC_IdIxLkRurrHxA.jpeg" /></figure><p>A few years ago I was not aware of company culture, when interviewing for developer positions I never inquired about it. What I cared about was flexible hours, being measured based on my work (not how many hours I spend at the office), and my salary.</p><p>That kind of thinking landed me in companies I quickly left. The kind where management sets deadlines, the VP of R&amp;D doesn’t know what debugging is, where no tests are written and developers are called to the office in the middle of the night to personally explain production failures, despite having fixed them from home. (Seriously, wouldn’t a phone call have been enough?)</p><p>That’s when I started caring about engineering culture.</p><p>However, having made a transition to product management, I no longer write and deploy code to production. I set the strategy and priorities, I facilitate communication &amp; trust, I listen to ideas &amp; drive execution, and schedule time for bug fixes. So as I no longer occupy an engineering role, I should not care about engineering culture, right?</p><p><strong>Wrong.</strong></p><p>Engineers are the heart and soul of software companies. When they are pushed to do quality work we all win.</p><p><strong>My product will be less prone to errors</strong> as the engineers who implement it have more time to invest in testing. They have time to think about what they’re doing, the implementation, its drawbacks and possible side effects.</p><p><strong>My product design will be better.</strong> A major part of my job is to listen and collect ideas for my product. I encourage, nay, expect, the engineers I work with have an opinion on the feature they’re developing or the bug that they’re fixing. When engineers are racing to meet a deadline they have no time to think outside of their problem domain, and if they’ve been in this routine for long enough they don’t care either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*aq38O7WLPY-uhwut.jpg" /></figure><blockquote><em>“Innovation comes from people meeting up in the hallways or calling each other at 10:30 at night with a new idea, or because they realized something that shoots holes in how we’ve been thinking about a problem”</em></blockquote><blockquote><em>– Steve Jobs</em></blockquote><p>Some of my best ideas came to me when I took a few days to work from home, without the pressure of the daily grind. Innovation can’t happen if you’re racing to meet a deadline or are busy handling support cases all the time.</p><p><strong>My work environment will be happier and more productive.</strong> Ever ask a colleague a question and get an unwarranted, angry reaction? Well, some people are just like that, and you have to deal with it. However, most people are not, unless they’re treated poorly. Want the team to be more productive? They have to be motivated. Motivated to discuss and push new ideas, motivated to help and challenge one another.</p><p>Bottom line is, if you want to work with top notch people to create a top notch product, you should care about how the entire team is treated.</p><blockquote><em>“..what matters is helping all parties understand that the success of the individual is tied irrevocably to the success of the whole.”</em></blockquote><blockquote><em>– Tom DeMarco, Peopleware: Productive Projects and Teams</em></blockquote><p><em>Originally published at </em><a href="https://karenmeep.github.io/culture/2015/12/31/PM-why-you-should-care.html"><em>karenmeep.github.io</em></a><em> on December 31, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4708773cd9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>