<?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 Olesia on Medium]]></title>
        <description><![CDATA[Stories by Olesia on Medium]]></description>
        <link>https://medium.com/@olesia.martushkanova?source=rss-54b41907d574------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*q-Wq4C-xnxqU6l0qWFW2Bg.jpeg</url>
            <title>Stories by Olesia on Medium</title>
            <link>https://medium.com/@olesia.martushkanova?source=rss-54b41907d574------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:41:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@olesia.martushkanova/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[Working Remotely as a Developer with an 18-Hour Time Difference]]></title>
            <link>https://medium.com/@olesia.martushkanova/working-remotely-as-a-developer-with-an-18-hour-time-difference-eb7ca81b957a?source=rss-54b41907d574------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb7ca81b957a</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[time-management]]></category>
            <dc:creator><![CDATA[Olesia]]></dc:creator>
            <pubDate>Tue, 31 Oct 2023 00:03:50 GMT</pubDate>
            <atom:updated>2023-10-31T03:37:43.519Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_yiDTY_IPU7IZ1co" /><figcaption>Photo by <a href="https://unsplash.com/@lukechesser?utm_source=medium&amp;utm_medium=referral">Luke Chesser</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>About myself</h3><p>I am a Full-Stack Developer, and I am based in New Zealand, Auckland. I work full-time and remotely as a contractor for the <a href="https://www.libertymutual.com/">Liberty Mutual Insurance Company</a>. The team I work with is based mainly in Boston, USA so in the EST time zone. And there is around<strong> 18–Hour time difference</strong> between my team and me. A common joke in our team because I am almost one day ahead of everyone is, “How is the future, Olesia?” 😅</p><p>This full-time job is my first time working remotely, and the time difference is crazy! With over a year since I started, I am ready to <strong>share more about my experience</strong>!</p><h3>Unusual work schedule</h3><p>I was fortunate to have the opportunity to choose the work schedule I prefer. But my work week can’t start on Monday because it is still Sunday for the rest of the team. So, for the first half of the year, I worked <strong>4 days per week</strong> and <strong>10 hours per day, </strong>from<strong> Tuesday to Friday.</strong></p><p>It sounded awesome at first because I would have 3-days weekends every week! Once I commit to something, I follow through, so a 10-hour workday means I work all 10 hours. It turned out that coding for 10 hours was exhausting. So, I switched to <strong>5 days per week</strong> and <strong>8 hours per day. </strong>Now I don’t work on Mondays. However, I do work on <strong>Saturdays</strong>. This might be tricky if you have friends with Monday-Friday 9–5 jobs. But I learned to appreciate Sundays more, and this is the day that I spend time with the people closest to me.</p><h3>Early waking up</h3><p>My unusual schedule overlapped partly with my team’s schedule. We follow agile, so daily stand-ups, refinements, retroes etc. are part of our team’s norms. For me, it is crucial to feel that I am <strong>part of the team </strong>and <strong>contributing to our team’s success; </strong>even though I love my peaceful coding time (like many other developers, I am a little introverted 😉), I still want to participate in all important meetings. During those meetings, I like open and honest communication that makes each teammate feel valued and comfortable asking for feedback and improvements.</p><p>My <strong>workday starts at 6 AM, </strong>which is 12–1 PM for my teammates from the EST time zone. I like to maintain my pre-work routine, which includes having a proper breakfast and reading, so I <strong>wake up at 5 AM</strong>. It took me probably around a year to fully get used to it. I go to bed around 9:30–10 PM, so I am well rested for work the next day. And yes, coffee helps!</p><p>My team is amazing because they schedule meetings when I am online. There are exceptions when I cannot join meetings. In this scenario, I will ask to <strong>record</strong> them so I can watch the recording later and<strong> keep up to date</strong> with my team’s news and objectives.</p><blockquote>Can you believe that back in Ukraine I would start my work at 10 AM and still complain that I wanted to sleep??</blockquote><h3>Planning my work ahead</h3><p>When I start my workday, it is already 12–1 PM for my team in Boston. At 10 AM my time, I am the only one left working. My work day ends at 2 PM, and <strong>I work by myself half of the day</strong>.</p><p>If I suddenly get stuck with a blocker, there is no one online to give me a hand. This is tricky, but I have <strong>learned to plan my work </strong>skillfully. I always make sure that I have additional things to do in case I get stuck with the main task and need some help.</p><p>If I need help, I ask for it first thing in the morning. I don’t want to bother people at 5 PM their time, so I <strong>prepare all my questions</strong> at the end of my workday, and in the morning, I reach out for help.</p><blockquote>The “Schedule to send message” Slack feature helps a lot! I am still a bit sleepy at 6 AM so I often schedule my messages at the end of my workday (I want my messages to be concise and without any typos!), and then in the morning, Slack automatically sends them, and I can review responses later.</blockquote><h3>Submitting my code for review</h3><p>The time difference works in my favor for the code reviews. I submit my code for review at the end of my workday, which allows my team to review my code the following day with plenty of time before I log on. This works just perfectly! When I wake up, my code has already been reviewed, and I can quickly address all comments, ask for another review, merge, and deploy 😁</p><blockquote>I want to mention that a huge part of being able to move faster with the code submit-review-approve-merge process depends on how responsive my team is. I remember when I used to wait weeks for my code to be reviewed by previous companies. But in my current team, we all jump on code reviews quickly! It is always about teamwork, being a team player, and caring about your team; please don’t make people wait too long.</blockquote><h3>Communication: more is better than less</h3><p>The hardest part of my remote work is communication. How do I build a relationship with people when I am so remote? Short answer: mostly via Slack 😆</p><p>Seriously, I communicate a lot in Slack! I usually send messages in our group channel at the end of my day asking to review my code or even with updates on the progress I have made. Sometimes, there are 3+ messages in a row from me in the group channel, but I don’t worry about being “too spammy”. I believe that when you are working remotely, there is no concept of “too much communication”. It is important to be on the same page and communicate a lot. Of course, I can always call people if I feel like messaging is not enough.</p><p>In addition, it is good to maintain some small talk before meetings and calls. Even asking the simple “what did you do during your weekend?” helps to know more about people.</p><h3>Having more time after work</h3><p>Waking up early is not easy, managing time difference is tricky, and building relationships with your teammates remotely takes a lot of effort, BUT this job gives me more time outside my work life, and <strong>time is of tremendous value</strong>.</p><p>I finish working at 2 PM so I have almost the full day to myself! Thanks to this remote job, this year has been one of the best for self-improvement. I have been very consistent with sports: gym, running, yoga. My back pain is no longer with me, and I think I even look better!</p><p>I read more and started taking classes in Spanish, acting, and dancing. I even went on a 2-month European trip and visited my family in Ukraine <strong>without taking any breaks from work.</strong></p><h3><strong>Final thoughts</strong></h3><p>I don’t think I need to be in the office to be productive. I am an adult and <strong>take full responsibility for my work.</strong> If you can only trust me when I am in the office, what is the point of hiring me?</p><p>However, working full-time and remotely gets very lonely sometimes. I miss times when I could grab coffee with teammates. Yes, I have friends that I regularly see to stay social, but it is also great to see people you work with in real life. Team lunches and Christmas parties — that is where you can build some amazing memories because coding is cool, but the best part of being a developer is <strong>all about people and connections</strong>.</p><p>For that reason, I think one day I may return to a typical 9–5, Monday to Friday, office job, and I might even enjoy it a lot! But for now, I am happy where I am and <strong>grateful for this opportunity</strong> ❤️</p><p>Thank you for reading to the very end! You are very welcome to connect with me on <a href="https://www.linkedin.com/in/olesia-martushkanova/">LinkedIn</a>, and happy #devlife!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb7ca81b957a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I passed my first AWS Certification]]></title>
            <link>https://medium.com/@olesia.martushkanova/how-i-passed-my-first-aws-certification-fc057284b995?source=rss-54b41907d574------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc057284b995</guid>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Olesia]]></dc:creator>
            <pubDate>Thu, 11 May 2023 09:02:08 GMT</pubDate>
            <atom:updated>2023-05-11T09:18:29.273Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6s14tGZVptZMZAYPVss1w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@dianamia?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">C Dustin</a> on <a href="https://unsplash.com/photos/K-Iog-Bqf8E?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Quick Overview</h3><p>On the 1st of May 2023, I passed AWS Cloud Practitioner exam and received my very first <a href="https://www.credly.com/badges/853614a7-76a9-40a0-829e-380db2855e54/public_url">AWS badge</a>. This was a big achievement for me because I was consistently studying for around 2 months. And in this article, I would like to share with you my experience with my first AWS certification.</p><h3>About my motivation</h3><p>I started my current job as Full Stack Developer in August 2022. And I always believed that I had some experience with AWS before I even got this job. But once I started working for my current company I realised that actually I didn’t have many AWS skills. My current project requires building a lot of infrastructure using AWS. Developers (including me) in our team are responsible for building all infrastructure. And this became my initial motivation to extend my knowledge in AWS.</p><p>I didn’t care too much about having the AWS badge but let’s be frank: studying something additional after a full-time Dev job is extremely hard. It requires so much effort! So I booked the AWS exam and told everyone who I could about it 😆</p><blockquote>Knowing that I already booked the exam and that many people expected me to eventually receive my AWS certification was a great motivation to study consistently and not to give up.</blockquote><h3>Why I chose AWS Cloud Practitioner</h3><p>I made some research but honestly, the choice was easy. I booked the AWS Cloud Practitioner exam because it seemed like a perfect choice for someone relatively new to AWS world.</p><p><strong>During preparation for AWS Cloud Practitioner you learn the foundation of cloud development with AWS such as</strong>:</p><ul><li>the advantages of cloud development;</li><li>benefits of using AWS services;</li><li>ways of reducing costs with AWS;</li><li>cloud development models and types of cloud computing that AWS offers;</li><li>AWS shared reshared responsibility model;</li><li>AWS Well-Architected Framework and The Five Pillars of this framework;</li><li>security with AWS services and best practices around that.</li></ul><p>In addition, you get to learn about the most popular AWS services and how to choose the correct service in different situations.</p><h3>How I studied for my AWS Cloud Practitioner exam</h3><h4>Actual learning of AWS</h4><p>I really wanted to get some useful AWS skills that I could apply at my Dev job rather than focusing on adding a nice line to my CV. And I chose the <a href="https://links.zerotomastery.io/olesia_learns_aws">AWS Cloud Practitioner course from Zero to Mastery </a>online academy as my primary source to study.</p><blockquote><a href="https://links.zerotomastery.io/olesia_learns_aws">AWS Cloud Practitioner course from Zero to Mastery</a> course includes a lot of demo on how to work with the most popular AWS services. You don’t learn everything in theory only, you are getting hands-on experience of using AWS services.</blockquote><p>Following this course was interesting and at the end of each part, you get to do a practice quiz that includes similar to the real AWS Cloud Practitioner exam questions.</p><h4>My studying strategy was simple:</h4><ul><li>do at least 1–2 lessons but consistently, almost every day;</li><li>take notes by hand of the key learning points (writing by hand helps to remember information better);</li><li>for each lesson, I tried to do some additional learning from the AWS official documentation to learn deeper;</li><li>follow ALL demos (remember, we want to actually learn and get useful AWS skills, AWS badge without skills worth nothing).</li></ul><h3>Practising for the real AWS exam</h3><p>Around a week before my exam, I focused on doing practice tests for the AWS Cloud Practitioner exam. This step was very important. It helped me to learn how the questions are built, about the structure of an exam and identify gaps in my knowledge required for passing the exam.</p><blockquote>The real AWS Cloud practitioner exam consists of 65 questions with possible multiple choice. You have 90 minutes to answer all questions and you need to give at least 70% of correct answers to pass the exam. But have a look on the official <a href="https://aws.amazon.com/certification/certified-cloud-practitioner/">AWS page</a> for more information.</blockquote><p><strong>There are a few resources I used to practice for my exam:</strong></p><ol><li><a href="https://www.udemy.com/course/aws-certified-cloud-practitioner-practice-test/">These 6 AWS cloud practitioner exams</a> from Udemy</li></ol><p>After passing each practice exam you get your score and correct answers plus a very details explanation of these answers. I definitely learned a lot!</p><p>2. <a href="https://d1.awsstatic.com/training-and-certification/docs-cloud-practitioner/AWS-Certified-Cloud-Practitioner_Sample-Questions.pdf">Free sample questions from AWS</a></p><p>3. <a href="https://explore.skillbuilder.aws/learn/course/external/view/elearning/12483/aws-certified-cloud-practitioner-practice-question-set-clf-c01-english">More free practice questions from AWS</a></p><p>4. And I partially watched this <a href="https://explore.skillbuilder.aws/learn/course/external/view/elearning/9449/exam-prep-aws-certified-cloud-practitioner-foundations">free preparation course from AWS</a></p><h3>Was it worth it? (My feelings after passing AWS exam and would I do it again)</h3><p>I definitely don’t regret passing AWS certification. I think it was a good challenge for me, I learned a lot and I will do my best to apply what I learned at my Dev job.</p><p>I am also confident that I will keep learning how to work with AWS services and will keep working on improving my skills in cloud development.</p><p>However, at the moment I don’t feel like taking any more certifications (definitely not this year!). Because at the end of the day, it’s all about skills and real hands-on experience. So I am planning to focus on it.</p><p>If you reached this point: thanks for reading! I hope you find this article useful! Please, feel free to share your experience with AWS certifications below in the comments 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc057284b995" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Examples of theory tech questions during React/ Full Stack Developer interview]]></title>
            <link>https://medium.com/@olesia.martushkanova/examples-of-theory-tech-questions-during-react-full-stack-developer-interview-e406cd273216?source=rss-54b41907d574------2</link>
            <guid isPermaLink="false">https://medium.com/p/e406cd273216</guid>
            <dc:creator><![CDATA[Olesia]]></dc:creator>
            <pubDate>Fri, 22 Jul 2022 04:11:33 GMT</pubDate>
            <atom:updated>2022-07-23T09:44:24.142Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Igrd-lsZcsmotM4dI-zkGg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@arianassphotography?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ariana Suárez</a> on <a href="https://unsplash.com/s/photos/scared?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><blockquote>I recently went through a bunch of interviews with different companies: big and small. I applied for either Full Stack or Front End (with a focus on React) Developer roles, mostly intermediate level. And I have made a list of all questions that I was asked during these interviews😁</blockquote><blockquote>This are just examples of possible questions that You could be asked during technical interviews if you apply for similar roles like me. And I hope that this article will help You to prepare for future interviews better and get Your dream job!</blockquote><h4>General questions related to programming or best practices:</h4><ul><li>Describe SOLID principles</li><li>What OOP principles do you know?</li><li>What is test-driven development?</li><li>What is DOM?</li></ul><p><strong>JavaScript-related questions:</strong></p><ul><li>Tell about array methods (e.g. find, filter, map, reduce)</li><li>What is closer in JavaScript?</li><li>What is a promise in JavaScript?</li><li>What is JavaScript event loop?</li><li>Explain when to use let , var , const</li></ul><p><strong>CSS/HTML-related questions:</strong></p><ul><li>What is HTML?</li><li>Accessibility in CSS</li><li>What’s area tag? (can be any tag)</li><li>Tell about flexbox and grid : what are their advantages?</li><li>Tell about media queries and responsive design in CSS</li></ul><h4>React-related questions</h4><ul><li>Explain useStatevs useRefhooks</li><li>What is useEffect hook?</li><li>What is useCallback hook?</li><li>Global vs Local state?</li><li>What are functional components?</li><li>When do you need to use class-based components?</li><li>How can you manage the global state in React application? (here you can list the most popular tools like Redux etc.)</li><li>When would you use Context API?</li></ul><blockquote>Yes, I don’t give answers to these questions: make an effort and find answers on Google, how else would you remember the answers? 😉</blockquote><p>Few last things that I want to add in the end:</p><ul><li><strong>Coding interviews are not broken</strong>: it is time to get rid of this idea. When you think like this you are programming yourself to expect the worst from the interviews. This might be the reason why you can’t pass them. Try to look at the coding interviews as a challenge, a fun adventure and an opportunity to meet interesting people and learn something new.</li><li><strong>Every company has a different interview process</strong>: it’s up to every company to decide how they want to interview people and what questions to ask. At the end of the day: they need to enjoy working with You, right? But it means that it’s simply impossible to know all possible questions and tasks that you might get during interviews.</li><li><strong>Be yourself during interviews:</strong> don’t tell everything that interviewers ‘want to hear’. If you don’t know the answer acknowledge it (nobody knows all the answers!). If you need to use Google during coding in zoom session, that’s okay too!</li></ul><blockquote>Once I was given a React task in <a href="https://codepen.io/">codepan</a> and I literally don’t remember by heart a proper React syntax without my IDE so I told about that and opened one of my React projects in VS Code to look for examples. They were okay with that!😅</blockquote><ul><li><strong>Always ask for feedback</strong>: look at the interview as your opportunity to improve and learn. Either you pass an interview or fail: ask them to give you feedback, especially about your technical tasks. It’s going to help you to improve your skills and get to know about your gaps.</li><li><strong>You have to interview a company as well</strong>: you don’t need any job where you won’t even be happy. Make sure that you also interview them and that you choose the best company for You. Ask about the job’s responsibilities, their expectations from you and the company’s culture. <em>You have more chances to succeed as a Developer if you are surrounded by the right people that inspire and motivate you</em>.</li></ul><p>Happy coding! And I wish You to find your dream job sooner!</p><blockquote><em>If you like my article you can support me by </em><a href="https://www.buymeacoffee.com/olesiamart"><em>buying me a coffee</em></a><em> ☕️</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e406cd273216" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100 Days of code: does it worth your efforts?]]></title>
            <link>https://medium.com/@olesia.martushkanova/100-days-of-code-does-it-worth-your-efforts-57f6b5a31f31?source=rss-54b41907d574------2</link>
            <guid isPermaLink="false">https://medium.com/p/57f6b5a31f31</guid>
            <category><![CDATA[my-coding-journey]]></category>
            <category><![CDATA[100daysofcode]]></category>
            <dc:creator><![CDATA[Olesia]]></dc:creator>
            <pubDate>Sat, 16 Jul 2022 01:51:45 GMT</pubDate>
            <atom:updated>2022-07-18T06:50:56.813Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3Ep1GD1Z_CocSVAJJ2qZfA.jpeg" /><figcaption><a href="https://www.pexels.com/photo/man-in-grey-sweater-holding-yellow-sticky-note-879109/">Photo by hitesh choudhary</a></figcaption></figure><h3>Pre-story</h3><p>I was working as Automation Engineer. Everything was really great but I had a feeling that I wanted more. “Why don’t I build some website that I can use to experiment with different types of automation tests” — I thought once. That seemed like an awesome idea, however, there was one <strong>BUT</strong>: I didn’t have any development skills. 😅 Few more days of thinking and I made a decision to push myself into the <a href="https://www.100daysofcode.com/">#100daysofcodechallenge</a> and track everything on social media (I thought that public commitment would motivate me to not give up):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*3CnZC3DRlBh36C6hBj1nFA.png" /><figcaption>My post related to #100daysofcode</figcaption></figure><h3>My goal for the 100 Days of code challenge</h3><p>I think when you are working full time it’s very easy to get into a trap of “comfort zone”: you do coding at work but do you actually keep learning something new? Do you still have enough challenges, especially if you’ve been working on the same project for quite a long time?</p><p>That was my case: I felt that I want to progress more, I didn’t want to resign but I also wanted to leave my established Automation testing comfort zone. And most important: I wanted to make sure that I will never feel too comfortable as a software engineer again.</p><p>So<strong> my main goal was to build a habit of learning every day</strong>: it would have to be something additional that I might don’t do currently at my job but also something that I can use for work later.</p><h3><strong>My first weeks of the 100 Days of code challenge</strong></h3><p>The beginning is always the hardest! I remember my first days of a challenge really well: I felt like the whole world was trying to stop me from progressing 😆</p><p>After a full day of work, it was really hard to focus on learning, even one hour was hard: I had to force myself to learn. I didn’t sleep enough and was constantly tired. I didn’t go out much at weekends anymore and spent every free minute coding. Once someone at work even mentioned that I looked stressed out.</p><p>At the same time, React seemed so interesting and I was excited to see my first simple app running!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r8-4pCWigncrzNEF9xgziQ.png" /><figcaption>My very first App (looks ugly!): day #3 of my challenge</figcaption></figure><h3><strong>My progress and feelings from 100 Days of code</strong></h3><p>No matter what: I kept learning, day after day during all 100 days. I had a one-week break when I went to Australia and it really helped me to release some pressure. Time passed and my coding challenge had been completed, I learned a lot:</p><ul><li>React from scratch,</li><li>CSS including things like flexbox, grid and best practices of responsive design,</li><li>my first React application was up and running on Github pages 👊</li></ul><p>I was really happy learning software development and I truly fell in love with it! I met a lot of great people online who also were doing the same challenge, we supported each other and were learning from each other. I had amazing 100 days!</p><h3>Life after 100 Days of code</h3><p>The truth is that 100 days is not even that many days. I have learned quite a lot during my challenge but I felt like it was still not enough.</p><p>I already had some basic development skills and I realised that either I keep learning and progressing as a developer or I stop, focus on my automation testing job and return to my normal life. But the second option meant that I would simply forget everything that I learned during the last 100 days and all my sleepless nights were for nothing 😅</p><p>Guess what I have chosen? Of course, Option 1: progress more as a <strong>Developer </strong>and<strong> </strong>I have moved to 365 Days of code challenge:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l0v5LYMf0-LTwDPfqf6VKQ.jpeg" /><figcaption>Day 101 of a future 365 days of code challenge</figcaption></figure><h3>Today</h3><p>It’s the 16th of July, 2022 and Day 245 of my coding challenge. Well, I had a few long breaks cause of problems in my personal life… But every time I stand up and try again and again to stay consistent in my learning journey.</p><p>During my challenge, I built more React projects, improved my coding skills, met even more awesome people and successfully transited to the Developer role at work (almost one year ago!)🔥</p><p>Even more: soon I am starting a new job, as a Developer! I have passed tech interviews, got a few job offers and picked one that looks the most challenging 🤞</p><p>I am learning the concepts of serverless applications with AWS, keep practising with React and really trying to get better as a Developer. And I am very happy to keep learning!</p><h3>Considering starting 100 Days of code challenge?</h3><p>Here are a few pieces of advice that I would give to you:</p><h4>#1 Accept straight away that you will <strong>not</strong> learn everything in 100 days.</h4><p>It is simply impossible: look at this challenge as a way to get a useful habit, and maybe improve in some areas or get some basic understanding of programming (if you are a newbie).</p><h4>#2 Make a plan</h4><p>What do you want to learn? What technologies or concepts in programming do you want to explore? Create a plan! Before starting your challenge research all things that you want to learn, list project ideas and find online tutorials that you are going to use.</p><h4>#3 Sleep and rest</h4><p>Don’t repeat my mistakes. Sleep matters! Since you can’t learn everything in 100 days, there is no point to damage your health and make yourself stressed out. In fact, people who start their 100 days of coding with coding till 3–4am tend to give up in the first 10 days. You don’t want to give up!</p><blockquote>This coding challenge is about consistent learning, not consistent not sleeping.</blockquote><h4>#3 It’s okay to take breaks and make up your own rules</h4><p>It’s <strong>Your</strong> challenge: you can decide on what rules you want to follow and what rules work better for you. If life happens and you have to pause your challenge for some time: it’s Okay! Just come back when you feel better 😉</p><p>Happy coding! I really hope that my experience might inspire you to start working on a habit of learning every day.</p><blockquote><em>If you like my article you can support me by </em><a href="https://www.buymeacoffee.com/olesiamart"><em>buying me a coffee</em></a><em> ☕️</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57f6b5a31f31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I am happy to receive negative feedback about myself, as a developer]]></title>
            <link>https://medium.com/@olesia.martushkanova/i-am-happy-to-receive-negative-feedback-about-myself-as-a-developer-29f74bcc0938?source=rss-54b41907d574------2</link>
            <guid isPermaLink="false">https://medium.com/p/29f74bcc0938</guid>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[developer-life]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Olesia]]></dc:creator>
            <pubDate>Wed, 15 Jun 2022 21:25:30 GMT</pubDate>
            <atom:updated>2022-06-15T21:41:31.050Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*6pMRnQRw1xKpNUppENj6Jg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jasonrosewell?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jason Rosewell</a> on <a href="https://unsplash.com/s/photos/feedback?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I love being a Developer. I love everything about my profession: challenges, continuous learning, exploring new frameworks and technologies, communicating with my team members and really seeing how the software I am building is growing and improving.</p><p>And I realise that I am not perfect (nobody is really!). I keep working on my skills and I am always willing to improve.</p><p>So when I receive negative feedback about my performance I appreciate it but only <strong>IF</strong>:</p><ul><li>You give me real examples of what I have done wrong.</li><li>You provide me with real advice on what I should have done instead to make it right.</li><li>You have given me specific expectations (that I have obviously ignored for some reason?) before providing negative feedback.</li><li>You actually spend enough time working closely with me to be able to estimate and judge my skills.</li><li>If I have gaps in my skills and knowledge: you tell me specifically what is it that I don’t know good enough (for example: “<em>I’d recommend investing time into becoming more comfortable with applying JavaScript functions like find, filter, map, and reduce</em>”).</li></ul><p>I know that delivering bad feedback could be very hard as well and I hope that this article helps someone to give negative feedback without making anyone feel bad.</p><p>And if I will be working with You (my reader) one day, please, remember: I care about my job and I want to do it really well, I want <strong>us</strong>, as a team, to <strong>succeed</strong> and you are absolutely welcome to help me by giving reasonable and constructive feedback 😉.</p><p>Happy coding!</p><blockquote><em>If you like my article you can support me by </em><a href="https://www.buymeacoffee.com/olesiamart"><em>buying me a coffee</em></a><em> ☕️</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29f74bcc0938" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Move from Manual to Automation Test role: guide based on real experience]]></title>
            <link>https://medium.com/@olesia.martushkanova/move-from-manual-to-automation-test-role-guide-based-on-real-experience-b8cc1470c8de?source=rss-54b41907d574------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8cc1470c8de</guid>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Olesia]]></dc:creator>
            <pubDate>Sun, 10 Apr 2022 09:10:10 GMT</pubDate>
            <atom:updated>2022-04-19T02:01:27.139Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*swDTi1eapgC742JdlwwKug.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@hay_leigh?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">hay s</a> on <a href="https://unsplash.com/s/photos/change?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Few words about myself</h3><p>I have started to work in IT industry as a Manual Test Engineer. However, after less than one year of fully manual testing responsibilities I had a feeling that I wanted more, more than clicking the same buttons over and over again.</p><blockquote>Of course, manual testing is not just about “clicking buttons”: it’s a process that includes analysing the business requirements and making sure that software satisfies customers needs. But during that time it seemed for me like “clicking buttons”.</blockquote><p>I started looking into programming and built my first automation tests at home. That’s was it: something that made me feel the excitement! So my next testing roles included not only manual testing anymore but also an active contributions to building and extending automation tests.</p><p>Finally, after three years I have got an amazing opportunity where my main responsibilities required setting up many automation test frameworks from scratch and building automation test strategy to support continuous deployment. (<em>Dreams came true</em>!)</p><p>I have fully moved to Automation Engineer role. It wasn’t easy and I had made a lot of mistakes on my way there, <strong>I have also learned a lot</strong>.</p><p>In this article, I’ll be sharing my recommendations on ‘How to move from Manual to Automation Test role that is based on all my mistakes and what I have learned.</p><h3>Who are You</h3><p>This simple guide is aiming to help someone who doesn’t have any technical skills yet, who is familiar with manual testing but looking to progress as Automation Test Engineer. You might be even working as a Manual Tester but you don’t know how to start learning automation.</p><h3>Step 1: Master Manual testing</h3><h4>- What?! But I want to do automation testing only!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*eDfc_ayHS5wiWDUM7LzQig.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@haughters?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jamie Haughton</a> on <a href="https://unsplash.com/@haughters?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I know that you do! But to build good automation tests you first need to have a really good idea on What needs to be tested. <strong>Your automation tests have to bring value.</strong> It’s an expensive resource, nobody needs automation tests just for the sake of having automation tests.</p><blockquote>Good automation tests help a development team to move faster, bring confidence in their changes, help to catch breaking bugs early.</blockquote><blockquote>Bad automation tests: become a problem for everyone in a team, they are a bottleneck that pulls everyone down, wastes your time and brings lots of disappointment. It is something that every developer eventually starts to ignore (and hate deep down…).</blockquote><blockquote><strong>It is better to not have any automation tests than to have bad automation tests.</strong></blockquote><p>To know what testing scenarios you need to automate, you have to know a lot about manual testing:</p><ul><li>types of tests,</li><li>how to decide what parts of the application are the most important to not break,</li><li>how to properly validate the testing result</li></ul><p>and</p><ul><li>how to avoid redundant tests. <a href="https://www.qamadness.com/5-test-design-techniques-qa-engineers-should-know/">Test design technics</a> become very handy here. Please, get to know them.</li></ul><p><strong>Master your manual testing skills before diving into automation</strong>.</p><h3>Step 2: Prioritize learning programming over learning automation testing tools</h3><p>Many manual tests make this mistake: they learn only the very basics of programming and jump straight away into learning automation testing tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*_OSBO9z0wi9S1a2C4OiqQQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@quinoal?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Quino Al</a> on <a href="https://unsplash.com/s/photos/fall-down?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><blockquote>I wasn’t an exception here: I was in a situation where I was left as the only Test Engineer in our team. Developers didn’t contribute to automation tests. I took the responsibility to build a new automation framework for end-to-end regression testing.</blockquote><blockquote>However, I was learning “on the go”, I didn’t have enough time: I was saving myself from hours and hours of manual testing. Later on, I realised that it was a big mistake: catching up on all my “basic programming” gaps was way harder than if I would have learned it properly in time.</blockquote><p>There are a few main reasons why programming skills matter for Automation Test Engineers too:</p><ul><li>You won’t find a perfect bug-free test automation tool. You will often have to come up with workarounds to solve your issues and keep progressing with automation testing.</li><li>Good automation tests require proper management of test data: preparing data for tests and cleaning up it in the end. 99% of the time, it requires involving API, dealing with Databases or other tricks: it is something that you write in the code, that test automation tools don’t provide out of the box.</li><li>Knowing important basics of programming like <a href="https://thevaluable.dev/dry-principle-cost-benefit-example/">DRY</a> and <a href="https://dev.to/kwereutosu/the-k-i-s-s-principle-in-programming-1jfg">KISS</a> principles helps to keep test automation code clean. It means that you will be able to maintain this code and your test automation will be bringing value for a long time.</li></ul><h3>Step 3: Choose your first programming language and start learning</h3><p>Now, there is no one right answer to this question: “<em>What programming language should you, as a future Automation Test Engineer, learn</em>?”.</p><p>Honestly, I think that it doesn’t matter too much in a long run: once you know the basics of programming you can pretty quickly learn any new language. However, you ideally want to start practising building automation tests as early as possible (<em>we will talk more about that in Step 4</em>).</p><p>There are a few approaches that can help you to decide on the programming language:</p><ul><li>If you are already working as a Manual tester there might be some automation tests built already by your teammates. You can choose to learn the language that is used for automation testing in your current job. It’s going to be so much easier for you because you will always have someone to help you and you can start writing your first automation tests really soon.</li><li>If you are either not working anywhere or there are no automation tests at your current job, make a research: open any popular job searching website and look for the “Automation Test Engineer” roles. Check the requirements and what programming language is mentioned the most in open roles. Then go ahead and learn it.</li><li>If you still don’t know: learn <a href="https://www.codecademy.com/learn/introduction-to-javascript">JavaScript</a>. This will never be a wrong choice because JavaScript-based test automation tools are so popular nowadays. They are the best to use in many cases + JavaScript is easy to start with.</li></ul><blockquote>This is my personal opinion, please feel free to disagree. My first programming language was Java. Then I learned some C# and used it for automation testing. Eventually, I switched to JavaScript and TypeScript. TypeScript is the main language that I choose for automation testing.</blockquote><h3>Step 4: Build Your first Automation tests</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*TdQuleJ-p0Bh5yAqdugjsg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jamesamolnar?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">James A. Molnar</a> on <a href="https://unsplash.com/s/photos/wall-e?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Step 4a: Learn about types of automation tests</h4><p>“<em>Test automation</em>” is a very broad term. To learn about types of automation tests you need to know about <a href="https://www.testim.io/blog/test-automation-pyramid-a-simple-strategy-for-your-tests/">Test Automation Pyramid</a>.</p><p><strong>Test Automation Pyramid is basic and key knowledge for every Automation Test Engineer</strong>.</p><p>However, you don’t need to become good in all types of automation tests straight away. For instance, <a href="https://www.xenonstack.com/insights/what-is-unit-testing">unit tests</a> are usually written by developers. As a Test Automation Engineer, you most likely won’t be writing any unit tests (it’s good to know about them anyway!).</p><p>I would advise starting with <a href="https://www.guru99.com/end-to-end-testing.html"><em>end-to-end automation tests</em></a><em>.</em></p><p>Most companies hire Automation testers to write end-to-end tests. They are also easier to start with because you can visually see how your tests interact with application.</p><h4>Step 4b: Choose test automation tool</h4><p>Now, when you know some programming, it’s time to use it in practice: it’s time to learn the actual automation testing!</p><p>Obviously, there are so many test automation tools available on the market. Initially, it is very hard to pick one. <strong>Consider these points:</strong></p><ol><li>How often this tool is mentioned in jobs requirements (<em>yep, please do research again, it is different for every country</em>).</li><li>Available official documentation and tutorials: open the website for the particular automation tool and have a look at docs. Good official documentation matters a lot, it’s something that you will be using a lot: does it look clear enough? Are there any tutorials or tips on how to start using this tool for automation testing?</li><li>How popular is the automation tool in the tech community. There are always some issues with all automation tools. Try to google about them anything and see how many results you get. Open <a href="https://stackoverflow.com/">Stack Overflow</a> and check how many questions about this tool are there.</li></ol><h4>Step 4c: Automate at home</h4><p>The best way to learn test automation is to start building automation tests!</p><p>You can build a small test project at home and a few simple automation tests. For example, my first automation tests were testing Facebook. I had a test for login and logout. I also built a test that creates a post on Facebook. But really you can test any website or application: the main idea is to practice as much as possible.</p><blockquote>Don’t forget to create <a href="https://github.com/">GitHub</a> account and save your test automation project there. It will help you with looking for a job later (<em>Step 5</em>).</blockquote><h3>Step 5: Get Automation Test Engineer job</h3><p>Now, when you have learned programming and when you have built your first automation tests, you want to start working as Automation Test Engineer as soon as possible. You will never learn as much at home as you can learn on a real-life big project.</p><ul><li><strong>In ideal scenario,</strong> if you are already working as a manual tester, go ahead and tell your manager that you want to contribute to automation testing (if there is any) or build first automation tests (if there is nothing yet). When you have invested your personal time and efforts in learning there is a huge chance that your current employer would be very happy to support you. After all: you want to bring more value to the company!</li><li><strong>If you don’t have any tech job currently</strong>: start applying for Test Automation roles. This can be tricky: make sure that when you are having interviews you are 100% clear about your desire to do automation testing. <strong>Let them know that you are not willing to be a manual tester anymore.</strong></li></ul><blockquote>The reality is that 90% (maybe even more…) of open Test roles mention in their job requirements automation testing skills but only a few such roles are actually automation testing roles. Most of the time you can end up being stuck in manual testing and writing very primitive automation.</blockquote><h3>Some advice about Test Automation tools that you can learn</h3><blockquote>Most of my experience is based on web automation testing and my advice regarding tools is aligned with it.</blockquote><h4>1. <a href="https://playwright.dev/">Playwright</a></h4><p>This is my favourite web test automation tool! I believe that Playwright is one of the best on the market nowadays for web automation. It supports 4 programming languages, has very clear documentation and amazing maintenance. Playwright is built by Microsoft team so there are many very talented developers working every day to make Playwright better.</p><p>You can also join <a href="https://playwright.slack.com/join/shared_invite/zt-smuwd93l-Itgcv8IKYaF~wRnLQl4UMg#/shared-invite/email">Playwright Slack channel</a> and ask any questions there. Every time when I ask them anything I get the answer and help straight away.</p><h4><a href="https://www.cypress.io/">2. Cypress</a></h4><p>Cypress is very easy for beginners. It has simple syntax, good documentation and it is extremely popular: there are so many tutorials available on Google!</p><p><a href="https://www.cypress.io/dashboard">Cypress</a> has really nice Dashboard that also makes your first test automation experience more enjoyable.</p><h4><a href="https://www.selenium.dev/documentation/webdriver/">3. Selenium</a></h4><p>Selenium is so old that everybody knows about it! However, I personally feel that it is good to at least get familiar with Selemium. Selenium was the first web driver and really all automation testing has started from Selenium. It is old but it is still good. Plus, there are millions of tutorials about Selenium available on Google and you can literally use any programming language with Selenium.</p><h3>If you are stuck in automation testing</h3><p>If you stuck: ask other testers to help you!</p><p><strong>Here is a </strong><a href="https://www.ministryoftesting.com/slack_invite"><strong>Ministry of Testing slack</strong></a><strong>:</strong></p><ul><li>join it and</li><li>find automation channel: there are people around the world that would be happy to help you! (I am one of them by the way 😉).</li></ul><p>I hope my article is at least a little bit helpful. Happy automation testing, enjoy your journey!</p><blockquote>If you like my article you can support me by <a href="https://www.buymeacoffee.com/olesiamart">buying me a coffee</a> ☕️</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8cc1470c8de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Git commands that you want to remember by heart]]></title>
            <link>https://medium.com/@olesia.martushkanova/4-git-commands-that-you-want-to-remember-by-heart-912dfa16e2c6?source=rss-54b41907d574------2</link>
            <guid isPermaLink="false">https://medium.com/p/912dfa16e2c6</guid>
            <category><![CDATA[git-commands]]></category>
            <dc:creator><![CDATA[Olesia]]></dc:creator>
            <pubDate>Sun, 27 Mar 2022 05:05:12 GMT</pubDate>
            <atom:updated>2022-04-19T19:41:23.711Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMKX0U0wkehkwKjYy4ZXZg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@praveentcom?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Praveen Thirumurugan</a> on <a href="https://unsplash.com/s/photos/git?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I remember when I have just started to learn programming: Git looked so scary and even magical for me! Every time when I needed to create a branch or do anything Git-related I called a senior developer from my team.</p><p>Today Git seems easy for me and I would like to share 4 Git commands that I use literally every day, in 99.9% of the time these commands are more than enough to remember by heart.</p><p>We are going to imagine that I am, as a Developer, starting to work on a new feature.</p><h3>Command #1: Create a new branch</h3><p>First of all, I need to create a new branch where I can work. (I assume that everyone knows that pushing straight away to `<em>master</em>` branch is not a good idea?)</p><p>For this purpose I run in my terminal:</p><pre>git checkout -b feature-my-new-branch-name</pre><blockquote>-b means branch</blockquote><blockquote>git checkout means switch to a different branch</blockquote><blockquote>Ideally, you would be creating a new branch from the master branch to get all the latest production code.</blockquote><h3>Command #2: S<strong>tage changes</strong></h3><p>Now, after I have already done some code changes I want to push them. So first of all I need to stage my changes.</p><p>In most cases, I want to push all my local changes so I am specifically doing that:</p><pre>git add -A </pre><blockquote>-A means `stage all changes`</blockquote><h3>Command #3: Commit changes</h3><p>I prefer to do small but very frequent commits to my branch.</p><blockquote>Small but very frequent commits give you such main benefits:</blockquote><blockquote>1) you can easily track your changes;</blockquote><blockquote>2) in case of error, it is easy to revert the breaking change back;</blockquote><blockquote>3) easier to add specific commit messages that tell exactly what has been done (again, in future it might help to track the bug).</blockquote><p>To commit my changes I simply run:</p><pre>git commit -m &quot;My commit message that discribes my change&quot;</pre><h3>Command #4: Push changes</h3><p>Finally, the last step is pushing my changes to my remote git branch:</p><pre>git push</pre><p>At this step I usually get an error that looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*RUgWt72yO7Sc6DGr_a5o_g.png" /></figure><p>This error tells me that my remote git branch doesn’t exist yet, it only exists on my local. And it makes sense: we haven’t created a remote branch yet.</p><p>But normally I don’t bother to remember this command and I just copy-paste it and run:</p><pre>git push --set-upstream origin my-branch-name</pre><h3>What if there are conflicts or I need to merge the latest master branch changes?</h3><p>Yes, conflicts happen a lot after you pull the latest changes from the master branch. And yes, you can run git commands to solve them. But I personally prefer to use <a href="https://desktop.github.com/">Github Desktop</a> for all “more advanced” Git-related activities.</p><blockquote>Github Desktop makes life easier, it’s 100% free and proves my idea that remembering only these 4 described above Git commands is more than enough.</blockquote><p>Happy coding 😉</p><blockquote><em>If you like my article you can support me by </em><a href="https://www.buymeacoffee.com/olesiamart"><em>buying me a coffee</em></a><em> ☕️</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=912dfa16e2c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My favourite ideas from The DevOps Handbook]]></title>
            <link>https://medium.com/@olesia.martushkanova/my-favourite-ideas-from-the-devops-handbook-ac72deff0122?source=rss-54b41907d574------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac72deff0122</guid>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Olesia]]></dc:creator>
            <pubDate>Thu, 17 Mar 2022 20:41:22 GMT</pubDate>
            <atom:updated>2022-04-19T19:42:25.395Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qJroYwcef7QHpDSQ5EVgFQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@marjan_blan">Marjan Blan</a></figcaption></figure><h3>About The DevOps Handbook (pre-story)</h3><p>Inspired by <a href="https://medium.com/@olesia.martushkanova/the-phoenix-project-what-i-as-a-software-engineer-have-learned-from-this-novel-7845e9b96e1">The Phoenix Project</a> I decided to read <a href="https://www.kobo.com/ww/en/ebook/the-devops-handbook-second-edition?utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=nz-kplu-max&amp;gclid=Cj0KCQjwuMuRBhCJARIsAHXdnqP_XpN5zBPj18q9rBupXJFNtNc1LchPJXa_00yxNgIcKBLDljHkgcgaAje0EALw_wcB">The DevOps Handbook</a>.</p><p>Plus I am working in the company that follows all the best DevOps practices: from continuous learning and improvements to investing in automation testing and even automation deployment. Every day for the last 2 years I’ve been learning about DevOps at work so I’ve decided to finally read more about it!</p><blockquote>We like to say in Ukraine: “It’s better late than never”.</blockquote><p><a href="https://www.kobo.com/ww/en/ebook/the-devops-handbook-second-edition?utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=nz-kplu-max&amp;gclid=Cj0KCQjwuMuRBhCJARIsAHXdnqP_XpN5zBPj18q9rBupXJFNtNc1LchPJXa_00yxNgIcKBLDljHkgcgaAje0EALw_wcB">The DevOps Handbook</a> explains in detail how to implement DevOps in any organisation and explains <strong>DevOps</strong>.</p><p>In this article, I am going to highlight my favourite thoughts from <a href="https://www.kobo.com/ww/en/ebook/the-devops-handbook-second-edition?utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=nz-kplu-max&amp;gclid=Cj0KCQjwuMuRBhCJARIsAHXdnqP_XpN5zBPj18q9rBupXJFNtNc1LchPJXa_00yxNgIcKBLDljHkgcgaAje0EALw_wcB">The DevOps Handbook</a>. You will not find any explanation for these ideas, I am leaving you the opportunity to build your own opinion, my dear Reader.</p><h3>My favourite ideas from the DevOps Handbook</h3><ol><li>Everyone is constantly learning, fostering a hypothesis-driven culture where the scientific method is used to ensure nothing is taken for granted.</li><li>Instead of a culture of fear, we have a hight-trust, collaborative culture, where people are rewarded for taking risks.</li><li>Everyone owns the quality of their work.</li><li>Our releases are controlled, predictable, reversible and low stress.</li><li>Instead of large batches of work being processed sequentially, our goal is to have testing and operations happening simultaneously with development and build quality into every part of our value stream.</li><li>Our goal is to decrease the amount of time required for changes to be deployed into production and to increase the reliability and quality of our software.</li><li>Stop starting, start finishing.</li><li>In order to move faster, we gain to automate the significant portion of work or reorganize the teams so they can deliver value to customers themself.</li><li>A problem common to any technical improvement effort is how to properly prioritize it — after all, organizations that need it most are those that have the least amount of time to spend on improvement.</li><li>Most successful organizations have in common one thing — a high-trust culture that enables all departments to work together effectively, where all work is transparently prioritized.</li><li>Testing, operations, and security as everyone’s jobs, every day.</li><li>We want to encourage learning, help people overcome learning anxiety, help ensure that people have relevant skills and a defined career road map.</li><li>Without automated testing the more code we write, the more time and money is required to test our code.</li><li>Our ability to meaningfully critique code changes goes down as the change size goes up.</li><li>DevOps must allow innovation and the resulting risks of people making mistakes. Yes, you will have more failures in production. But that’s a good thing, and should not be punished.</li></ol><h3>Would I recommend reading The DevOps Handbook?</h3><p>Absolutely yes!!!</p><p>The DevOps Handbook is easy to read, its material is well-organized and structured. In every chapter, you will find not just a theory but proof of how your organization could be transformed in a better way if you start practising this theory.</p><p>The DevOps Handbook focuses your attention on the most important: only automated testing and deployment are not enough to build a high-effective development process. Everything starts with the right culture, the right mindset and everyone in your organization should inspire each other to constantly learn and experiment.</p><p>The DevOps Handbook encourages you to leave your comfort zone, take a risk, become more cross-functional and explore new areas of software development related work.</p><h3>Additional conclusion</h3><p>One of the impressions I have got after reading The DevOps Handbook is that in order to survive, as a software engineer, in a DevOps-based organization I have to become some sort of Super Hero: I have to know almost everything at every stage of the development process to be able to fully take the responsibility of delivering software from end to end.</p><p>And I guess sometimes I feel that it is almost impossible, I feel scared that I won’t have enough skills to become this Super Hero who meets all DevOps standards. After all, it is a lot to learn!</p><p>However, I don’t give up because I have seen such Super Heros!</p><p>Happy learning 😉</p><blockquote><em>If you like my article you can support me by </em><a href="https://www.buymeacoffee.com/olesiamart"><em>buying me a coffee</em></a><em> ☕️</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac72deff0122" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Phoenix Project: what I, as a Software Engineer, have learned from this novel]]></title>
            <link>https://medium.com/@olesia.martushkanova/the-phoenix-project-what-i-as-a-software-engineer-have-learned-from-this-novel-7845e9b96e1?source=rss-54b41907d574------2</link>
            <guid isPermaLink="false">https://medium.com/p/7845e9b96e1</guid>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Olesia]]></dc:creator>
            <pubDate>Fri, 29 Oct 2021 05:14:22 GMT</pubDate>
            <atom:updated>2022-04-19T19:42:52.810Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Phoenix Project: <strong>what I have learned from this novel as a Software Engineer</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iBLQjd7MaQDpRXaI7yLW9Q.jpeg" /></figure><h3>The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win</h3><blockquote>“Bill is an IT manager at Parts Unlimited. It’s Tuesday morning and on his drive into the office, Bill gets a call from the CEO.</blockquote><blockquote>The company’s new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill’s entire department will be outsourced.</blockquote><blockquote>With the help of a prospective board member and his mysterious philosophy of The Three Ways, Bill starts to see that IT work has more in common with manufacturing plant work than he ever imagined. With the clock ticking, Bill must organize work flow, streamline interdepartmental communications, and effectively serve the other business functions at Parts Unlimited.</blockquote><blockquote>In a fast-paced and entertaining style, three luminaries of the DevOps movement deliver a story that anyone who works in IT will recognize. Readers will not only learn how to improve their own IT organizations, they’ll never view IT the same way again.” -&gt; <a href="https://books.google.co.nz/books/about/The_Phoenix_Project.html?id=qaRODgAAQBAJ&amp;source=kp_book_description&amp;redir_esc=y"><strong>From Google books</strong></a></blockquote><p>We are used to reading about successful IT stories. “The Phoenix Project” shows us everything from the opposite side: what happens when IT people have no idea what business people are trying to achieve.<br>At the same time business people, people with very minimal or even zero technical knowledge, make technical decisions.</p><h3>What have I learned from this novel as a Software Engineer?</h3><h4>1. Communication is key #1 to success</h4><p>All the positive improvements in The Phoenix Project happen when technical leaders finally meet in person with Dick (the big boss who manages the company’s business strategy). Bill finally asks the main question: <em>“What does the business is trying to achieve? And what IT department can help them with?”.</em></p><p>Couldn’t they ask it from the very beginning? They could but they didn’t. They were trying to fix lots of technical issues, focusing on software improvements that are not important for the business without even knowing where the company is heading, what the main business goal is, what their customers even need.</p><p>Simple regular and established communication between business people, sales and technical engineers helps everyone win and avoid time and effort being wasted.</p><p><strong><em>As a Software Engineer, I have learned…</em></strong></p><p>from this lesson, to think more about the business part of my everyday work. I want to fully understand the product I am working on, understand its main purpose and how can I help the company to succeed. I have learned that my communication skills and ability to understand the business vision for a software product are often even more important than my technical skills.</p><p><em>Here is a tip for you:</em> ask yourself: “What is the business strategy for the product I am working on? What value the features I am developing can bring to our customers? Do I do enough to help our business win?”.</p><p>If you don’t know the answer, please, go ahead and talk with your teammates, product owners, managers or salespeople. Practice regular communication.</p><h4>2. You have to know how to deal with unplanned work</h4><p>In The Phoenix Project Bill is learning about the main categories of work. One of them is unplanned work.</p><p>Unplanned work is a destructive type of work. It appears all of the sudden, makes you nervous and ruins all your plans. It’s something you want to avoid.</p><blockquote>Unplanned work takes you away from your goal. That’s why it’s so important to know where your unplanned work is coming from. -&gt; <strong>“The Phoenix Project, chapter 15”.</strong></blockquote><p><strong><em>As a Software Engineer, I have learned…</em></strong></p><p>that wise time management and work estimation are critical to achieving your goals. Oh wait, didn’t I know that before? Isn’t it obvious?</p><p>Yeah, I guess it is BUT from now on I always plan unplanned work!</p><p>What if there is a bug that has to be fixed ASAP or a failing CI pipeline blocking everyone? Of course, all my other work suddenly gets “less important” and I am going to leave it and focus on fixing urgent issues. And the truth is: in the everyday software development real world it happens all the time. We have to deal with unplanned work all the time!</p><p>That’s why I am learning to predict it and plan some extra time in case it happens. Thinking about unpredictable issues which can affect your productivity, as a software engineer, or all your engineering team, helps you to achieve more and reach your goals.</p><p><strong>3. DevOps is a Culture</strong></p><p>I am one of those people who believe in<strong> </strong><em>DevOps as a Culture</em>.</p><p>I think ‘The Phoenix Project’ shows it’s every well: DevOps is not just a job title, it’s not just a role. DevOps is not even just a modern work approach.</p><p><em>DevOps is a Culture, a culture of continuous learning and improvement.<br></em>Modern IT is impossible without adopting a DevOps culture.</p><p>In “The Phoenix Project” Bill and his team make amazing progress after they start questioning everything they do every day and try to improve it.</p><p>They make releases to production more frequent and automated, they implement automated testing and most important: they change their mindset to follow DevOps culture.</p><p>Of course, they do mistakes and learn from them. And they keep looking for better ways to do the same job. Even at the very end of the story, they still have lots of things to improve. And they still keep learning.</p><p><strong><em>As a Software Engineer …</em></strong></p><p>I have got inspired even more to keep learning every day. Every software engineer has to be a lifelong learner. I knew about it before reading “The Phoenix Project” and now I am focused even more on getting better every day.</p><p>It’s so easy to get in a trap and get used the things as it is and stop noticing toils in your everyday tech work. Something which seemed uncomfortable and manual on your first workday for the project eventually starts feeling normal if you don’t try to improve it.</p><p>The critical mindset: that’s what I practise as a Software Engineer.</p><p><strong>4. Don’t be that idiot who doesn’t ask for help</strong></p><p>Well, ‘The Phoenix Project’ isn’t exactly about it but at the end of the story Bill gets amazing new job opportunities and hears these supporting words:</p><blockquote>And remember that there are a lot of experienced people around you who’ve been on similar journeys, so don’t be the idiot that failed because he didn’t ask for help.</blockquote><p><strong><em>As a Software Engineer, I have learned…</em></strong></p><p>I guess it’s clear what I have learned: I am not an idiot 😅 (🤞)</p><h3>Thanks for reading my review!</h3><p>If you have already read “The Phoenix Project” book, I hope you love it as much as I do! And if you are about to read it soon: enjoy every page!</p><blockquote><em>If you like my article you can support me by </em><a href="https://www.buymeacoffee.com/olesiamart"><em>buying me a coffee</em></a><em> ☕️</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7845e9b96e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>