<?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 Eli on Medium]]></title>
        <description><![CDATA[Stories by Eli on Medium]]></description>
        <link>https://medium.com/@ms_lizzie?source=rss-e9f1d1e9091f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dWJZTvX3b3v7tpB6wnnRnA.jpeg</url>
            <title>Stories by Eli on Medium</title>
            <link>https://medium.com/@ms_lizzie?source=rss-e9f1d1e9091f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:00:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ms_lizzie/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[Before You Build That Feature, Test the Promise]]></title>
            <link>https://medium.com/@ms_lizzie/before-you-build-that-feature-test-the-promise-6f5a86e94f23?source=rss-e9f1d1e9091f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f5a86e94f23</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Eli]]></dc:creator>
            <pubDate>Tue, 15 Sep 2026 16:40:52 GMT</pubDate>
            <atom:updated>2026-09-15T16:40:52.281Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M0_Dm7TF0NNhmJfi" /><figcaption>Photo by <a href="https://unsplash.com/@abillion?utm_source=medium&amp;utm_medium=referral">abillion</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You have an idea for a feature. It makes sense, solves a problem you believe your users have, and your team estimates it will take three weeks to build. Three weeks isn’t catastrophic. But it’s three weeks you can’t spend on something else, and you still don’t know whether anyone will use the feature once it’s there.</p><p>You could ask users. The problem is that people are generally quite generous with hypothetical products. “Would you use automated weekly reports?” is an easy question to answer yes to when using them costs nothing.</p><p>Or you could put an “Automated weekly reports” button in the product before the reports exist and see what people actually do. That’s a <strong>Fake Door Test</strong>: you expose users to something that looks real without building the functionality behind it. It’s a much cheaper way to learn something before committing those three weeks, although what exactly you’ve learned deserves some attention.</p><h3>You haven’t tested the feature</h3><p>Suppose 18% of users click the new button. That’s a strong enough number to get excited about, especially when you’re already inclined to believe the feature is a good idea. It would be very easy for “18% clicked” to become “users want this” and, eventually, a green light for development.</p><p>But those users haven’t seen a report. They don’t know whether it contains useful information, whether the numbers are accurate, or whether receiving one every week would save them any time. They have experienced none of the things you’re actually considering spending three weeks building. What they have experienced is the promise: <em>click here and we’ll generate your weekly report</em>. Eighteen percent found that promise interesting enough to click.</p><p>That is evidence, just of something narrower than “people want the feature.” Once an idea enters development, the cost of being wrong changes. Before development, changing the idea costs very little. Three weeks later, you have working software, a team that invested time in it, and a very understandable desire to justify that investment. Being precise about what you learned is considerably easier before all of that happens.</p><h3>A click isn’t a green light</h3><p>The simplest Fake Door asks almost nothing from the user. They click, discover that the feature is coming soon, perhaps leave disappointed, and you record the interaction. You can ask for more: let them join a beta, connect a data source, or spend twenty minutes on an onboarding call. Each version gives you a different behavior to observe, and those behaviors aren’t interchangeable.</p><p>If someone gives you twenty minutes of their time because they want access to a feature that doesn’t exist yet, that’s different from clicking a button out of curiosity. But I wouldn’t turn this into a convenient formula where more friction automatically means stronger validation. If I want your automated reports but have absolutely no desire to spend twenty minutes talking to your team, my refusal to book that call tells you quite a lot about my willingness to book a call. It doesn’t automatically tell you that I don’t want the reports.</p><p>A Fake Door doesn’t produce a yes-or-no answer on whether to build. It gives you a piece of observed behavior, and the action you asked users to take determines what you can reasonably infer from it.</p><h3>What would make you spend the three weeks?</h3><p>Let’s say 18% click the automated reports button, but almost nobody joins the beta. I wouldn’t build the feature based on the 18%, but I wouldn’t discard the idea based on the beta signups either. The promise attracted attention, but something changed when users were asked to do more.</p><p>Talk to the people who clicked and find out what they expected to happen. What did they think the report would contain? Were they already doing this work manually? What problem did they expect the feature to remove? You’re no longer asking whether an imaginary feature “sounds useful.” You have an actual behavior to investigate.</p><p>You might discover that the problem is real but your proposed solution is wrong. You might find that people want one part of the report and couldn’t care less about the rest. Or perhaps “automated reports” simply sounded interesting on a button.</p><p>I’d make a very different decision about those three weeks in each case. The 18% gets me interested enough to find out which one I’m looking at. It doesn’t get the feature built.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f5a86e94f23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Management Principles To Learn From Tom DeMarco]]></title>
            <link>https://medium.com/@ms_lizzie/5-management-principles-to-learn-from-tom-demarco-6bd76f0b8b8d?source=rss-e9f1d1e9091f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bd76f0b8b8d</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Eli]]></dc:creator>
            <pubDate>Tue, 08 Feb 2022 10:52:17 GMT</pubDate>
            <atom:updated>2022-02-08T10:52:17.505Z</atom:updated>
            <content:encoded><![CDATA[<h4>MANAGEMENT LITERATURE</h4><h4>Great tips from the father of management</h4><figure><img alt="Tom DeMarco Peopleware Productive People and Teams Short Notes Management Literature" src="https://cdn-images-1.medium.com/max/1024/1*NFG8tF5112qnhvgC9yID_w.jpeg" /><figcaption>Image by <a href="https://www.pexels.com/ru-ru/@shvets-production?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">SHVETS production</a>: <a href="https://www.pexels.com/ru-ru/photo/7203700/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>One of the first books I had read when I first stepped into management was Tom DeMarco’s <em>“Peopleware: Productive Projects and Teams.”</em></p><p><a href="https://www.amazon.com/Peopleware-Productive-Projects-Tom-DeMarco/dp/0932633439">Peopleware: Productive Projects and Teams</a></p><p>This book is one of the classics for management literature. And, though it first came out in 1987, the outlined principles remain true to that day. I have read many management-related books in my career, but I still think this book is the one that influenced me the most.</p><p>I have prepared a list of key ideas that I incorporate into my management routine and I want to share them with you.</p><p>Let’s roll!</p><h3>#1 Manage people, not code</h3><p>A project’s success is directly dependent on human interaction, while rookie managers often try to concentrate on the technical aspects. This usually happens because it is easier for a manager who has grown from a performer to solve technical issues. As I have mentioned in one of my <a href="https://medium.com/@ms_lizzie/stop-writing-code-if-you-are-a-team-leader-794e78ce6426">previous articles</a>, such attitude may lead to critical problems on the project that you will not be aware of till the last minute.</p><p><strong>People</strong> are your most valuable asset. A project will never be truly successful if created by a group of strangers who just come together every day from 9 to 5.</p><p><strong>Teams</strong> create great projects. As a manager, it’s your job to build that team.</p><h3>#2 Don’t bully developers for making mistakes</h3><p>For most developers and other engineer-related workers, making mistakes from time to time is an entirely natural part of their job. Encouraging a <em>“no-error environment”</em> simply ties people’s hands and prevents them from trying new approaches due to the fear of failure.</p><p>I spent years and years punishing myself for every little mistake I made. It cost me my self-esteem; it nearly cost me my whole career. The atmosphere in a team I worked with was quite tense when it came to mistakes. Every slight error was a target of detailed investigation by management and ridicule by senior colleagues. If QA returned a ticket to us, the Team Lead would go through the whole process: <em>How did this happen? Why didn’t you do it right in the first place? What should we do never to repeat that mistake?</em></p><p>I’m sure that his intentions were good by nature. And these are, in fact, the right questions to ask a developer, but you have to know <strong>when</strong> and <strong>how</strong> to ask them. Because otherwise, it will only lead to your employees’ lack of confidence and self-doubt.</p><p>There is a thin line between helping your teammates grow by analyzing their weaknesses and bullying the hell out of them by researching their every blunder.</p><h3>#3 Treat your teammates as humans</h3><blockquote>Although your staff may be exposed to the message “work longer and harder” while they’re at the office, they’re getting a very different message at home. The message at home is, “Life is passing you by. Your laundry is piling up in the closet, your babies are uncuddled, your spouse is starting to look elsewhere. There is only one time around on this merry-go-round called life, only one shot at the brass ring. And if you use your life up on C++ . . .</blockquote><p>This may come as a shock, but your colleagues are actual people, not some code-writing robots. They have their ups and downs, their own worries and concerns. The key method of getting peoples’ loyalty is to show them that you understand that. And that you care about them.</p><p><strong>Do the little things:</strong> get to know what interests them and what they value the most; ask about their opinion; compliment a well-done job. If your colleague’s wife is sick — let them go home early and ask how she’s doing the next day; they will highly appreciate it.</p><h3>#4 Don’t neglect product quality</h3><p>We all know the stress of the development routine, with all the missed deadlines and non-realistic estimations. In turmoil, the quality of an end product (code) often isn’t one of the manager’s top concerns.</p><p>But it should be. Because the rule “<em>Quality? Only if we have time!</em>” will lead to no quality at all.</p><p>Accumulation of technical debt, outdated technology stack, spaghetti code — all of this will eventually force developers to leave the project. And you don’t want the loss of knowledge and low team morale due to the high staff turnover.</p><p>Customers often do not want to extend the development time, thus not providing us an opportunity to service technical debt. What I always do in that case is a detailed document explaining all of the codebase weak spots, what they may lead to, and how it will affect the product’s development and the client’s business in the future.</p><p>You have to stand your ground here: your team is responsible for its work, and you want the outcome of that work to be good.</p><h3>#5 Create a comfortable environment</h3><p>When we all were still working at the office, one of my main concerns was a vast, noisy open space with many people and not enough air for all that crowd. How can a developer be productive in such a place?</p><p>I had so many disagreements with my colleague due to this, me always wanting to keep the window open and him always wanting to keep it closed. <em>Ah, the typical office kerfuffle!</em></p><p>As a manager, you need to create an environment that will be comfortable for everybody. That will be quiet, will have enough space, where there won’t be any distractions.</p><p>Even with the home office, this idea still applies, especially about distractions. Keep meetings to a minimum. Remember, if a person is not talking at a conference, it’s a fool-proof indicator that they do not need to be there. Simply send the meeting notes later.</p><p>Leave your developers some time to do their work in peace.</p><p>These are some of the basics management principles for you to follow if you want to build a loyal and productive team.</p><p>I would like to summarize these concepts with my favorite quote:</p><blockquote>The manager’s function is not to make people work, but to make it possible for people to work.</blockquote><p>Did you find this article useful? Let me know what you think by leaving a comment, or consider following me if you like to read more about management in IT.</p><h3>About the author</h3><p><em>Lizzie is a Software Developer and a Team leader with overall 7 years of experience in the field. She has been managing development teams for 3 years now. In this blog, she writes about everything you would like to know about being a good leader, making your customer happy, and making your developers feel like a real team.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bd76f0b8b8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Obvious Mistakes I Made as a Junior Team Lead]]></title>
            <link>https://medium.com/@ms_lizzie/3-obvious-mistakes-i-made-as-a-junior-team-lead-6f11dbeeea02?source=rss-e9f1d1e9091f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f11dbeeea02</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Eli]]></dc:creator>
            <pubDate>Sun, 06 Feb 2022 20:09:10 GMT</pubDate>
            <atom:updated>2022-02-06T20:09:10.302Z</atom:updated>
            <content:encoded><![CDATA[<h4>MANAGEMENT TIPS</h4><h4>A personal story</h4><figure><img alt="Mistakes of a Junior Team Leader, management tips, IT Management" src="https://cdn-images-1.medium.com/max/1024/1*cXpYpOzPie_hHvNikUNjfQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@neonbrand?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">NeONBRAND</a> on <a href="https://unsplash.com/s/photos/mistake?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I first became a Team Leader in 2019, being promoted from a Software Engineer. I had what it takes, or at least my management thought so.</p><p>But nobody has ever taught me how to do this new job.</p><p>Please don’t take me wrong; I understood my responsibilities very well. But I had no management training whatsoever, and thus at the beginning, I made all the possible mistakes.</p><p>Now, when I look at other fellow developers who start their career path as team managers, I recognize all the mixed feelings I also had. And I see the same struggles and the same mistakes.</p><p>This article will outline three of them that I encounter most often, with personal examples.</p><p>Let’s roll!</p><h3>#1 Over-performing</h3><p>If there was previously a well-defined result of my work — a new piece of code, a whole new feature, or a fixed bug — now there is none. I spend my days mostly talking, to developers, QA engineers, other managers, clients, or writing emails. It seems that I stopped making an impact on a project whatsoever.</p><p>That is when <strong>the impostor syndrome</strong> kicks in.</p><blockquote><em>Why does the team need me?</em></blockquote><blockquote><em>My work is not essential.</em></blockquote><blockquote><em>The team can function well without me.</em></blockquote><p>These are just some examples of the thoughts in my head at that time. To compensate my “uselessness,” I began working more. And then even more. In addition to my management tasks, I continued to act as a developer: I needed to see some actual results of my labor.</p><p>Needless to say that nobody asked me to work this hard. I wasn’t paid for it also. I began getting tired and slowly burning out.</p><p><strong>What I did about this:</strong></p><p>After recognizing the impostor syndrome, I started keeping track of my managerial victories, even the small ones, to get rid of it.</p><p><em>We have released a feature on time</em> — check, that’s a win.</p><p><em>I’ve pitched the client a vital performance improvement that requires a lot of development resources</em> — more success for me.</p><p>Over time, just looking at the list of my achievements, it became clearer that I’m doing well as a manager, and there is no need to over-compensate.</p><h3>#2 Underestimation</h3><p>I was under the impression that the faster the team works — the better. So when we received a significant feature, it was always tough for me to give a proper estimate.</p><blockquote><em>We should do it faster to please the client</em>.</blockquote><blockquote><em>No way the client will agree to such an extensive time frame.</em></blockquote><p>For the first few features, I gave a tight estimate. The team did everything on time, and there was no problem, but what if something went wrong? The obvious thing: someone could have gotten sick. I did not consider that in my estimate at all.</p><p><strong>What I did about this:</strong></p><p>I’m not saying that it was easy, but I took the path of behavioral therapy. I exposed myself to my fear. I practically forced myself to stop minimizing the work that we needed to do. If the proper estimate was immense — I said so to our client. And, shockingly, nothing terrible happened.</p><h3>#3 Inability to delegate tasks</h3><p>I first felt a strong urge to do all the most complex technical tasks myself. Partly due to the impostor syndrome covered in the first paragraph, partly because I would do them much faster than the newly hired developers who knew nothing about this project.</p><p>The latter was my main concern. I was afraid that we would fail to release a feature if I entrusted it to the new developer.</p><p><strong>What I did about this:</strong></p><p>I began to give developers time for research first. After they familiarized themselves with a feature or an existing codebase, I would ask them to present me with an assessment of how they plan to proceed. We discussed the needed changes on a high level and set checkpoints.</p><p>I also increased the developer’s estimation before providing it to the customer to be safe.</p><h3>Summary</h3><p>As with everything, becoming a manager is a journey. It’s OK to deviate from the route as long as you reach the destination. It’s OK to make mistakes as long as you learn from them.</p><p>Of course, now, with years of experience, my management style is different. But I have to own my past mistakes.</p><p>This very personal story was somewhat challenging for me to share. If you want to support me or have encountered the same problems in your management path, please leave a comment or a clap, or consider following me if you would like to read management-related stories.</p><h3>About the author</h3><p><em>Lizzie is a Software Developer and a Team leader with seven years of experience in the field. She has been managing development teams for three years now. In this blog, she writes about everything you would like to know about being a good leader, making your customer happy, and making your developers feel like a real team.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f11dbeeea02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Writing Code If You Are a Team Leader]]></title>
            <link>https://medium.com/@ms_lizzie/stop-writing-code-if-you-are-a-team-leader-794e78ce6426?source=rss-e9f1d1e9091f------2</link>
            <guid isPermaLink="false">https://medium.com/p/794e78ce6426</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Eli]]></dc:creator>
            <pubDate>Mon, 31 Jan 2022 21:11:17 GMT</pubDate>
            <atom:updated>2022-01-31T21:16:10.840Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k5wlkf7Y80t9GTgO" /><figcaption>Photo by <a href="https://unsplash.com/@sigmund?utm_source=medium&amp;utm_medium=referral">Sigmund</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You have been coding your whole life. You like it; you are passionate about it and probably really good at it too. But then you start leading a team, which means that everything should change.</p><p><em>Or shouldn’t?</em></p><p>It’s an eternal question for every manager from an engineering background.</p><p>The hardest thing is to understand that <strong>you are not an actual developer anymore</strong>. You are now in a role with different responsibilities, different daily schedules, and tasks that involve different mental processes. Trying to mix business with pleasure, or in our case — trying to combine developing with management — is like working two jobs.</p><p>And working two jobs may often lead to early burning out and, frankly, not being any good in either of them.</p><p>Most development tasks require high concentration and focus, which contradicts the very nature of the team leader’s work. Constant meetings, calls, messages — a manager is always on alert. It’s tough to consider all the algorithm’s edge cases when your phone is ringing all the time.</p><p>And on the other side, it’s hard always to be prepared to answer your teammates’ or customers’ questions if all you can think about is the efficiency of that function you just wrote.</p><blockquote><em>Being a good manager means giving up habits that make you inefficient, even if that means giving up coding.</em></blockquote><p>Another thing is that spending a lot of time on development gives you little time to do your actual job as a manager. And your job is managing other <strong>people</strong>. Though you will probably make time for your primary duties — assigning tasks, making estimations, communicating with the customer — you will miss out on all the other “noncrucial” parts of your job. You can get so invested in a feature that you will miss some critical signs of your employees becoming demotivated to do their work, tired, or less happy.</p><p><em>You may not even notice that your team is no longer a </em><strong><em>team</em></strong><em>.</em></p><blockquote><em>Every good leader needs to monitor their team members’ emotional state. And it’s hard to do that if you are too busy.</em></blockquote><p>And, as you are busy, you become less creative. Who will come up with a new fun team-building activity? Most certainly not you, since you are too deep in the code.</p><h3>But what if I do not want to give up coding?</h3><p>It may so happen that plain management isn’t your path. Being a Team Lead is all about people; being a Tech Lead is about code. If programming is critical for you and brings you more joy, you may be more suited for a Technical Leader role. So choose wisely.</p><p>But as a Team Lead, you are still most welcome to join code reviews and help your teammates with challenging coding problems if you want to.</p><blockquote><strong>Consult. Guide. Assist</strong>.</blockquote><p>That’s your motto now.</p><p>And of course, it’s always a good idea to keep reading technical articles, stay up to date with news and trends, solve little programming challenges for yourself to keep your brain sharp.</p><p>But no full-time development anymore. Promise?</p><p>Did you find this article useful? Let me know what you think by leaving a comment, or consider following me if you like to read more about management in IT.</p><h3><strong>About the author</strong></h3><p><em>Lizzie is a Software Developer and a Team leader with overall 7 years of experience in the field. She has been managing development teams for 3 years now. In this blog, she writes about everything you would like to know about being a good leader, making your customer happy, and making your developers feel like a real team.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=794e78ce6426" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Traits of a Bad Code Reviewer]]></title>
            <link>https://medium.com/@ms_lizzie/5-traits-of-a-bad-code-reviewer-598da8e6dc19?source=rss-e9f1d1e9091f------2</link>
            <guid isPermaLink="false">https://medium.com/p/598da8e6dc19</guid>
            <category><![CDATA[coderview]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Eli]]></dc:creator>
            <pubDate>Thu, 27 Jan 2022 14:30:35 GMT</pubDate>
            <atom:updated>2022-01-28T22:28:45.055Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ey8vLWJDIVu9CataybBXdQ.jpeg" /><figcaption>Image by <a href="https://www.pexels.com/ru-ru/@anete-lusina?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Anete Lusina</a>: <a href="https://www.pexels.com/ru-ru/photo/5723268/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>Code review is a widespread practice for most current projects. In all teams that I have worked with, it was mandatory. But that does not mean that it was always good. Or even a bit helpful.</p><p>Why is that? Because of the developers’ attitude towards this process. In some cases, it was not only a waste of time, but it made things worse.</p><p>This article will look at some red flags that may indicate that a person is not doing that good job as a code reviewer.</p><p>Let’s roll!</p><h3>1) Reviewing only from the technical side</h3><p>Code review is not only about code quality. That’s an important part, and you should not neglect it. But code review is so much more than that. It’s about ensuring that the code you are checking <strong>will do its job</strong>. If you are reviewing a piece of new implementation, make sure you familiarize yourself with the business requirements of that feature and check if the written code matches those requirements.</p><p><em>That’s tedious</em> — you may think. But no one said that code review is an easy process. It’s complex. And a responsibility.</p><p>The easiest way to check if a person correctly understood business requirements is to check unit tests. First of all, are they present? Do they include edge cases?</p><p>By looking at the unit tests, you can easily understand whether the developer has considered all the possible outcomes of their code.</p><h3>2) Not taking responsibility</h3><p>Code reviews are generally part of your job. And it’s your responsibility to do that job well, which means that superficially glancing over the code is not enough. Even since you press that <em>‘Approve’</em> button, you become as responsible for that code as the one who wrote it, and if any serious problem occurs — you will be equally to blame.</p><p>So you either invest enough time into this process or deny doing it altogether.</p><p>Don’t do a half-ass job.</p><h3>3) Using “I don’t like this” as an argument</h3><p>There are so many ways to do the same thing — indeed, more than one. And yes, it may so happen that another person prefers another method. There is no tragedy here. And no need to start a holy war over a pattern used, or even the lack of it. Is the code easy to understand? Does it meet requirements? Then everything is ok. Would you do it differently? That doesn’t matter.</p><h3>4) Not taking time restrictions into account</h3><p>We always want to make things better. But you have to think about the priorities. So when you are doing a code review, always consider the current situation on a project. If there is plenty of time, there is plenty of room for improvement. But if we are on a deadline, asking a colleague to re-implement a feature from scratch is just reckless.</p><h3>5) Not being polite</h3><p>Remember, you are checking someone’s days of work. Even if there are mistakes or the code is terrible, this is still your colleague. Always show some basic respect.</p><p>My rule of thumb is leaving comments in the form of a question.</p><p>“Maybe it’s better to do this in another way?” sounds much better than “Do this in another way!”.</p><p>After all, you want to maintain a good relationship with your team.</p><h3>Briefly</h3><p>When doing a code review, check both technical implementation and code’s compliance with requirements. Be attentive, as you are responsible for your review. Don’t waste time arguing about best practices — there are more opinions than one. Consider current project status and suggest massive changes only if there is time to make them. And of course, always be polite.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=598da8e6dc19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Rules That Will Help You Become a Better Junior Developer]]></title>
            <link>https://medium.com/@ms_lizzie/6-rules-that-will-help-you-become-a-better-junior-developer-c56568131474?source=rss-e9f1d1e9091f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c56568131474</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[first-job]]></category>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Eli]]></dc:creator>
            <pubDate>Tue, 25 Jan 2022 18:36:36 GMT</pubDate>
            <atom:updated>2022-01-28T22:30:34.440Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Or even a great one</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dN2MUQtajPN5SWW7jldP0Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kylejglenn?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kyle Glenn</a> on <a href="https://unsplash.com/s/photos/development?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>So you have finally landed that Junior Developer job. That’s great! And while there is no doubt that starting a new job is scary, when it’s your first job — it’s plain as day terrifying. So let’s find out together how to make this a more positive experience for you and your colleagues’ sake.</p><p>I won’t state here the obvious facts like be polite, do your job, don’t show up late for meetings, etc. Instead, I will give you some advice that will help you stand out from other fellow Junior Devs.</p><p>Lets’s roll!</p><h3>Rule 1. Write down everything</h3><p>And I mean everything! Even if you are super confident with your memory and it has never betrayed you before. It’s a very stressful time and there is a lot of new information coming your way. Remember, you will never make a good first impression if you forget things.</p><p>And on the contrary, you will quickly gain some basic respect from your colleagues if they won’t have to repeat you twice.</p><h3>Rule 2. Record audio calls/conversations</h3><p>That’s pretty much an extension of a previous rule. If your colleague is explaining something to you, being that a technical assignment, or a knowledge share, it’s always a good idea to set up some sort of a recording. That way, you can later come back and listen to the explanation again without bothering anyone else. And believe me, that will come in handy, especially for the first few months.</p><h3>Rule 3. Master the art of asking questions</h3><p>You will have a lot of questions for the first time. It’s okay. It’s better to ask questions and do something instead of sitting around all day wondering and doing nothing.</p><p>But you should do that in a moderate way. First, always ask yourself the following:</p><ol><li>Have someone already told me about that? Do I have some notes/recordings on that topic?</li><li>Is there any documentation about this? Maybe there’s a specification that I can read to get some insight?</li></ol><p>After doing that, if the question still persists — put it on the list.</p><p>It’s much better to approach a person <em>once</em> with a bunch of questions than bother that person five times within a 15-minute interval.</p><p>Always proofread your list before approaching, making an actual call or sending a message. Make sure that questions are well put.</p><p>Remember: people are busy with their own work. So it will be appreciated if you put in some context before dropping on all those question bombs. Start with a short summary of the task that you are working on, it will help them understand what is that you are even talking about.</p><h3>Rule 4. Try to solve the problem yourself before seeking help from others</h3><p>There is no shame in asking for help. That’s how you learn, that’s how we all learned. But there is a fine line between <em>asking for help</em> and <em>asking somebody to do your job for you.</em> When you approach a colleague with a request, make sure that you have exhausted each and every way of dealing with the issue yourself. Always give all information that you have already learned beforehand: I have tried this and that and nothing works, what else should I try?</p><p>That way, the person will know your way of thinking and will be able to quickly point you on the right direction.</p><h3>Rule 5. It’s horses, not zebras. But sometimes it’s zebras</h3><p>In medical schools, there is a saying: <em>when you hear hoofbeats, think horses not zebras</em>. That means that the doctor should always think of the most common diagnosis, because it’s most likely to happen.</p><p>Basically the same applies to software development.</p><p>When you are presented with a problem, try to rule out the most basic and obvious causes first. Even if they seem too simple or just plain stupid. Rule them out, and then go looking for your zebras.</p><h3>Rule 6. Business problems always come first</h3><p>I suppose that goes without saying. But it’s an important rule to apply when writing — and <em>checking</em> — your code. If you are implementing a new feature, think about how customers will use it. Think about business needs. Edge cases. That will help you provide working and well-thought-out code, which is the most important outcome of your work.</p><p>Think: was every case thought of when the requirements were made? If not, don’t be afraid to make suggestions. That will show that you care about the system and its users.</p><h3>Briefly</h3><p>Don’t forget stuff. Don’t annoy people with obvious questions. Never try to get someone to do your job for you. Always think about the big picture.</p><p>And good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c56568131474" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>