<?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 Victoriya Kalmanovich on Medium]]></title>
        <description><![CDATA[Stories by Victoriya Kalmanovich on Medium]]></description>
        <link>https://medium.com/@vicki.kalm?source=rss-df0572f54bf0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*efQLCXRm7jWrXPk5Mj9DYg.jpeg</url>
            <title>Stories by Victoriya Kalmanovich on Medium</title>
            <link>https://medium.com/@vicki.kalm?source=rss-df0572f54bf0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:04:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vicki.kalm/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[Growing Pains: Scaling and Re-architecting Systems Under Fire!]]></title>
            <link>https://medium.com/aspectiva-engineering/growing-pains-scaling-and-re-architecting-systems-under-fire-494be19e0a1d?source=rss-df0572f54bf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/494be19e0a1d</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[data-pipeline]]></category>
            <dc:creator><![CDATA[Victoriya Kalmanovich]]></dc:creator>
            <pubDate>Mon, 25 Jul 2022 08:00:31 GMT</pubDate>
            <atom:updated>2022-07-25T08:00:31.587Z</atom:updated>
            <content:encoded><![CDATA[<p>For the past couple of years, I’ve been leading software teams in a company called Aspectiva. Walmart acquired the company, and as happens to many companies post-acquisition, they must make changes to fit the new world’s new requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ccn_vULsZOkJUXlmIzpJjQ.jpeg" /></figure><p>When Aspectiva first started, we designed and built a reviews collection app that collected reviews from all over the web. The app’s purpose was to bring in volumes of data from which our NLP models could benefit. We built the app in a startup mode where we needed to make things happen fast, using the most straightforward stack we could find, which fit the first software engineer’s expertise. We didn’t have time to waste and needed to get things done quickly. The objective of this app was to get reviews from external sources, a term known as syndication. When building the app, we created one flow where everything was coupled to everything. For example, if you would try to save a review to the DB and the DB connection was lost before saving the flow processing, the whole processing would get lost.</p><p>After Walmart acquired Aspectiva, we weren’t sure if the syndication app would still be an asset worthy of maintaining. Walmart didn’t depend on us to collect reviews (you can learn more about it <a href="https://youtu.be/l7vFR0I04EA">here</a>), we were not acquired based on our syndication capabilities, so we weren’t sure that this app would ever come to use again. Eventually, we found a solid business justification and a meaningful use case where our app could make a huge impact. So not only did we need to keep the app going, we suddenly needed it to be very reliable, scalable, and maintainable.</p><p>So we started by mapping out the main business units the app handled. The next step was to decouple huge components into smaller single-responsibility units within the app. Decoupling the components was essential to properly implement the separation of concerns (SOC) design principle. For example, separating the user handling component into an isolated component helped us when the user handling flow had a critical bug. It was much easier to spot the bug in one specific flow, and we didn’t need to spend great efforts looking for it in a vast complex app. To implement this separation of concerns, we needed to do considerable refactoring while the app was still required to be on the air and very much usable. We started by prioritizing the refactoring necessary for each business unit according to the complexity and overall effect on other components. We needed to balance writing components from scratch and utilizing existing business logic in various components we only needed to extract into their own components. Last but not least was the extensive detailed design and implementation for each business unit, which eventually resulted in a single app that had decoupled business units.</p><p>After we completed this process and our services were neatly mapped out and extracted into separate components within the app — the app broke. Our code was amazing, but the scale we worked with before the acquisition was completely different from the scale we needed to support now. So no matter how beautiful our code was, it didn’t fit the new requirements. We quickly understood that some of our components needed more resources than others. The right way to handle proper resource allocation between our components was to extract them into microservices. It was relatively easy because we already had our services decoupled within the app. Working with microservices in the new environment helped us with better resource allocation per service but, hand in hand, introduced a new set of challenges from the decentralized complex systems world.</p><p>Once we overcame this new set of challenges, we suddenly needed to face the fact that our data collection app, which only served the purpose of collecting reviews in the background, now required to change its face and become user-friendly. At that point, we faced a challenge different from all other challenges we’ve seen before. By that time, we already knew how to scale our products, how to refactor our code efficiently, learned best practices for working with microservices, and how to define new business logic in a way that would be decoupled from all other business logics — but working with users? That’s one hell of a challenge. We started by mapping the user requirements and needs from the system as they used the UI utterly different from how we used it. We had to rethink our metrics and understand how we plan to provide the proper support. Being user-facing introduced us to ramping up our frontend abilities and reading user needs correctly, but also introduced us to urgent user bugs, support SLAs, and defining a good UX. Even though this challenge seemed different than what we’ve done before — we managed to use our strengths to overcome it. We knew our forte was data collection and understanding, so understanding our data helped us understand the user needs better. Our data-driven approach led us to look at the user bugs as an opportunity. We clustered the issues based on similarities, understood which of our services contained the main pain points, and handled them appropriately.</p><p>Our data collection app started as an internal tool built as a proof of concept, continued with significant architecture changes caused by huge demand, and is now pivoting again towards being user-facing. These steps we took at every turn helped us understand our product in view of the new business needs and tame the changes. We managed to re-architect while still being in motion and delivering business value, and we can’t wait to see what new challenges the future holds for us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=494be19e0a1d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aspectiva-engineering/growing-pains-scaling-and-re-architecting-systems-under-fire-494be19e0a1d">Growing Pains: Scaling and Re-architecting Systems Under Fire!</a> was originally published in <a href="https://medium.com/aspectiva-engineering">Aspectiva Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Manager? Here’s How You Can Make Sure Your New Hire Onboards Onto a Bias-Aware Environment]]></title>
            <link>https://medium.com/aspectiva-engineering/software-manager-heres-how-you-can-make-sure-your-new-hire-onboards-onto-a-bias-aware-environment-1ff47b874e79?source=rss-df0572f54bf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ff47b874e79</guid>
            <dc:creator><![CDATA[Victoriya Kalmanovich]]></dc:creator>
            <pubDate>Tue, 31 Aug 2021 10:23:32 GMT</pubDate>
            <atom:updated>2021-09-13T07:52:12.089Z</atom:updated>
            <content:encoded><![CDATA[<p>Mentoring others has always been my passion. On my first year as a software developer, I mentored high school girls, in a program which was designed to make computer science and engineering related fields more accessible to girls. This program started because the numbers of girls who attended computer science and software engineering faculties were low (further reading in Hebrew — <a href="https://www.themarker.com/technation/1.4442835">למה נשים לא לומדות מדעי המחשב</a>). In this program I would go to different schools and talk to girls about computer science. I would explain about computer science courses and what my day to day looks like, as a software engineer in the high-tech industry.</p><p>This one time I came to talk to a group of high school girls. This was almost six years ago, but it was such an important encounter for me that I remember it vividly to this day. There, I talked about how very few women go to computer science and engineering faculties, and that the numbers are low mostly because of conscious and unconscious gender tracking (here’s a short video in Hebrew — <a href="https://www.youtube.com/watch?v=gXkSm14fFCU">כיצד מתחיל להתהוות אי שוויון מגדרי</a>). The girls had a hard time during this part. They said they didn’t feel any different than the boys. They said they make their own decisions and they don’t care what society says. At one point, one of the girls even compared this talk to a similar talk they had in class concerning racism. The girl said that the talk about racism left them all in shock, because prior to that talk — they never even knew they should consider looking at colour or race. They said that creating spaces for girls only — that’s what creates a deeper rift between the genders. Their teacher, who sat with us the whole time, also said that only once we stop paying attention to the issue of gender — there will be equality.</p><p>This talk went down slightly different than I’d expected, but this was a very important discussion and it was even more important because of what had happened next.</p><p>The last part of my presentation was a <a href="https://www.youtube.com/watch?v=bipTWWHya8A">short video on how engineering affects all of our lives</a>. This last part is meant for both boys and girls. This part’s purpose is to make computer science and software engineering more accessible to everyone, since there’s always demand for more engineers. The boys, who were waiting outside up until that moment came back to the class for the video. Usually, after the short video I would ask the class some follow up questions and allow the kids to lead a free discussion.</p><p>Before the boys came in, all the girls were talking freely, raising their hands and having a passionate discussion with each other and with me. Once the boys came into class — not even one hand was raised in the air. Not even one of those girls spoke up. I really wanted to believe the things they said earlier — that they feel their voice is heard, that they can safely state their views and that their behaviour isn’t influenced by the boys in their class. But that wasn’t the case. They felt uncomfortable to raise their hands, uncomfortable to say anything that the boys might mock and uncomfortable sharing any of their thoughts in front of the boys.</p><p>We can hope for equality and inclusion and expect it to just occur. Unfortunately, it won’t occur out of nowhere. There are behaviours and biases we have, which are deeply assimilated within us. When we are aware of these behaviours and biases, that’s when we can really make a difference. Awareness is key, and awareness can only be raised when we actively talk about these topics in the open.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVH1SV5tR451UGWswUqSUg.png" /></figure><p><strong>So that was six years ago, haven’t a lot of things changed since then?</strong></p><p>Some years have passed, I’ve worked in various roles, with different atmospheres, different peers and under different managements. I’m now an engineering manager. Kept mentoring women in high school, in university and in the high-tech industry. And this week, almost six years after the difficult conversation with the school kids, I found myself in the middle of the same discussion — only this time, similar things were being said by experienced female software developers.</p><p>There is a Facebook group I participate in, meant for women in various roles in the high-tech industry. This week a deputy executive officer in one of the startup companies in Israel posted a question. She asked if other group members have reading materials for managers to read, because they’re onboarding the first female developer to one of their teams.</p><p>As a relatively practical question requesting a practical answer, she was aiming to get access to specific materials. What actually happened was a very wide discussion which can be summarised in a short question — “should we even be asking this question in 2020?”.</p><p><strong>So how do we onboard a new member?</strong></p><p>The onboarding process is not easy on anyone. Not for the existing team, not for the new team member’s manager and especially not for the new team members themselves. In a short period of time, the new team member is required to be able to bring professional value and become an impactful member on the one hand, and on the other hand — to be an integral part of the team’s and the company’s culture.</p><p>When I onboard a new team member, I need to create an atmosphere to make this person feel they’re a part of the team. Making them feel that they belong is not an easy task. The team has adjustments to do, the management needs to adjust and the new developer of course has a whole lot of adjusting to do.</p><p><strong>Why is it different when the new member is the only one of its gender on the team?</strong></p><p>Being the sole men on a team of women is a different situation than being an only woman on a team of men, as can be seen here — <a href="https://www.youtube.com/watch?v=M4Pnxh_WdJg">Gender bias in the workplace</a>. Since I’ve had experience with being the only woman on various teams of men most of the time, this is the angle I will present here.</p><p>The topic of gender is generally a topic we avoid addressing at work, but once a new developer joins the team and they’re from a different gender, it’s something that needs addressing. There are many things that can be lost in translation, because of biases and stigmas we carry around with us, sometimes unconsciously. For example, certain behaviours or figures of speech might be interpreted as offensive, or unconscious biases can sometimes affect promotions.</p><p>For those of you who wish to learn more about these, I’ve collected some reading and viewing materials. These materials could be helpful for managers who wish to learn more on inclusive and bias aware work environments.</p><p><strong>What should I read and watch when I’m a manager who wants to create a safe and supportive atmosphere for my team?</strong></p><p><strong>Suggested books:</strong></p><p>1. “Brotopia”, by Emily Chang.</p><p>2. “Lean In”, by Sheryl Sandberg.</p><p>3. “How Women Rise”, by Sally Helgesen.</p><p><strong>Suggested articles:</strong></p><ol><li>“<a href="https://www.mckinsey.com/business-functions/organization/our-insights/women-in-the-workplace#">Women in the Workplace</a>”, a study by LeanIn.org and McKinsey.</li><li>“<a href="https://www.impraise.com/blog/how-performance-reviews-are-reinforcing-gender-bias-5-steps-to-fight-against-it">How Performance Reviews are Reinforcing Gender Bias: 5 Steps to Fight Agains it</a>”, by Impraise.</li><li><a href="http://ambadylab.stanford.edu/pubs/2006Steele.pdf">“Math is Hard!” — The effect of gender priming on women’s attitudes</a>, by Jennifer R. Steele and Nalini Ambady.</li><li>“<a href="https://www.bustle.com/articles/131418-7-examples-of-benevolent-sexism-that-are-just-as-harmful-as-hostile-sexism">7 Examples of Benevolent Sexism</a>”, by Suzannah Weiss.</li><li><a href="https://www.hahem.co.il/sartan/?p=6458">איך לא להיות חרא לנשים בהייטק</a> (Hebrew), by Avgad Yavor.</li></ol><p><strong>Suggested videos:</strong></p><p>1. <a href="https://www.youtube.com/watch?v=B6uuIHpFkuo">Purl</a>, by Pixar.</p><p>2. <a href="https://www.youtube.com/watch?v=JFW2cfzevio">Addressing Unconscious Bias</a>, by McKinsey.</p><p>3. <a href="https://www.youtube.com/watch?v=18uDutylDa4">Why we have too few women leaders</a>, by Sheryl Sandberg.</p><p>4. <a href="https://www.youtube.com/watch?v=3NvkjgbY0M8">How to be an inclusive leader</a> (Hebrew), by Moran Weber.</p><p><strong>Suggested online course:</strong></p><p>1. <a href="https://www.linkedin.com/learning/diversity-inclusion-and-belonging-2/dibs-an-introduction">Diversity, inclusion and belonging</a> (linkedin learning online course).</p><p><strong>Here are 4 tips for managers who want to create a more pleasant and inclusive work environment:</strong></p><ol><li>Be aware of unconscious gender biases when you’re thinking of who to promote.</li><li>When giving feedback, or writing the annual performance review — be aware of what you base your review or feedback on. We sometimes follow social stereotypes and unconscious stigmas, such as: “He speaks up — he’s so assertive” vs. “she speaks up — she’s so aggressive”, or “he’s interrupting the other person while their presenting — he must have a strong opinion” vs. “she doesn’t interrupt any of the discussions — this must mean she doesn’t have a strong opinion, and doesn’t speak her mind”.</li><li>Take into consideration how you divide tasks and try to avoid social stereotypes, for example: Sally, the software engineer, should organise the company’s activities. This is fine when everyone was considered equally, and the decision is made based on the person’s skillset, and not gender stereotypes.</li><li>Work life balance is not a question only women need to ask themselves — as Ruth Bader Ginsburg said:</li></ol><blockquote><em>“When fathers are equal parents to their children, only then will women truly be free”</em></blockquote><p><strong>And finally</strong></p><p>It’s important to be an inclusive leader, but even more important is remember why we do it. We, as software managers, need to be able to create a great work environment for the people on our teams. The many examples I’ve brought here, are meant to show how unconscious biases and social stigmas might escalate situations to places we never intended them to escalate. It’s on us to create good work environments which are good for everyone.</p><p>I hope this article helps understand both why awareness of these topics is so important, and how, as software managers, we can create and keep an inclusive and bias aware environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ff47b874e79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aspectiva-engineering/software-manager-heres-how-you-can-make-sure-your-new-hire-onboards-onto-a-bias-aware-environment-1ff47b874e79">Software Manager? Here’s How You Can Make Sure Your New Hire Onboards Onto a Bias-Aware Environment</a> was originally published in <a href="https://medium.com/aspectiva-engineering">Aspectiva Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Manager? Here’s How You Can Make Sure Your New Hire Onboards Onto a Bias-Aware Environment]]></title>
            <link>https://medium.com/swlh/software-manager-heres-how-you-can-make-sure-your-new-hire-onboards-onto-a-bias-aware-environment-6f7f9364d0fc?source=rss-df0572f54bf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f7f9364d0fc</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[managment-software]]></category>
            <category><![CDATA[gender-bias]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <dc:creator><![CDATA[Victoriya Kalmanovich]]></dc:creator>
            <pubDate>Tue, 22 Sep 2020 06:25:45 GMT</pubDate>
            <atom:updated>2020-09-24T09:10:12.340Z</atom:updated>
            <content:encoded><![CDATA[<p>Mentoring others has always been my passion. On my first year as a software developer, I mentored high school girls, in a program which was designed to make computer science and engineering related fields more accessible to girls. This program started because the numbers of girls who attended computer science and software engineering faculties were low (further reading in Hebrew—<a href="https://www.themarker.com/technation/1.4442835"> למה נשים לא לומדות מדעי המחשב</a>). In this program I would go to different schools and talk to girls about computer science. I would explain about computer science courses and what my day to day looks like, as a software engineer in the high-tech industry.</p><p>This one time I came to talk to a group of high school girls. This was almost six years ago, but it was such an important encounter for me that I remember it vividly to this day. There, I talked about how very few women go to computer science and engineering faculties, and that the numbers are low mostly because of conscious and unconscious gender tracking (here’s a short video in Hebrew — <a href="https://www.youtube.com/watch?v=gXkSm14fFCU">כיצד מתחיל להתהוות אי שוויון מגדרי</a>). The girls had a hard time during this part. They said they didn’t feel any different than the boys. They said they make their own decisions and they don’t care what society says. At one point, one of the girls even compared this talk to a similar talk they had in class concerning racism. The girl said that the talk about racism left them all in shock, because prior to that talk — they never even knew they should consider looking at colour or race. They said that creating spaces for girls only — that’s what creates a deeper rift between the genders. Their teacher, who sat with us the whole time, also said that only once we stop paying attention to the issue of gender — there will be equality.</p><p>This talk went down slightly different than I’d expected, but this was a very important discussion and it was even more important because of what had happened next.</p><p>The last part of my presentation was a <a href="https://www.youtube.com/watch?v=bipTWWHya8A">short video on how engineering affects all of our lives</a>. This last part is meant for both boys and girls. This part’s purpose is to make computer science and software engineering more accessible to everyone, since there’s always demand for more engineers. The boys, who were waiting outside up until that moment came back to the class for the video. Usually, after the short video I would ask the class some follow up questions and allow the kids to lead a free discussion.</p><p>Before the boys came in, all the girls were talking freely, raising their hands and having a passionate discussion with each other and with me. Once the boys came into class — not even one hand was raised in the air. Not even one of those girls spoke up. I really wanted to believe the things they said earlier — that they feel their voice is heard, that they can safely state their views and that their behaviour isn’t influenced by the boys in their class. But that wasn’t the case. They felt uncomfortable to raise their hands, uncomfortable to say anything that the boys might mock and uncomfortable sharing any of their thoughts in front of the boys.</p><p>We can hope for equality and inclusion and expect it to just occur. Unfortunately, it won’t occur out of nowhere. There are behaviours and biases we have, which are deeply assimilated within us. When we are aware of these behaviours and biases, that’s when we can really make a difference. Awareness is key, and awareness can only be raised when we actively talk about these topics in the open.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XuGNkiKIWCNKa3Kkk42ADQ.jpeg" /></figure><p><strong>So that was six years ago, haven’t a lot of things changed since then?</strong></p><p>Some years have passed, I’ve worked in various roles, with different atmospheres, different peers and under different managements. I’m now an engineering manager. Kept mentoring women in high school, in university and in the high-tech industry. And this week, almost six years after the difficult conversation with the school kids, I found myself in the middle of the same discussion — only this time, similar things were being said by experienced female software developers.</p><p>There is a Facebook group I participate in, meant for women in various roles in the high-tech industry. This week a deputy executive officer in one of the startup companies in Israel posted a question. She asked if other group members have reading materials for managers to read, because they’re onboarding the first female developer to one of their teams.</p><p>As a relatively practical question requesting a practical answer, she was aiming to get access to specific materials. What actually happened was a very wide discussion which can be summarised in a short question — “should we even be asking this question in 2020?”.</p><p><strong>So how do we onboard a new member?</strong></p><p>The onboarding process is not easy on anyone. Not for the existing team, not for the new team member’s manager and especially not for the new team members themselves. In a short period of time, the new team member is required to be able to bring professional value and become an impactful member on the one hand, and on the other hand — to be an integral part of the team’s and the company’s culture.</p><p>When I onboard a new team member, I need to create an atmosphere to make this person feel they’re a part of the team. Making them feel that they belong is not an easy task. The team has adjustments to do, the management needs to adjust and the new developer of course has a whole lot of adjusting to do.</p><p><strong>Why is it different when the new member is the only one of its gender on the team?</strong></p><p>Being the sole men on a team of women is a different situation than being an only woman on a team of men, as can be seen here — <a href="https://www.youtube.com/watch?v=M4Pnxh_WdJg">Gender bias in the workplace</a>. Since I’ve had experience with being the only woman on various teams of men most of the time, this is the angle I will present here.</p><p>The topic of gender is generally a topic we avoid addressing at work, but once a new developer joins the team and they’re from a different gender, it’s something that needs addressing. There are many things that can be lost in translation, because of biases and stigmas we carry around with us, sometimes unconsciously. For example, certain behaviours or figures of speech might be interpreted as offensive, or unconscious biases can sometimes affect promotions.</p><p>For those of you who wish to learn more about these, I’ve collected some reading and viewing materials. These materials could be helpful for managers who wish to learn more on inclusive and bias aware work environments.</p><p><strong>What should I read and watch when I’m a manager who wants to create a safe and supportive atmosphere for my team?</strong></p><p><strong>Suggested books:</strong></p><p>1. “Brotopia”, by Emily Chang.</p><p>2. “Lean In”, by Sheryl Sandberg.</p><p>3. “How Women Rise”, by Sally Helgesen.</p><p><strong>Suggested articles:</strong></p><ol><li>“<a href="https://www.mckinsey.com/business-functions/organization/our-insights/women-in-the-workplace#">Women in the Workplace</a>”, a study by LeanIn.org and McKinsey.</li><li>“<a href="https://www.impraise.com/blog/how-performance-reviews-are-reinforcing-gender-bias-5-steps-to-fight-against-it">How Performance Reviews are Reinforcing Gender Bias: 5 Steps to Fight Agains it</a>”, by Impraise.</li><li><a href="http://ambadylab.stanford.edu/pubs/2006Steele.pdf">“Math is Hard!” — The effect of gender priming on women’s attitudes</a>, by Jennifer R. Steele and Nalini Ambady.</li><li>“<a href="https://www.bustle.com/articles/131418-7-examples-of-benevolent-sexism-that-are-just-as-harmful-as-hostile-sexism">7 Examples of Benevolent Sexism</a>”, by Suzannah Weiss.</li><li><a href="https://www.hahem.co.il/sartan/?p=6458">איך לא להיות חרא לנשים בהייטק</a> (Hebrew), by Avgad Yavor.</li></ol><p><strong>Suggested videos:</strong></p><p>1. <a href="https://www.youtube.com/watch?v=B6uuIHpFkuo">Purl</a>, by Pixar.</p><p>2. <a href="https://www.youtube.com/watch?v=JFW2cfzevio">Addressing Unconscious Bias</a>, by McKinsey.</p><p>3. <a href="https://www.youtube.com/watch?v=18uDutylDa4">Why we have too few women leaders</a>, by Sheryl Sandberg.</p><p>4. <a href="https://www.youtube.com/watch?v=3NvkjgbY0M8">How to be an inclusive leader</a> (Hebrew), by Moran Weber.</p><p><strong>Suggested online course:</strong></p><p>1. <a href="https://www.linkedin.com/learning/diversity-inclusion-and-belonging-2/dibs-an-introduction">Diversity, inclusion and belonging</a> (linkedin learning online course).</p><p><strong>Here are 4 tips for managers who want to create a more pleasant and inclusive work environment:</strong></p><ol><li>Be aware of unconscious gender biases when you’re thinking of who to promote.</li><li>When giving feedback, or writing the annual performance review — be aware of what you base your review or feedback on. We sometimes follow social stereotypes and unconscious stigmas, such as: “He speaks up — he’s so assertive” vs. “she speaks up — she’s so aggressive”, or “he’s interrupting the other person while their presenting — he must have a strong opinion” vs. “she doesn’t interrupt any of the discussions — this must mean she doesn’t have a strong opinion, and doesn’t speak her mind”.</li><li>Take into consideration how you divide tasks and try to avoid social stereotypes, for example: Sally, the software engineer, should organise the company’s activities. This is fine when everyone was considered equally, and the decision is made based on the person’s skillset, and not gender stereotypes.</li><li>Work life balance is not a question only women need to ask themselves — as Ruth Bader Ginsburg said:</li></ol><blockquote>“When fathers are equal parents to their children, only then will women truly be free”</blockquote><p><strong>And finally</strong></p><p>It’s important to be an inclusive leader, but even more important is remember why we do it. We, as software managers, need to be able to create a great work environment for the people on our teams. The many examples I’ve brought here, are meant to show how unconscious biases and social stigmas might escalate situations to places we never intended them to escalate. It’s on us to create good work environments which are good for everyone.</p><p>I hope this article helps understand both why awareness of these topics is so important, and how, as software managers, we can create and keep an inclusive and bias aware environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f7f9364d0fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/software-manager-heres-how-you-can-make-sure-your-new-hire-onboards-onto-a-bias-aware-environment-6f7f9364d0fc">Software Manager? Here’s How You Can Make Sure Your New Hire Onboards Onto a Bias-Aware Environment</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Have you tried turning your software team’s identity off and on again?]]></title>
            <link>https://medium.com/free-code-camp/have-you-tried-turning-your-software-teams-identity-off-and-on-again-a06aad5f1f50?source=rss-df0572f54bf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a06aad5f1f50</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Victoriya Kalmanovich]]></dc:creator>
            <pubDate>Fri, 01 Feb 2019 17:13:35 GMT</pubDate>
            <atom:updated>2019-02-01T17:13:35.549Z</atom:updated>
            <content:encoded><![CDATA[<p>This series portrays my experience as an R&amp;D group leader of a group that has the same behavior as a failing startup. In my last two blog posts, I’ve presented a short background regarding the developers and the technologies. This blog post will deal with the vague definition of a group’s identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ei2UmVQ2cAA2FM2Vy8Pi-A.jpeg" /></figure><p>In <a href="https://medium.com/@vicki.kalm/overcoming-a-technological-gap-a-horrible-circumstance-or-a-creative-adventure-ad3e97e64e44">my last blog post</a>, I portrayed an image almost too good to be true. An image of a productive software group, full of energy and hunger for projects. I knew I must look away from newly gained success and only into the problems, however unfortunate that made me feel.</p><p>On the one hand, I felt the need to present the milestones I’ve created to restore some kind of productivity. I wanted to show the boss all the recent successes — the coding methodology, working regulations and other concepts we’ve begun implementing. I wanted to present the training concepts and procedures we’ve established. I wanted to present the strong cooperation I’ve led with another organization. This cooperation granted an opportunity to combine the organization’s knowledge pool and create better professional training for my group. On top of these, one of our projects was accepted to an acceleration program. I really wanted to show that off as well.</p><p>But I knew this image would soon fade unless I continued targeting the main issues. The primary issue was this next hard truth. The group didn’t have a strong basis and it was just a matter of time until it might collapse again. I identified it as the group’s lost identity.</p><h4>What is a group identity?</h4><p>When we reach a point in life where we seek our unique identity we look into various questions. Where am I from? What is my heritage? Who influences me? What’s exciting for me? What’s the reason I wake up in the morning? These questions helped me shape my personal identity both as a human being and as a leader. The same process happens one way or another in every organizational structure.</p><p>Defining a group’s identity must happen the moment a manager takes the reins. They must look at the group’s responsibilities and define each group member’s position. It clears many things up. It provides clear borders regarding the manager’s and the developers’ responsibilities.</p><p>This process must occur at the group manager’s level and even higher. It is rare that a complex organizational understanding such as an identity can depend on the team leads’ scope or lower. It is also unfair to the team leads, who already have enough on their plate.</p><p>As you may recall from my previous blog post, I talked about the vicious zero-products cycle. This cycle started somewhere, so I started retracing the group’s steps. I realized that the moment the last official product version was released was the breaking point. This was the point where there was no clear view on what the group’s main objective was, what was its purpose and what was the product it was responsible for delivering.</p><h4>What was the main objective?</h4><p>The main objective was software and system maintenance for a very complex system. In order to perform software maintenance on such a large amount of code, a developer must work on the code. The developer must understand it and get to know its genius functions, but also its inherent faults and flaws. The developer must feel the code. They can only gain this feeling through massive research and deep understanding of procedures within the system.</p><p>In my view, it is impossible to maintain the entire system simultaneously, as a result of a small number of maintenance dedicated developers and a very serious lack of knowledge. So I declared that maintaining specific domains every year was good enough for us. The alternative would be scattered maintenance that would only lead to more gaps in the long run.</p><p>Let’s look at a simple example such as inserting an image on a screen. This is easy in modern systems written in readable code that follows proper coding methodologies.</p><p>In our case, to insert a feature, the developer needed to follow more complex steps. They would research the entire screen’s code and the entire code of screens that might be affected by the change. It might take up to a month of research. After the research would’ve developed some conclusions. They would try to decipher the relevant piece of the system’s architecture and find a few ways to implement image insertion.</p><p>In parallel, and this is the important part, the developer must document EVERYTHING. Every difficult method. Every process they discover. Every architecture or network insight they have. Every unusual phenomenon and its investigation all the way to its origin. This is crucial since the existing documentation and most of the written code are barely readable.</p><p>The objective seems very straightforward, but regulated documentation and code maintenance is not the only thing that defines a group’s identity. The group has to have a purpose. Our purpose went missing.</p><h4>Where did the purpose go?</h4><p>At some point, software maintenance was performed under no regulations and slowly went out of the professional focus. What started flowing instead were side projects. Side projects became the main objective. Whenever a client approached one of the teams, in need of a quick fix, the group would pivot in that direction. People were working on side projects for the sake of working. The difficult yet crucial maintenance was completely abandoned.</p><p>When I started my position as group leader, almost every group member told me they didn’t know exactly what the group was actually meant to do. They felt they had no real goals when they came to work. Side projects scattered the purpose.</p><h4>Why do we sometimes need to manage our clients?</h4><p>A software group cannot blindly do what the client wants. Especially when the client changes their mind frequently. For example — back when I was a software developer, my team and I were working on a navigation project similar to “Waze”. Our product owner kept requesting changes that made no difference whatsoever to the system’s functionality. It was always a request to change button colors or move toolbars around the UI. This kept the team from making any progress for a very long time.</p><p>In my software group, the problem was on a larger scale. The group didn’t have one indecisive client. It had a few separate clients and each client pulled in their own direction. There wasn’t one integrating factor, looking at the larger picture and managing the clients and the projects. For a long time, the group worked through a queue — first client in meant first project the group developed. Therefore, almost any type of project could be brought to the group. In time the group began dealing with QA, IT and even hardware issues, rather than software development.</p><p>Retrieving the purpose, and consequently the motivation, was an ongoing process. It began with a definition — I’ve defined, along with my team leads, our projects. We’ve prioritized them in accord with our clients’ demands, thus setting a roadmap we will not slip from, as happened in the past. This roadmap indicated our objective — system’s software maintenance was declared our purpose.</p><p>We’ve added one more project to the roadmap, a second main project, related to the system but not directly. It added to the purpose since it had great unimplemented potential. I believed it would be great for PR and to enhance the developers’ belief in their own skills. This dedicated roadmap focused the teams. We knew that by the end of the year we needed to deliver two products end-to-end.</p><p>Setting the professional compass was important. The bigger problem was regaining the developers’ trust in the group. After so many years, my developers — both experienced and new — had no fuel nor will to work. After some of my scheduled one on one talks, I mapped each developer’s strengths. If for example, one developer was really good at research — I let them do the research.</p><p>After mapping individual strengths, I mapped team strengths. Some paired programming was performed in order to strengthen some developer’s self-esteem. We’ve held a professional workshop for team leads, to strengthen management abilities. I addressed the issues I picked up when I observed the programming process and the issues the developers themselves had presented.</p><h4>So how was the identity restored?</h4><p>By finding a definition and restoring order. We’ve defined our field of expertise. I’ve put borders around our designated projects and let no other project cross that border. Limited the issues we work on (no more hardware issues!). Made sure there was proper usage of coding methodologies and version control. Made everyone document their work. Strengthened each programmer’s strengths. Sharpened the team leads’ set of soft skills.</p><p>I targeted both professional and personal values in order to restore the group’s inevitable software DNA.</p><p>The difficulties of leading changes in an unforgiving environment, leading innovation instead of sinking and how to survive as a young female in a very ego driven male environment? Stay tuned, all this and more as the series unravels!</p><p><a href="https://medium.com/@vicki.kalm/how-can-corporations-heal-a-dying-software-group-1abe03d8a492">Part 1 — How Can Corporations Heal a Dying Software Group?</a></p><p><a href="https://medium.com/@vicki.kalm/overcoming-a-technological-gap-a-horrible-circumstance-or-a-creative-adventure-ad3e97e64e44">Part 2 — Overcoming a Technological Gap — a Horrible Circumstance or a Creative Adventure?</a></p><p><a href="https://medium.freecodecamp.org/how-i-started-the-process-of-healing-a-dying-software-group-d5610cf416bc">Parts 1+2 — How I started the process of healing a dying software group</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a06aad5f1f50" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/have-you-tried-turning-your-software-teams-identity-off-and-on-again-a06aad5f1f50">Have you tried turning your software team’s identity off and on again?</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I started the process of healing a dying software group]]></title>
            <link>https://medium.com/free-code-camp/how-i-started-the-process-of-healing-a-dying-software-group-d5610cf416bc?source=rss-df0572f54bf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5610cf416bc</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Victoriya Kalmanovich]]></dc:creator>
            <pubDate>Wed, 19 Dec 2018 22:02:28 GMT</pubDate>
            <atom:updated>2018-12-19T22:02:28.055Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine yourselves managing a software development group which consists of very strong programmers. They research and develop one of the most complicated systems known to mankind. They write and write and write code — but eventually, no one wants software versions of that code. No one knows what they actually do day to day. The truth is — no one believes in your group.</p><p>This year I became a software development group manager, and I’ve had to deal with 15 employees in 3 teams who, from the moment they arrive until the moment they leave the office — feel transparent.</p><p>This is my story, which will illustrate my journey as group lead, from a moment before closing the group, to a well appreciated, needed and a formal authority in the corporation. In this blog post, I will present the group’s background including a few major failure points which occurred in my group — and which can occur in many big corporations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f5D1TCdEqjeuElPkPY2-wQ.jpeg" /></figure><p>In my professional past, I developed defense systems as a software engineer, managed autonomous vehicle projects for very big clients, developed autonomous vehicles navigation algorithms and organized events as a data science community manager. Becoming a software group manager, after a very technical professional past, was not an easy task.</p><p>The more problems I’ve diagnosed in my group, the more it seemed like a failing startup — there was no money, no client, no motivation. I arrived a moment before shut down.</p><p>Before managing my group, I heard of it from many different sources. The main idea was its low productivity and a grand waste of human resources. I had to try and understand — how can such a talented group of software engineers not get their well-deserved recognition? How can they work on such important projects and still seem to be wasting theirs and the company’s time?</p><p>The more hours I spent at the office, the more challenges I discovered within the group.</p><p>I felt that in order to succeed, I needed to reach out to the people as my first step, before digging further into the projects. I scheduled one-on-one talks with everybody and a separate talk for each team. My intention was to map out my people’s thoughts, strengths and professional interests, in order to be as impartial as I could to gossip.</p><p>In the meantime, I started mapping out all the projects the group had been working on at the time, and the picture I got was so scattered and misguided that none of them actually knew what the group’s main objective was.</p><p>It was very clear to me that over the years the group has lost its professional identity.</p><h3><strong>How does a group lose its identity?</strong></h3><p>When the group was established, it had a very well defined purpose and a great value as it was beneficial for the client. It was in charge of application hosting platforms and applications which were consequently hosted upon these platforms.</p><p>After the final version of each of the developed products was released, the spiraling began. The group received projects that had nothing to do with its main purpose, they began supporting technical issues in order to help clients other than the main client, and worst of all — the group stopped releasing versions. Unfortunate managing choices let the group’s already bad reputation deteriorate immensely. Its identity had been completely wiped out.</p><p>I immediately devised a plan which consisted of freshening up the teams, teaching proper agile development methodology and strengthening the teams’ leads. On the verge of change, I decided to wait. I had spotted a hostile group member.</p><p>It was a programmer who the former group manager put in a team lead position. He got to manage the strongest team of all three. As a team lead, he somehow managed to wreak havoc upon the entire group and be completely unproductive.</p><p>I knew I had to deal with the human resources problem before I headed on to solving the other issues.</p><p>To sum up some of the damage he caused over the years:</p><ul><li>he set irrelevant assignments to his group members</li><li>disappeared for large amounts of time during the day</li><li>failed to complete his assignments as a programmer and his responsibilities as team lead</li><li>created an atmosphere filled with fear from approaching him</li><li>and a most serious incident — deleted large amounts of code that his team members had been working on for the past year and a half.</li></ul><p>I will present one example in greater detail.</p><p>During assignment planning, he received an assignment to organize the project’s GIT. Up until that time, the GIT was a great big mess that consisted of two different project versions. Since the team lead (let’s name him Steve for the sake of the example) was the most experienced senior developer, we all agreed it would be most effective if he got the assignment, since it would take him the least amount of time and efforts.</p><p>After a month, in which we’d held a few status meetings where he spoke of his progress, we found out that not only did the GIT stay exactly the way it was, but he also ordered his team members to develop upon the older version — thus creating unnecessary integration problems. Everywhere else a worker like that would’ve been immediately fired. Unfortunately, I could not fire him nor take any other disciplinary measure against him.</p><p>This story with Steve reminded me of an employee I had as a regional manager for a non-profit organization a few years back. Let’s name her Suzy. As a regional manager, I was in charge of managing my branch managers on the one hand, and on the other hand developing our region’s community and business relations.</p><p>Suzy was one of my employees. In time, we realized that being a branch manager lead her to have a strong thirst for power. She took on many responsibilities, treated her branch co-managers as her employees, disrespected her co-workers, and basically bossed everyone around.</p><p>No one had the guts to stand up to her for years, because it was a voluntary job, and we didn’t want her to use her rage against the organization. Every action had to be taken very delicately. I’d tried changing the atmosphere, adding bonding activities and a few other approaches. When we saw nothing changed her behavior, I decided to take more drastic measures.</p><p>I started actively managing their meetings and assigned more responsibilities to the other managers. I reduced the amount of power she supposedly had, by letting the other managers talk to the contacts she usually contacted. My response to the problem was decentralization, which ultimately led to a healthier work environment.</p><p>Going back to Steve — the situation was much more extreme and involved one of the company’s crown jewel projects. It was clear to everyone that Steve, much like Suzy, had a thirst for power. He always requested more people for his team, and it didn’t matter to him what happened next — he just needed to be everyone’s boss. At management meetings, he had to cancel out every idea but his own, and he was always so stubborn he never really listened to his peers.</p><p>Since I could not fire him, but could not keep him either, I started looking for a different position for him, far from my group. Simultaneously, I started decentralization. I gave him and his team fewer responsibilities and every new group member was forwarded to one of the other two teams.</p><p>Throughout the process, I gave him performance feedback, hoping his behavior would change. His stubbornness and thirst for power prevented any change, and when he felt his power was slipping away he got angry — and so we reached a turning point.</p><p>At this point, Steve and I finally had a shared interest. He wanted to seek power elsewhere, and I wanted him to seek power elsewhere. I knew he was one of the group’s many setbacks, but I also knew that dealing with any other setback before I got rid of him would be futile.</p><p>Peter Drucker once said: “Management is doing things right, leadership is doing the right things”. This thought is what kept me going in the direction I believed was right. I saw in my mind’s eye an effective software group, and I knew I had to work very hard and convince many people I was going in the right direction — in order to accomplish what I’d started. I chose to fight instead of to comfortably sit in my office and watch the group suffer defeats.</p><p>To make a long story short, I got rid of Steve, he moved to another group, and I began mapping the faults and behavioral patterns I was looking forward to dealing with. As we are an R&amp;D group, I started with the technology.</p><h3><strong>Overcoming a technological gap — a horrible circumstance or a creative adventure?</strong></h3><p>My next step was to figure out how to overcome technological gaps. When I say technological gaps, I don’t mean switching from Java to Node.js, oh no. We’re talking here about obsolete systems, ancient coding language (worse than hieroglyphs, trust me on that one), an impossible coding environment, no coding methodology, plenty of spaghetti code etc. The systems were implemented in such a way that there was no possible hardware upgrade without just writing everything from scratch.</p><p>I began solving each problem separately. I found several solutions to each problem and began prioritizing. For example, the coding environment issue. The system’s coding environment was so old, that even the company that designed it had already been shut down for many years. It was designed in a certain way that even the simple things were in fact very counter-intuitive.</p><p>The compilation process, for one, had to be done very carefully. In order to compile one file, a programmer had to find all the files that were affected by it, all the files it might affect and files that are somehow related to it. They needed to find all these files manually, and run them through some other processes, and then when that was finally over with- they needed to wait for a few hours for the compilation to be complete. This was the least of all problems; therefore it was the first issue to attend to.</p><p>After massive research and thought, we found an elegant solution, that was immediately applicable. We found a way to automate the previously manual process through a third party application. However, an easy compilation was not the main goal here. My goal was to target all the faulty infrastructures, find and implement a simple solution, yet constantly remind the client we needed more budget to solve the more serious infrastructure issues.</p><p>This proved to be a path worth pursuing, since each problem we’ve solved uncovered more issues concerning the architecture and design of the system. This project was doomed the moment the papers were signed, but I hadn’t given up hope.</p><p>I started sniffing around, trying to find an interesting project related to our system. I found a project that could solve a very serious problem that we could add to the main system.</p><p>This decision provided two things: first, the client understood there was more potential to the group than he had previously thought. And second, that we could add infrastructure upgrades as a part of the new project’s budget.</p><p>This had more value than just money — the developers began feeling the new spirit, they felt more needed, and they began working with extra willpower on infrastructure projects, since they knew it was meant to serve a project the client believed in. This led to an effective work environment, where people felt more productive and felt more inclined to share creative solutions.</p><h3><strong>At this point, you might ask — where is our DevOps team?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QO_R3RCYti7-Sf3rLYsP3g.jpeg" /></figure><p>Well, to tell you the truth — there was no designated DevOps team, nor was there a QA team, a product manager, a proper project manager and so on. We had to rely on ourselves and to be completely honest — but it was better that way.</p><p>In my opinion, distributing DevOps responsibilities among team members is more efficient and leads to better and faster results instead of depending on an outside team to come and rescue us from poor infrastructure. By sharing the responsibilities, I made sure that when integration and deployment time came, my group members would know how to deal with issues. By integration time, they would have come to a point in their research of the code and its behavior where things made sense. Another positive outcome was a shared interest in succeeding, leading to better teamwork and shared efforts.</p><p>Each third party application we wrote made the people stronger. They felt committed to the project and wanted to do whatever it took to make sure the system was approachable — for them but also for the next generations.</p><p>One of my developers began showing unusual expertise in DevOps related projects. I began quietly grooming him for the position of DevOps team expert. He was always excited to research the system’s code, to write manuals, to suggest improvements, to explore various solutions, to help others. He was a great DevOps mentor, our go-to guy.</p><p>Suddenly there was hope. We began solving one infrastructure problem at a time. After building a few relatively small helpful applications, we could embark on an end-to-end solution to something big.</p><p>One of our big infrastructure projects was to change the work environment from the old obsolete one to the beloved Visual Studio. This project had been postponed for many years because of low prioritizing. Since we drew infrastructure on our flag — this topic now became the top priority.</p><p>This project was the perfect study case. I wanted to prove that my group was both professionally capable and had fuel to see a massive project through. These things were very important to me since the group has never released a version and people outside the group claimed that the programmers were unprofessional.</p><p>My thesis was that when a manager creates an environment where every effort is put in order to reach one major goal — people would work hard to reach that one major goal. They will research, they will talk to experts and they will find a way.</p><p>The first aspect I was trying to prove, through the new environment platform porting project, was that the group consisted of programmers who had a passion for their jobs. Since they began working on the project, it became very clear in a very short amount of time that they had large amounts of fuel and passion that were just waiting for the right time. They had tons of energy and they put their souls into the project.</p><p>My developers began researching, came with different solutions, coded day and night — until we decided on the proper architecture and design. This was not an easy project and we began working on it from point blank. Reviewing the code, throughout the process, made sure that programming skills were not a problem — this cleared out the second aspect of my thesis.</p><p>This project’s success had opened the group to a whole new dimension. Their professional self-esteem has begun its restoration process, and they were now very eager to prove themselves worthy to other clients.</p><p>I felt improvement, but it wasn’t the group’s time yet. They needed to fill some of the other holes they had fallen into, now and again, over the years. They needed building and empowering. We needed proper marketing, and effective software group marketing comes with, believe it or not, good software products. We needed to work on development methodologies and coding standards, on proper product management and on project milestones before we could show anything to anyone.</p><p>Overcoming the technology gap was a difficult step. It demanded many sacrifices from each group member, but it was necessary when it came to leaving the vicious zero-products cycle. It was necessary for improvement and for the upcoming products we were going to sell our future clients.</p><p>What is a group’s identity? How do we define our group and how do we create an identity when there is none?</p><p>All this and more in my next blog post. Stay tuned :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5610cf416bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/how-i-started-the-process-of-healing-a-dying-software-group-d5610cf416bc">How I started the process of healing a dying software group</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overcoming a Technological Gap — a Horrible Circumstance or a Creative Adventure?]]></title>
            <link>https://medium.com/@vicki.kalm/overcoming-a-technological-gap-a-horrible-circumstance-or-a-creative-adventure-ad3e97e64e44?source=rss-df0572f54bf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad3e97e64e44</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[management-software]]></category>
            <category><![CDATA[infrastructure]]></category>
            <dc:creator><![CDATA[Victoriya Kalmanovich]]></dc:creator>
            <pubDate>Thu, 15 Nov 2018 18:24:44 GMT</pubDate>
            <atom:updated>2018-11-16T08:46:52.308Z</atom:updated>
            <content:encoded><![CDATA[<h3>Overcoming a Technological Gap — a Horrible Circumstance or a Creative Adventure?</h3><p>This is part 2 of my series on my journey of healing a dying software group. In part 1- <a href="https://medium.com/@vicki.kalm/how-can-corporations-heal-a-dying-software-group-1abe03d8a492">How Can Corporations Heal a Dying Software Group?</a>, I presented an overall scan of a dying software group I had begun leading. This time, I will dive into the technological difficulties.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*bVgAj5lJH4beU6Sq89-qDQ.jpeg" /></figure><p>My next step was to figure out how to overcome technological gaps. When I say technological gaps, I don’t mean switching from Java to Node.js, oh no. We’re talking here about obsolete systems, ancient coding language (worse than hieroglyphs, trust me on that one), an impossible coding environment, no coding methodology, plenty of spaghetti code etc. The systems were implemented in such a way that there was no possible hardware upgrade without just writing everything from scratch.</p><p>I began solving each problem separately. I found several solutions to each problem and began prioritizing. For example, the coding environment issue. The system’s coding environment was so old, that even the company that designed it had already been shut down for many years. It was designed in a certain way that even the simple things were in fact very counter-intuitive. The compilation process, for one, had to be done very carefully. In order to compile one file, a programmer had to find all the files that were affected by it, all the files it might affect and files that are somehow related to it. They needed to find all these files manually, and run them through some other processes, and then when that was finally over with- they needed to wait for a few hours for the compilation to be complete. This was the least of all problems; therefore it was the first issue to attend to.</p><p>After massive research and thought, we found an elegant solution, that was immediately applicable. We’ve found a way to automate the previously manual process through a third party application. However, an easy compilation was not the main goal here. My goal was to target all the faulty infrastructures, find and implement a simple solution yet constantly remind the client we needed more budget to solve the more serious infrastructure issues.</p><p>This proved to be a path worth pursuing, since each problem we’ve solved uncovered more issued concerning the architecture and design of the system. This project was doomed the moment the papers were signed, but I hadn’t given up hope.</p><p>I started sniffing around, trying to find an interesting project related to our system. I found a project that can solve a very serious problem and we can add it to the main system. This decision provided two things: first, the client understood there is more potential to the group than he had previously thought, and second — we could add infrastructure upgrades as a part of the new project’s budget. This had more value than just money — the developers began feeling the new spirit, they felt more needed, they began working with extra willpower on infrastructure projects since they knew it was meant to serve a project the client believed in. This led to an effective work environment, where people felt more productive and felt more inclined to share creative solutions.</p><p>At this point, you might ask — where is our DevOps team?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*BJBFmE21S3vxSHWRBb6_Ow.png" /></figure><p>Well, to tell you the truth — there was no designated DevOps team, nor was there a QA team, a product manager, a proper project manager and so on. We had to rely on ourselves and to be completely honest — it was better that way. In my opinion, distributing DevOps responsibilities among team members is more efficient and leads to better and faster results than depending on an outside team to come and rescue us from poor infrastructure. By sharing the responsibilities, I made sure that when integration and deployment time came — my group members would know how to deal with issues. By integration time, they would have come to a point in their research of the code and its behavior where things made sense. Another positive outcome was a shared interest in succeeding, leading to better teamwork and shared efforts.</p><p>Each third party application we wrote made the people stronger. They felt committed to the project and wanted to do whatever it takes to make sure the system is approachable — for them but also for the next generations.</p><p>One of my developers began showing unusual expertise in DevOps related projects. I began secretly grooming him for the position of DevOps team expert. He was always excited to research the system’s code, to write manuals, to suggest improvements, to explore various solutions, to help others. He was a great DevOps mentor, our go-to guy.</p><p>Suddenly there was hope. We began solving one infrastructure problem at a time. After building a few relatively small helpful applications, we could embark on an end-to-end solution to something big. One of our big infrastructure projects was to change the work environment from the old obsolete one to the beloved Visual Studio. This project had been postponed for many years because of low prioritizing. Since we drew infrastructure on our flag — this topic now became the top priority.</p><p>This project was the perfect study case. I wanted to prove that my group was both professionally capable and had fuel to see a massive project through. These things were very important to me since the group has never released a version and people outside the group claimed the programmers to be unprofessional. My thesis was that when a manager creates an environment where every effort is put in order to reach one major goal — people would work hard to reach that one major goal. They will research, they will talk to experts and they will find a way.</p><p>The first aspect I was trying to prove, through the new environment platform porting project, was that the group consisted of programmers who had a passion for their job. Since they began working on the project, it has become very clear in a very short amount of time, that they had amounts of fuel and passion that was just waiting for the right time. They had tons of energy and they put their souls into the project. My developers began researching, came with different solutions, coded day and night — until we have decided on the proper architecture and design. This was not an easy project and we began working on it from point blank. Reviewing the code, throughout the process, made sure that programming skills were not a problem — this cleared out the second aspect of my thesis.</p><p>This project’s success had opened the group to a whole new dimension. Their professional self-esteem has begun its restoration process, and they were now very eager to prove themselves worthy to other clients.</p><p>I felt improvement, but it wasn’t the group’s time yet. They needed to fill some of the other holes they have been falling into, now and again, over the years. They needed building and empowering. We needed proper marketing, and effective software group marketing comes with, believe it or not, good software products. We needed to work on development methodologies and coding standards, on proper product management and on project milestones before we could show anything to anyone.</p><p>Overcoming the technology gap was a difficult step, it demanded many sacrifices from each group member, but it was necessary when it came to leaving the vicious zero-products cycle. It was necessary for improvement and for the upcoming products we were going to sell our future clients.</p><p>What is a group’s identity? How do we define our group and how do we create an identity when there is none?</p><p>All this and more, in my next blog post. Stay tuned :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad3e97e64e44" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Can Corporations Heal a Dying Software Group?]]></title>
            <link>https://medium.com/@vicki.kalm/how-can-corporations-heal-a-dying-software-group-1abe03d8a492?source=rss-df0572f54bf0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1abe03d8a492</guid>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[management-software]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Victoriya Kalmanovich]]></dc:creator>
            <pubDate>Tue, 23 Oct 2018 18:38:47 GMT</pubDate>
            <atom:updated>2020-03-29T14:22:38.122Z</atom:updated>
            <content:encoded><![CDATA[<h3>Reinventing and Scaling a Software Group that Lost Its Way</h3><p>Imagine yourselves managing a software development group which consists of very strong programmers. They research and develop one of the most complicated systems known to mankind. They write and write and write code — but eventually, no one wants software versions of that code. No one knows what they actually do day to day. The truth is — no one believes in your group.</p><p>This year I became a software development group manager, and I’ve had to deal with 15 employees in 3 teams who, from the moment they arrive until the moment they leave the office — feel transparent.</p><p>This is my blog series, which will illustrate my journey as group lead, from a moment before closing the group, to a well appreciated, needed and a formal authority in the corporation. In this first blog post, I will present the group’s background including a few major failure points which occurred in my group — and can occur in many big corporations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gPpc9C6wHNkY0cwCNR_Jgg.jpeg" /></figure><p>In my professional past, I developed defense systems as a software engineer, managed autonomous vehicle projects for very big clients, developed autonomous vehicles navigation algorithms and organized events as a data science community manager. Becoming a software group manager, after a very technical professional past was not an easy task.</p><p>The more problems I’ve diagnosed in my group, the more it seemed like a failing startup — there was no money, no client, no motivation. I arrived a moment before shut down.</p><p>Before managing my group, I heard of it from many different sources. The main idea was its low productivity and a grand waste of human resources. I had to try and understand — how can such a talented group of software engineers not get their well-deserved recognition? How can they work on such important projects and still seem to be wasting their and the company’s time?</p><p>The more hours I spent at the office, the more challenges I’ve discovered within the group.</p><p>I felt that in order to succeed, I needed to reach out to the people as my first step, before digging further into the projects. I scheduled one-on-one talks with everybody and a separate talk for each team. My intention was to map out my people’s thoughts, strengths and professional interests, in order to be as impartial as I can to gossip. In the meantime, I started mapping out all the projects the group had been working on at the time, and the picture I got was so scattered and misguided that none of them actually knew what the group’s main objective was.</p><p>It was very clear to me that over the years the group has lost its professional identity.</p><p>How does a group lose its identity?</p><p>When the group was established, it had a very well defined purpose and a great value as it was beneficial for the client. It was in charge of application hosting platforms and applications which were consequently hosted upon these platforms. After the final version of each of the developed products was released, the spiraling began. The group received projects that had nothing to do with its main purpose, they began supporting technical issues in order to help clients other than the main client, and worst of all — the group stopped releasing versions. Unfortunate managing choices have let the group’s already bad reputation — to deteriorate immensely. Its identity had been completely wiped out.</p><p>I immediately devised a plan which consisted of freshening up the teams, teaching proper agile development methodology and strengthening the teams leads. On the verge of change, I decided to wait. I had spotted a hostile group member.</p><p>It was a programmer who the former group manager put in a team lead position. He got to manage the strongest team of all three. As a team lead, he somehow managed to wreak havoc upon the entire group and be completely unproductive.</p><p>I knew I had to deal with the human resources problem before I headed on to solving the other issues.</p><p>To sum some of the damage he caused over the years — he set irrelevant assignments to his group members, disappeared for large amounts of time during the day, failed to complete his assignments as a programmer and his responsibilities as team lead, created an atmosphere filled with fear from approaching him and a most serious incident — deleted large amounts of code that his team members had been working on for the past year and a half. I will present one example in greater detail.</p><p>During assignment planning, he received an assignment to organize the project’s GIT. Up until that time, the GIT was a great big mess that consisted of two different project versions. Since the team lead (let’s name him Steve for the sake of the example) was the most experienced senior developer, we all agreed it would be most effective if he’d gotten the assignment, since it would’ve taken him the least amount of time and efforts. After a month, in which we’d held a few status meetings where he spoke of his progress, we found out that not only did the GIT stay exactly the way it was, but he also ordered his team members to develop upon the older version — thus creating unnecessary integration problems. Everywhere else — a worker like that would’ve been immediately fired. Unfortunately, I could not fire him nor take any other disciplinary measure against him.</p><p>This story with Steve reminded me of an employee I had as a regional manager for a non-profit organization a few years back. Let’s name her Suzy. As a regional manager, I was in charge of managing my branch managers on the one hand and on the other hand — developing our region’s community and business relations. Suzy was one of my employees. In time, we’ve realized being a branch manager lead her to have a strong thirst for power. She took on many responsibilities, treated her branch co-managers as her employees, disrespected her co-workers and basically bossed everyone around. No one had the guts to stand up to her for years, because it was a voluntary job, and we didn’t want her to use her rage against the organization. Every action had to be taken very delicately. I’d tried changing the atmosphere, adding bonding activities and a few other approaches. When we saw nothing changed her behavior, I decided to take more drastic measures.</p><p>I started actively managing their meetings and assigned more responsibilities to the other managers. I reduced the amount of power she supposedly had, by letting the other managers talk to the contacts she usually contacted. My response to the problem was decentralization, which ultimately led to a healthier work environment.</p><p>Going back to Steve — the situation was much more extreme and involved one of the company’s crown jewel projects. It was clear to everyone Steve, much like Suzy, had a thirst for power. He always requested more people for his team, It didn’t matter to him what happened next, he just needed to be everyone’s boss. At management meetings, he had to cancel out every idea but his own, and he was always so stubborn he never really listened to his peers.</p><p>Since I could not fire him, but could not keep him either, I started looking for a different position for him, far from my group. Simultaneously, I started decentralization. I gave him and his team fewer responsibilities and every new group member was forwarded to one of the other two teams. Throughout the process, I gave him performance feedback, hoping his behavior would change. His stubbornness and thirst for power prevented any change, and when he felt his power was slipping away he got angry — and so we’ve reached a turning point. At this point, Steve and I finally had a shared interest. He wanted to seek power elsewhere, and I wanted him to seek power elsewhere. I knew he was one of the group’s many setbacks, but I also knew that dealing with any other setback before I got rid of him would be futile.</p><p>Peter Drucker once said: “Management is doing things right, leadership is doing the right things”. This thought is what kept me going in the direction I believed was right. I saw in my mind’s eye an effective software group, and I knew I had to work very hard and convince many people I was going in the right direction — in order to accomplish what I’d started. I chose to fight instead of to comfortably sit in my office and watch the group suffer defeats.</p><p>To make a long story short, I got rid of Steve, he moved to another group, and I began mapping the faults and behavioral patterns I was looking forward to dealing with.</p><p>The technological gaps, lack of flexibility in the organization, creating a professional identity and returning the group’s motivation — in the following blog posts, stay tuned :)</p><p>Part 2- <a href="https://medium.com/@vicki.kalm/overcoming-a-technological-gap-a-horrible-circumstance-or-a-creative-adventure-ad3e97e64e44">Overcoming a Technological Gap — a Horrible Circumstance or a Creative Adventure?</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1abe03d8a492" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>