<?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 Kazuki Higashiguchi on Medium]]></title>
        <description><![CDATA[Stories by Kazuki Higashiguchi on Medium]]></description>
        <link>https://medium.com/@hgsgtk?source=rss-aec8ceaac4a2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Kazuki Higashiguchi on Medium</title>
            <link>https://medium.com/@hgsgtk?source=rss-aec8ceaac4a2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:39:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hgsgtk/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[Book review of “97 Things Every SRE Should Know”]]></title>
            <link>https://medium.com/@hgsgtk/book-review-of-97-things-every-sre-should-know-5382eda33604?source=rss-aec8ceaac4a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5382eda33604</guid>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Kazuki Higashiguchi]]></dc:creator>
            <pubDate>Mon, 06 Mar 2023 22:58:22 GMT</pubDate>
            <atom:updated>2023-03-06T22:58:22.481Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog post is a book review of “97 Things Every SRE Should Know” in O’Reilly.</p><p><a href="https://learning.oreilly.com/library/view/-/9781492081487/">97 Things Every SRE Should Know</a></p><p>This book has small 97 stories written by SRE engineers, which are key points for service reliability fields, such as on-call rotation, SLO adoption, etc. Those are categorized into four groups, zero to one, one to ten, ten to hundreds, and future. Therefore either people in a start-up company or people in an enterprise can enjoy this book and will find fit advice for them.</p><p>Speaking of my situation, I am working at <a href="https://autify.com/about">Autify</a> as a senior site reliability engineer. Prior to Autify, I was responsible for DevOps of a financial service in an e-commerce platform, including infrastructure budget management, account control, and security practices require by stock market requirements.</p><p>Still, I wanted to know how other engineers feel about their job. My current position is a kind of embedded SRE, working in a development team and handling both feature development and service reliability work. Therefore, I started reading this book to look for useful advice.</p><p>Fortunately, I found some useful advice for me. I’ll highlight some impressive advice in this book, and add my thoughts.</p><h3>One defining trait of an SRE is curiousity</h3><p>This book starts with the following paragraph at the Preface chapter.</p><blockquote>If there is one defining trait of an SRE, it would be curiosity</blockquote><p>This is definitely a true and universally defining trait in software engineering jobs. Operating software services is a challenging job because there are lots of unknown and unfamiliar events. One of SRE’s activities is joining on-call rotations. When we receive a pager, we often find new things for us and learn how our service works. For service reliability purposes, we should be interested in every technical field to a certain degree.</p><p>Additionally, it is not just technical, but also people too. Without that, we couldn’t create a meaningful SLO and achieve to resolve department-wide issues.</p><p>On a different note, in my case, I sometimes struggle with recognizing a gap of knowledge among engineers in the teams. It is quite natural because each engineer has a different technical background and experience. It can happen even among the same role’s developers, because of their experience difference, such as start-ups vs enterprises, industry differences, and technical specialties. It is often said that developers and system engineers (a.k.a. SRE, DevOps engineers, etc) have different focuses and interests.</p><p>I recalled the following phrase in the book “Staff Enginner’s Path”.</p><blockquote>The work that’s most important will often be the work that nobody else sees. It might be a struggle to even articulate the need for it, because your teams don’t have good mental models for it yet.</blockquote><p>From this retrospective, I thought an important value of an embedded SRE is to build good mental models for service reliability, operational excellence, and good operational standard level, in a development team.</p><p>Anyway, SRE activities and objectives are often cross-cutting concerns and they require us to collaborate with other teams smoothly. We need to be curious about people and the organization’s goal, to find a communication path.</p><h3>Error budgets provide a foundation for preparing for incidents</h3><p>In the chapter “<a href="https://learning.oreilly.com/library/view/-/9781492081487/ch04.html">Four Engineers of an SRE Seder</a>”, Jadob Scott, an engineer at Stripe, discusses his story to answer the question, “How can error budgets prevent my next serious incident?”.</p><p>His answer is:</p><blockquote>The oh-so-unfortunate truth is that error budgets are retrospective and cannot predict – let alone prevent – incidents. To her, we note that although error budgets can’t predict or prevent incidents, they provide a foundation for preparing for incidents.</blockquote><p>Error budgets are retrospective and cannot predict incidents, but provide a foundation for preparing for incidents. I felt this explanation is a good summary to prepare for the same situation I would have to answer this question.</p><p>Also, I recalled the paragraph in the prominent book “<a href="https://learning.oreilly.com/library/view/-/9781491929117/app02.html">Site Reliability Engineering</a>”.</p><blockquote>Error budgets eliminate the structural tension that might otherwise develop between SRE and product development teams by giving them a common, data-driven mechanism for assessing launch risk.</blockquote><p>It is a tool to balance SRE and product development without structural tension.</p><h3>Making work visible</h3><p>Most of the operational work is invisible and subject matter experts sometimes don’t have any idea of what portions are unclear for others.</p><p>Lorin Hochstein’s advice, an engineer at Netflix, is like having a sync session with SMEs.</p><blockquote>How do you learn from the experts inside of your organization? In general, the best way to facilitate skill transfer is to watch experts in action. Ideally, you’re working alongside them. Watch them solve real problems and document how they mitigated operational surprises: you see how they interpret signals, which tools they use, and you ask them how to make their decisions.</blockquote><p>I like this idea and referred this chapter from my presentation at a tech conference, Conf42 SRE.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fspeakerdeck.com%2Fplayer%2Fbff5a5a4030a4f4a8ab74613bdaf9110&amp;display_name=Speaker+Deck&amp;url=https%3A%2F%2Fspeakerdeck.com%2Fhgsgtk%2Fa-guide-to-joining-operational-work-in-your-new-devops-team&amp;image=https%3A%2F%2Ffiles.speakerdeck.com%2Fpresentations%2Fbff5a5a4030a4f4a8ab74613bdaf9110%2Fslide_0.jpg%3F21598134&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=speakerdeck" width="710" height="399" frameborder="0" scrolling="no"><a href="https://medium.com/media/e60329970a867f7b8ba96d64665ca48e/href">https://medium.com/media/e60329970a867f7b8ba96d64665ca48e/href</a></iframe><p>Additionally, he insisted on the benefit of narrative-style documentation.</p><blockquote>Narrative-style write ups take longer to write and longer to read. But, if the narrative is written well, people will happily read the whole thing</blockquote><p>I agree with this idea, too. My first option to start something new is to start with narrative-style documentation. For example, I use narrative-style documentation to consider a technical design, to write an incident postmortem.</p><p>Over time, I have changed my position from a learner to a storyteller, because it has passed 1 year and 2 months since joining my current company, Autify. I recently retrospect that I could improve my questions to subject matter experts. I can’t find a proper word, but I might have more suitable and polite phrases to ask questions to understand the current operation, despite the fact I was careful of my way to communicate with them. That’s probably because I didn’t understand a considerate fashion of English communication.</p><h3>Dedicate incident channel</h3><p>The SREs at Monzo recommended to set up a dedicated incident communication channel, and I am a fan of this idea. This idea allows us to gather the same place even we are in different team’s.</p><blockquote>A dedicated channel breaks down any existing silos such as existing organizational team structures and communication boundaries in favor of a new shared objective of everyone coming together to resolve the incident at hand.</blockquote><p>Besides, a creating new incident channel lets everyone know that we are in an emergency. Some people are good at noticing ongoing emergencies but others aren’t, depending on each attribute.</p><p>In addition to this practice, I like the idea to set up a channel to share new channel births. Let’s say I set up the new channel #incidents-20230226, and the birth of this channel is notified at the slack channel #notif-new-channels. Subscribers can notice that even if they are not direct stakeholders.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5382eda33604" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Work-life balance for software engineers – retrospective and plan for February 2023]]></title>
            <link>https://medium.com/@hgsgtk/work-life-balance-for-software-engineers-retrospective-and-plan-for-february-2034-9be7aa5b0c5e?source=rss-aec8ceaac4a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9be7aa5b0c5e</guid>
            <category><![CDATA[books]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Kazuki Higashiguchi]]></dc:creator>
            <pubDate>Wed, 01 Feb 2023 03:26:54 GMT</pubDate>
            <atom:updated>2023-02-01T03:27:27.357Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog post is a kind of personal essay to leave a retrospective on January 2023, and make a plan for February 2023. You can see the previous post at the following link. As a note, I am working at Autify as a senior site reliability engineer, and looking for a good work-life balance to prepare for the birth of my first kid.</p><p><a href="https://medium.com/@hgsgtk/plan-and-milestone-for-january-2023-2b134e930037">Plan and milestones for January 2023</a></p><h3>Retrospective</h3><p>The milestones I planned are as follows;</p><h4>Family milestones</h4><p>I prioritized a family issue and there are three milestones.</p><ul><li>Read 2 books about childcare and publish a book review -&gt; 8 books</li><li>2 days to think up a menu and cook -&gt; 5+</li><li>List up necessary tasks until our first child is born -&gt; done</li></ul><p>The result is 8 books. I’ve learned about parenting more than I expected. It was beneficial to know anti-patterns as a father that can annoy my wife.</p><p>Additionally, I found that reading English childcare books is a bridge between work and childcare. I am not a native English speaker, so I’ve trained my English skill for my business. Previously, the topics I chose were only software engineering but the mindset change to prioritize life with my family brought me a new topic. I got lots of new vocabulary from these books and YouTube videos. It is a precious discovery that I didn’t expect last year because it indicates the possibility that I can work on both important aspects, work and life, seamlessly.</p><p>Regarding cooking, I achieved the milestone. An issue of this milestone is hard to track the result. We often cook a meal and discuss a receipt, together. Also, the basis of the cooking is not day. There are three timing to cook theoretically, morning, lunch, and dinner. Still, I feel I succeeded in getting more trust from my wife. After the birth, I should be the duty with housekeeping, although the mother of my wife also is going to help us. I’ll keep improving my skill to prepare for it.</p><h4>Software engineering milestones</h4><p>They are not a top priority but I have three concrete milestones.</p><ul><li>Publish a blog about “Chaos Engineering(O’Reilly)” -&gt; still in progress</li><li>Publish one small blog related to technology used by current work. -&gt; zero</li><li>Read one book about architecting -&gt; 1 book</li></ul><p>Regarding small blogs, I started writing several drafts but haven’t finalized them yet. Considering other milestones, I should have changed this goal to discovering new learns that could be a topic of blogs. That’s because the main point is to be careful with spending meaningful time learning new things every day.</p><p>One thing I achieved is reading a book about architecture. I chose “<a href="https://learning.oreilly.com/library/view/-/9780137314942/">Modern Software Engineering: Doing What Works to Build Better Software Faster</a>” written by David Farley. I like this book because I am a TDD lover. This book gave me beneficial insight on a whole software engineering. I am writing a book review and am going to finalize it this week.</p><h4>English</h4><p>English is one of the essential keys to both my personal career and work because I am working for a global company the official language is English. Besides, I am not a native English speaker.</p><ul><li>30-minute online private English lesson every weekday -&gt; 18 days / 19 days</li><li>30-minute English grammar book (1 chapter) exercise -&gt; 4 days /19 days</li></ul><p>I tried DMM Eikaiwa to have 25 minutes personal lesson every workday and it worked well. I found having an English lesson every morning had a good effect to communicate with colleagues.</p><p>One issue is that I still sometimes have trouble with understanding fast-speed English talk. It usually happens in hiring interviews.</p><p>Also, I wrote a technical blog in my company blog, but I found that my English writing still needs to train more, especially in finding suitable phrases.</p><p>Regarding grammar books, I failed to make time to work on them because of two reasons. The first reason is my English teacher gave me homework and it worked as an alternative. The second reason is it takes roughly 30 minutes and it isn’t realistic to work in a day.</p><h4>Work</h4><p>I am working as a senior site reliability engineer at Autify. On January, I had two milestones.</p><ul><li>Publish one blog about Autify Connect’s technical aspect on the Autify company blog -&gt; One blog has been published!</li><li>One question or comment every meeting –&gt; 20 meetings /22 meetings</li></ul><p>I have two drafts of my blog, and one of them is in the final review. Finally, I’ve published a blog in my company blog, which has taken one year and more since I joined.</p><p><a href="https://blog.autify.com/srecon22apac">Joined SREcon22 Asia/Pacific to give a session about Autify&#39;s Design of a stateful system | Autify Blog</a></p><p>Meetings. Expect an all-hands meeting and another small spot meeting, but I succeeded in participating in them actively. This milestone also brought me a discovery that it could resolve the gap between Japanese-style conversation and English-style conversation. I feel I got used to English-style conversation more, in other words, a style not to wait for others saying and… hmm, difficult to describe…</p><h3>What I’ve tried to build a new work-life balance</h3><p>I tried the following trials on January 2023.</p><ul><li>Fixed working hours from 9 AM to 6 PM to prioritize family tasks</li><li>Don’t respond to business messages during personal time.</li><li>Use 1 hour from 8:00 AM to address family tasks and learning.</li><li>1 hour and 30 minutes break time</li><li>3 days per week: drinking</li></ul><p>It sounds quite natural and easy, but it was challenging for me. Previously, when I get up early morning, I start working and make a progress in a project that I am involved in. That’s why many colleagues said to me “when do you sleep? You look to work anytime even midnight.” Since I graduated from my university and started working as a full-time employee, I’ve continued this kind of working style.</p><p>Additionally, I’ve been working as a software engineer for a web service, and my expectation for myself is that I should always be online in case something critical happens. When I was a “junior-level” engineer, I studied the behavior of excellent infra engineers and tech leads. They had a great sense of responsibility to ensure their service reliability.</p><p>As a result of these trials, fixed working hour works very well for me! I usually get up at 7:40 AM and start the laundry, make a coffee and have breakfast. When I get up earlier, I read a book about childcare or software engineering. After 6 PM, I finish working and start cooking, doing house chores, or taking a bath.</p><p>I guess it will be tough after my first kid is born, but I succeeded in building a new rhythm.</p><h3>Plan for February 2033</h3><p>The structure of milestones is the same as the last month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k96EmRDQF-TL79fFIAaEzA@2x.jpeg" /></figure><p>I don’t expect myself to grow up rapidly. Just do what I can within my time. I tend to concentrate on working rather than family chores without any policy, so I set Family as the top priority. Software engineering is just a part of my Family’s happiness. That’s because I am impressed by someone’s advice that you should take into account your happiness as your family’s happiness. I expect this way of thinking to allow me to think of work and life seamlessly.</p><h3>Milestones</h3><h4>Family</h4><ul><li>1 book in my native language, 1 book in English</li><li>10 times or fewer house chores when only my wife does</li></ul><p>I found an English book is beneficial both for knowing better practices and being able to explain parenting in 1on1 meetings or etc.</p><p>I found it troublesome to count up every time, so I changed my mind to set another milestone. It is a demerit method to count up a negative point. What I need to avoid is being lazy and doing nothing while there are necessary tasks.</p><p>Additionally, I feel that I need to be more proactive to prepare the childbirth like researching goods to welcome a baby. However, I’ve not found a good indicator to measure that.</p><h4>Software Engineering</h4><ul><li>Publish two book review blogs that I’ve read last month.</li><li>Read one book about SRE.</li></ul><p>I found that it is not realistic to read a book and write a book review blog, so I compromised the milestone of reading new books related to architecture reviews and SRE.</p><h4>English</h4><ul><li>30-minute online private English lesson every weekday</li></ul><p>This is the same milestone as the last month because it worked well to have an English conversation lesson before business meetings.</p><h4>Work</h4><ul><li>Publish one blog in the Autify company blog</li><li>One question or comment every meeting</li></ul><p>These are the same milestone as the last month.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9be7aa5b0c5e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Plan and milestones for January 2023]]></title>
            <link>https://medium.com/@hgsgtk/plan-and-milestone-for-january-2023-2b134e930037?source=rss-aec8ceaac4a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b134e930037</guid>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Kazuki Higashiguchi]]></dc:creator>
            <pubDate>Mon, 02 Jan 2023 08:53:24 GMT</pubDate>
            <atom:updated>2023-01-02T11:02:11.894Z</atom:updated>
            <content:encoded><![CDATA[<p>I decided not to have any clear goals and milestones to prioritize family stuff, but I realized it led to the situation that relaxed me too much.</p><p><a href="https://medium.com/@hgsgtk/one-year-has-passed-since-joining-autify-a-retrospective-on-2022-ec25b96ab710">One year has passed since joining Autify – a retrospective on 2022</a></p><p>Hence, this blog will declare the goals and milestones. The target term is from January 4 to 31.</p><h3>Theme: get used to a new work style and mindset</h3><p>This month will be the first month since I changed my mindset, so I need to get used to this change. In other words, tasks and interests in software engineering have become a part of my goal.</p><p>The new mindset is shown in the subsequent diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k96EmRDQF-TL79fFIAaEzA@2x.jpeg" /></figure><p>The first prioritized perspective is Family, which consists of Childcare and Software engineering. Our first child will be born next year, and we bought some necessary goods (e.g., a Pushchair). To prepare for it, I need to learn childcare as advance as possible.</p><p>Regarding my job, nothing has been decided except for my belonging team. One thing I found in the last retrospective was that I focused on my work too much. It was effective last year because the project I was involved in was filled with technical uncertainty and difficulty. However, it will not be effective this year because the last year is tricky. I will need to be proactive in learning new unknown things.</p><p>In addition, my English communication skill is now a blocker because Autify’s engineering team communication style is migrating from a single person project style to multiple person project style which requires more frequent oral communication.</p><h3>Milestone</h3><p>The following tasks should be done in the subsequent month.</p><h4>Family</h4><ul><li>Read 2 books about childcare and publish a book review to learn childcare knowledge.</li><li>2 days to think up a menu and cook to reduce the burden on housework on my wife</li><li>List up necessary tasks until our first child is born to be on the same page with my wife perfectly</li></ul><h4>Software engineering</h4><ul><li>Publish a blog about “Chaos Engineering(O’Reilly)” / in progress</li><li>Publish one small blog related to technology used by current work. A good candidate is AWS service comparison (e.g., ECS, Lambda) to launch a simple server in terms of operational excellence.</li><li>Read one book about architecting. A good candidate is “Microservice architecture, second edition.”</li></ul><h4>English</h4><ul><li>30-minute online private English lesson every weekday to improve English oral communication efficiency</li><li>30-minute English speaking and pronunciation exercise every weekday to convey my thoughts more appropriately in English. ELSA speaking and Speak buddy are good apps to do it.</li><li>30-minute English grammar book (1 chapter) exercise to improve the percentage that I can use correct English grammar in daily conversation smoothly.</li></ul><h4>Work</h4><ul><li>Publish one blog about Autify Connect’s technical aspect on the Autify company blog to get used to write a blog on my company blog.</li><li>One question or comment every meeting (including all hands meetings) to be more proactive to other team members’ work.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b134e930037" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One year has passed since joining Autify – a retrospective on 2022]]></title>
            <link>https://medium.com/@hgsgtk/one-year-has-passed-since-joining-autify-a-retrospective-on-2022-ec25b96ab710?source=rss-aec8ceaac4a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec25b96ab710</guid>
            <dc:creator><![CDATA[Kazuki Higashiguchi]]></dc:creator>
            <pubDate>Fri, 16 Dec 2022 08:41:55 GMT</pubDate>
            <atom:updated>2022-12-16T09:29:25.033Z</atom:updated>
            <content:encoded><![CDATA[<p>In this post, I will recap what I have done in Autify in 2022 and retrospect on 2022, including my personal life.</p><p>This blog post includes only information published publicly (e.g., general help page, release note, press release, and tweets).</p><h3>Who are you?</h3><p>I am working at Autify, a start-up company founded in San Francisco. We serve an AI-based end-to-end no-code test automation platform for web and mobile applications.</p><p><a href="https://medium.com/@hgsgtk/im-joining-autify-a-no-code-ai-powered-software-testing-automation-platform-2a6285b38fb0">I’m joining Autify, a no-code AI-powered software testing automation platform</a></p><p>I joined here as a backend engineer, and as the organization grew, the name of my role changed to “Sr. Backend Engineer,” and then I changed my title to “Sr. Site Reliability Engineer” as the result of the discussion with my managers, considering the actual work I’d addressed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PV7-8hjsAKh_Vg9bFikJcA@2x.jpeg" /></figure><p>Other personal profiles include being married and living in Japan.</p><h3>The project I was involved in Autify</h3><p>In Autify, I have been involved in one project for entirely one year. We’ve worked hard in this project and released the new feature called Autify Connect.</p><p><a href="https://autify.com/news/autify-connect-release">Autify Connect is released</a></p><blockquote>Using Autify Connect, you can run automated tests on applications located within an organization’s network, such as localhosts, internal systems, and staging environments that are not publicly accessible.</blockquote><p>Technically I’ve designed all layers from frontend to cloud infrastructure, and have been responsible for all software development lifecycle from planning to operating running systems in production.</p><p>This project was relatively unique in Autify because we started this project from the engineering aspect, not from the product requirement. We had a kind of abstract ambition last year. Before releasing this feature, customers couldn’t use Autify because they had to prepare their target application accessible from the public internet. It was a blocker to use Autofy in the following use cases.</p><ul><li>Before deploying code changes, run tests against their localhost application</li><li>Run tests against applications under a restricted network condition</li></ul><p>To eliminate these limitations, I started technical investigations, discussed the necessary scope, and implemented several proof of concepts. This project had high uncertainty of technical feasibility, which means there are bunch of technical tradeoffs that could affect the customer visible user experience.</p><p>This project consisted of three timespans, PoC phase, MVP phase, and evolution after MVP.</p><h3>Knowledge to spend PoC trials effectivelty</h3><p>The PoC phase was challenging, but I enjoyed this period because the outcome gained in this term would decide whether our product could provide an excellent user experience. Fantastic user experience with this feature depended on my technical ability. I investigated a bunch of open-source projects and case studies of commerce products. In this period, I’d learned deep knowledge of the following technologies:</p><ul><li>Layer-7 tunneling designs; Long polling vs WebSocket</li><li>WebSocket specification; RFC6455 (I memorized this number through this project)</li><li>TCP and socket programming</li><li>Proxy (transparent proxy, MITM proxy, etc)</li><li>Network requests emitted by modern browsers</li></ul><p>I set the demonstrable milestones every sprint. Every sprint, I made many trials and errors. I sometimes had a nightmare where I failed to find a solution to the current problem. There, I learned some lessons to succeed in a PoC phase.</p><ul><li>Get the consensus that we delete all codes written in the PoC phase after completing it and we will not use it in production. It helps us to try new ideas speedily and to avoid unnecessary discussions about the quality to maintain it for the long term, in other words, maintainability.</li><li>Plan this period to demonstrate the outcome with the stakeholder each sprint. The PoC phase tends to become a black box for stakeholders, but it’s not a good idea. Clear demonstrable goals make our work transparent.</li><li>Prioritize additional issues by verifying the current goal. During investigating new ideas, you may find different concerns that you need to address. You may want to start this additional investigation, but it will be an endless journey. Even when you come up with any concerns, I recommend you thinking first whether they are a blocker to completing your sprint goal.</li></ul><h3>Minimal viable product</h3><p>After completing the PoC phase, I listed necessary user stories again, and started tracking the velocity. These are basic techniques of agile methodologies. As the result of my technical investigation, our approach was to use WebSocket as a secure bidirectional tunnel connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VNH9_WUOo1ZLpNoJLM0PBA@2x.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fspeakerdeck.com%2Fplayer%2F6b97d32c277d4625b646379eab8eeabc&amp;display_name=Speaker+Deck&amp;url=https%3A%2F%2Fspeakerdeck.com%2Fhgsgtk%2Fsrecon2022apac-design-of-stateful-system&amp;image=https%3A%2F%2Ffiles.speakerdeck.com%2Fpresentations%2F6b97d32c277d4625b646379eab8eeabc%2Fslide_0.jpg%3F23714139&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=speakerdeck" width="710" height="399" frameborder="0" scrolling="no"><a href="https://medium.com/media/4bea038c712c1b1386a916e62424ebb9/href">https://medium.com/media/4bea038c712c1b1386a916e62424ebb9/href</a></iframe><ul><li>Robust concurrent programming in Go.</li><li>Each browser specification and limitation, especially local loopback address and proxy configuration.</li><li>Streaming TCP connection over WebSocket</li><li>Effective tips to make stateful black box system observable and easy to investigate</li></ul><p>Several months right before releasing this feature were tough for me. Proxying browser requests was more difficult than other proxies like a simple API proxy because a browser sends multiple requests simultaneously, including several protocols such as HTTP, HTTPS, WebSocket etc. I found many edge cases and solved them one by one. I occasionally had a nightmare where I found a new unknown error, and woke up, although 90% of them were not real.</p><p>This period was precious time for me as a software engineer. I’ve gotten several lessons from this experience.</p><ul><li>Prioritize security issues. If customers have security concerns to start with your product, you should prioritize security considerations. It doesn’t mean that you must implement all possible security improvements because there are an unlimited number of tasks ultimately. It means that you should prepare the answers to all possible questions. Depending on each question, it may be enough to prepare a manual operation workflow.</li><li>Have unit tests as much as possible. I am a big Test-driven development lover, so I always write unit tests first. I wouldn’t say I like to test my code by my hand, and instead, I run my code with automated test codes. This behavior worked well for such a technically complex program.</li><li>Design operational excellence before releasing the feature, including customer success. Engineering work is not limited with designing software, writing codes, and building infrastructure. It is the minimal expectation for engineers who work for software service companies. Releasing a product is just a starting point. It would help if you designed how to handle customer inquiries, how to investigate failures in production, and procedures when a server is down BEFORE making a new feature visible to end-users. They include writing runbooks, implementing logging, instrumenting traces, publishing help pages, and creating infrastructure metrics monitoring.</li><li>Limiting features as minimal makes sense. As long as users can achieve a simple customer journey, we can start serving the feature in production. Beta releasing would help you to go with the limited MVP.</li></ul><h3>Scalable and reliable stateful system</h3><p>After releasing the MVP, my primary individual work is to implement service reliability and facilitate team engineers to implement missing features. I focused on service reliability stuff, so my current role is Sr. Site Reliability Engineer, including the low-layer knowledge gained in the previous period.</p><p>Recently, we have fewer chances to manage such a stateful system, which requires us to have a kind of traditional infrastructure operation knowledge. So it gave me more proof of firm infrastructure knowledge because it needed me to address challenges without fully-managed services provided by cloud vendors.</p><p>Besides, I facilitated missing feature implementations as a kind of mini-product/project manager. As what one individual workforce can do is limited, I believe that it is an essential skill to collaborate with other people. I used to be a tech lead and engineering manager at my previous workplace, and these experiences helped me to ask others to implement my idea behalf of me.</p><h3>Service operation</h3><p>In addition to the assigned project, I have proactively addressed service operation issues. From my perspective, working only for assigned projects is not enough for engineers who work for internet services. It is common sense that engineers, who develop a product, are involved in operating services. Therefore, I’ve jumped into alerts, incidents, application errors, customer inquiries and etc. The following presentation material explained my approach to catching up on service operations.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fspeakerdeck.com%2Fplayer%2Fbff5a5a4030a4f4a8ab74613bdaf9110&amp;display_name=Speaker+Deck&amp;url=https%3A%2F%2Fspeakerdeck.com%2Fhgsgtk%2Fa-guide-to-joining-operational-work-in-your-new-devops-team&amp;image=https%3A%2F%2Ffiles.speakerdeck.com%2Fpresentations%2Fbff5a5a4030a4f4a8ab74613bdaf9110%2Fslide_0.jpg%3F21598134&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=speakerdeck" width="710" height="399" frameborder="0" scrolling="no"><a href="https://medium.com/media/e60329970a867f7b8ba96d64665ca48e/href">https://medium.com/media/e60329970a867f7b8ba96d64665ca48e/href</a></iframe><h3>Technical PR</h3><p>I value technical PR activities such as presenting at tech conferences, writing blogs, and speaking at podcasts. These opportunities give me time to retrospect my work and to organize my thinking by reading books and articles.</p><p>Good points 👍</p><ul><li>I gave 5 presentations this year, including an in-person global conference, SREcon22 at Sydney.</li></ul><p><a href="https://www.usenix.org/conference/srecon22apac/presentation/higashiguchi">A Better Way to Manage Stateful Systems: Design for Observability and Robust Deployment</a></p><p>Bad point 😞</p><ul><li>I didn’t contribute any blog on the company blog</li></ul><h3>English communcation</h3><p>I am not a native English speaker; instead am not good at speaking/listening/writing/reading in English, so I’ve been training my English skill for the whole of this year.</p><p>Autify provides skill-up allowance and incentives to improve each English skill. Thanks to them, my English skill has been improved.</p><p>We use CERF as a measurement of English skills, and my English level at the beginning of this year was B1 medium according to the first test. I had a test last month and the test showed my English skill B2, which is a happy news.</p><p>Still, I am struggling with English. I can’t understand what native English speakers say 100%. I am often stuck in subsequent words when I speak English. My pronunciation is still wrong. Many employees in Autify are based in Japan or are familiar with Japanese culture. That’s why they can understand what I say even though my English is broken.</p><p>Furthermore, advanced English skill is required to act as a leadership role. Just to behave as an individual worker whose influence is very small, it may not be necessary to have a sophiscated English skill. It’s not what I wish.</p><h3>2023 is coming soon</h3><p>Next year, the slogan that come to mind is “take it easy.”</p><p>I’ve worked very hard until now since jumping into the IT field. Thanks to decades of effort, my career goal, which I had when I graduated from the university, was achieved to some extent. Besides, one of the most significant changes are coming soon. I want to make more time for family.</p><p>Therefore, the expectation of evolution as a software engineer is nothing. Let’s go with the flow. Prioritize child care first and get used to a new life. Take it easy. I will not be depressed even if I feel no progress in my career.</p><p>Based on this prerequisite, I will focus on learning two fields;</p><ul><li>Effective design and architecture review</li><li>Act as an embedded SRE</li></ul><p>Considering my subsequent career, the time to work on specific implementations will be less than now because my mindset is not a specialist one. Even when I need to act as a specialist, there are more chances to advise other engineers about software design and architecture. Doing that, more knowledge is required. I will read more books to get ideas about the pros and cons of each option and case studies to solve actual problems, including practical communication skills.</p><p>I feel many engineers are not good at expressing and organizing their thought about technical tradeoff issues, probably including me. The lack of this skill can be a blocker to staff+ engineers.</p><p>Secondly, my role is a senior site reliability engineer, and I’ll work in the team developing new features, not in the central SRE team. I’m in a unique position now, so I will try to find out how to contribute to our product effectively.</p><p>There are few developers who are good at thinking of service operational excellence, in addition to implementing business logic. I believe my unique position allows me to do balancing both aspects.</p><h4>Wish in 2032~</h4><p>I’ll switch from sprint-style working to marathon-style working. Therefore, the next milestone is 10 years-basis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Dpjwv7EB2oy_haD5w5d9Q@2x.jpeg" /></figure><p>I wish all members in my family would spend happy time.</p><p>I wish Kaz 2032 would give a more extended presentation about the more profound and broader software engineering knowledge, with more fluent English, at a global conference.</p><p>I wish Kaz 2032 has an organized broader knowledge to write a commercial book.</p><p>Take it easy, and have a good rest in 2022.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec25b96ab710" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Focus on solving burning needs to spend happy engineering time]]></title>
            <link>https://medium.com/@hgsgtk/focus-on-solving-burning-needs-to-spend-happy-engineering-time-5caa49df4f0a?source=rss-aec8ceaac4a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5caa49df4f0a</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[autify]]></category>
            <dc:creator><![CDATA[Kazuki Higashiguchi]]></dc:creator>
            <pubDate>Tue, 15 Feb 2022 03:47:28 GMT</pubDate>
            <atom:updated>2022-02-15T03:47:28.091Z</atom:updated>
            <content:encoded><![CDATA[<p>I joined Autify on January 1, 2022, and passed 1.5 months today.</p><p><a href="https://medium.com/@hgsgtk/im-joining-autify-a-no-code-ai-powered-software-testing-automation-platform-2a6285b38fb0">I’m joining Autify, a no-code AI-powered software testing automation platform</a></p><p>Since joining here, I have found that Autify’s company values are universally useful in engineering work.</p><p>This post will talk about Autify company values and share my thoughts on embodying essential values to perform well, especially in terms of software engineering.</p><h3>Autify company values</h3><p>Autify has three company values: “Solve burning needs,” “Aim high, stay grounded,” and “Be selfless.”</p><p>In my opinion, the <em>most</em> important one is “Solve burning needs.” Perhaps some of you have not heard of the concept of burning needs, so let me explain it briefly.</p><p>A burning need is analogous to the urgent need to of extinguishing the flames if your hair is on fire as you can see in this picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dabBD1zIAe2DOs82" /><figcaption><a href="http://viewfrombehindhomeplate.blogspot.com/2014/01/putting-out-fire.html">http://viewfrombehindhomeplate.blogspot.com/2014/01/putting-out-fire.html</a></figcaption></figure><p>In general, companies will only spend money to solve pressing issues such as this, so SaaS startups need to focus on solving burning needs.</p><p><a href="https://medium.com/@chikathreesix/solving-customers-burning-needs-3705cd8b1f72">Solving customer’s burning needs</a></p><p>The value “Solve burning needs” can be broken down into three elements: “Problem-first,” “Dig deeper,” and “The shortest path.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*X_i_yjaXuzzsyhM07RbOkg.png" /><figcaption><a href="https://speakerdeck.com/autifyhq/autify-company-deck-efd29263-1045-43c2-b2a0-17328638b0fe?slide=22">https://speakerdeck.com/autifyhq/autify-company-deck-efd29263-1045-43c2-b2a0-17328638b0fe?slide=22</a></figcaption></figure><h3>Problem-first</h3><p>Significantly, the “Problem-first” mindset is crucial for software engineers to perform well.</p><p>In general, engineers tend to get caught up in detailed solutions such as better <em>architecture</em>, fabulous <em>design</em>, popular <em>programming</em> languages, etc. There is no end to developing better solutions if we don’t have an apparent problem.</p><p>For example, let’s say you will build a CI/CD pipeline for a new service. It would be best if you answered: “What is the problem? …What is the burning need?” You will find out <em>whose</em> burning need you want to solve with your task by answering <em>these</em> questions.</p><p>If they are <em>non</em>-engineers, the solution would be something like a chat-ops that doesn’t require deep technical knowledge. If they are <em>familiar</em> with infrastructure, it may be enough to use a cloud console provider service <em>directly</em>.</p><p><strong>The “Problem-first” mindset helps us set a goal and find the <em>shortest</em> path to solve someone’s burning need.</strong></p><h3>Conclusion</h3><p>Autify company values are universally crucial and beneficial not <em>only</em> for Autify members but also for <em>all</em> business people.</p><p>I hope you will check the values out in our company deck.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fspeakerdeck.com%2Fplayer%2F8d1df30d6ad544829f65b7c5216a7a71&amp;display_name=Speaker+Deck&amp;url=https%3A%2F%2Fspeakerdeck.com%2Fautifyhq%2Fautify-company-deck-efd29263-1045-43c2-b2a0-17328638b0fe&amp;image=https%3A%2F%2Ffiles.speakerdeck.com%2Fpresentations%2F8d1df30d6ad544829f65b7c5216a7a71%2Fslide_0.jpg%3F18031341&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=speakerdeck" width="710" height="399" frameborder="0" scrolling="no"><a href="https://medium.com/media/b972e8a424b5cdf512a1212f8a398e9e/href">https://medium.com/media/b972e8a424b5cdf512a1212f8a398e9e/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5caa49df4f0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get results effectively in your engineering side job with Agile practices]]></title>
            <link>https://medium.com/@hgsgtk/how-to-get-results-effectively-in-your-engineering-side-job-with-agile-practices-cc2d5d45a1fc?source=rss-aec8ceaac4a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc2d5d45a1fc</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Kazuki Higashiguchi]]></dc:creator>
            <pubDate>Tue, 11 Jan 2022 09:26:45 GMT</pubDate>
            <atom:updated>2022-01-11T09:29:28.871Z</atom:updated>
            <content:encoded><![CDATA[<h3>Key takeaways</h3><ul><li>Agile philosophy and practices helped a lot in my side job, even if it’s a one-person project.</li><li>Alexander Laufer’s categorization, which is means uncertainty and end uncertainty, helps to design your way of working.</li><li>Shorten the iteration to get feedback for your work frequently by dividing your task into detailed user stories.</li><li>If your task has high technical uncertainty, it is also a good way to add an additional phase where focuses on investigating technical issues.</li><li>If you wish to work with more discretion and initiative, do self-management.</li></ul><h3>A difficulty to get results in an engineering side job</h3><p>Previously, I published the blog sharing that I’m joining Autify, which serves as a no-code AI-powered software testing automation platform, on January 1, 2022.</p><p><a href="https://medium.com/@hgsgtk/im-joining-autify-a-no-code-ai-powered-software-testing-automation-platform-2a6285b38fb0">I’m joining Autify, a no-code AI-powered software testing automation platform</a></p><p>In fact, I had worked at the company as my second job for a few months about 40 hours per month. Then, I joined this company this year as a full-time employee.</p><p>Based on this experience and my former experience as an engineering manager supporting new employees into my team, I would like to share my thoughts on how to get results in a short time as a side job engineer.</p><p>If you work as your second job, you probably don’t have much time available because you have your primary job during the daytime. In my case, the longest month was 40 hours, and the shortest month was only one month. That’s why you need to produce steady results in a short time. To work well, <strong>agile philosophy and practices helped a lot in my side job, even if it’s a one-person project.</strong></p><p>In this post, I will introduce four techniques to get results in a short time as a contractor.</p><ol><li>Shorten the iteration to get feedback frequently</li><li>Self-management</li><li>Prepare in advance for the first kickoff</li><li>Transparency at your work</li></ol><h3>1. Shorten the iteration to get feedback frequently</h3><p>Needless to say, you don’t have much time to work the side job compared with the primary job. <strong>I suggest you</strong> <strong>develop your work in a short period of time in order to get feedback on your work frequently</strong>. This idea is based on the principles behind the agile manifesto proposed by Agile Alliance.</p><p><a href="https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/">12 Principles Behind the Agile Manifesto | Agile Alliance</a></p><blockquote>3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.</blockquote><p>Alexander Laufer groups uncertainties into two categories in his book <a href="https://www.amazon.com/Simultaneous-Management-Managing-Projects-Environment/dp/0814403123"><em>Simultaneous Management</em></a><em>: </em><strong><em>means uncertainty</em></strong><em> and </em><strong><em>end uncertainty</em></strong><em>. Means uncertainty refers to uncertainty about exactly how we will design and. develop a product; end certainty refers to uncertainty about exactly what a product will do.</em></p><p>As a person who joins as a side job, you will probably be assigned to tasks that are expected to have less uncertainty, especially end uncertainty. Still, <strong>if you show the finished work without showing the progress along the way, you may end up creating something that is misguided!.</strong></p><p>There is less first-hand information available to you compared to a full-time employee. For example, your working hours would be irregular, such as early mornings and evenings, that’s why it tends to be difficult to get frequent syncs on the daily or attend the team meeting. In addition, your scope of access to the code repository may be limited to the minimum necessary, or the range of the slack channel may also be limited.</p><p>You may make mistakes that you would not make in your primary job if you don’t actively acquire information.</p><p><strong>To reduce means uncertainty, you need to get feedback for your approach to solve your task.</strong> In the case of service feature development, it is important to take into account how they work for service reliability in the production system, how they support their customers, the system of manning, the future outlook of the engineering team, and etc. One of means uncertainty is that it is a little bit difficult to obtain first-hand information about these production issues. You should get feedback about that in order not to end up with a low-quality design.</p><p><strong>Also, to reduce end uncertainty, Your understanding of its requirement should be checked by showing the progress along the way.</strong> The situation is ever-changing, and something more important than the first requirement you were told might appear. Since you may end up making decisions that do not align with the product vision, you should get feedback from one who has a deep understanding of it frequently.</p><p>There are two specific techniques: <strong>to</strong> <strong>divide into detailed user stories</strong> and <strong>to add an additional phase</strong> where the technical investigation is the main focus.</p><h4><strong>Divide into detailed user stories</strong></h4><p>If you are working on a relatively large project, break up your user stories into smaller pieces and demo them at a sustainable pace. Needless to say, if you are familiar with user story practices, <strong>it is important to keep them “vertical slice”</strong>. The term “vertical slice” refers to a cross-sectional slice through the layers that form the structure of the software codebase <strong>with emphasis on demonstrating progress across all components of a project.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mAuplEaCQ4VA7Mkv.png" /><figcaption>Quoted by <a href="https://en.wikipedia.org/wiki/Vertical_slice">https://en.wikipedia.org/wiki/Vertical_slice</a></figcaption></figure><p>It is also a good idea to have regular demonstration meetings such as the sprint review in Scrum.</p><p><a href="https://www.scrum.org/resources/what-is-a-sprint-review">What is a Sprint Review?</a></p><h4><strong>Add an additional phase where the technical investigation is the main focus</strong></h4><p>If it is a relatively long-term project that may take more than 3 months and there are several uncertainties due to technical difficulties, it may not be efficient to continue to produce user stories at the production level (i.e. writing automated tests and doing other manual tests), in each iteration. In that case, it can be a prescription that you add the phase such as PoC (Proof of Concept), prototype and etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rDWvqn_vI57qvpy7guQ4Dg.png" /><figcaption>Divide one phase into two phases: the PoC phase and the developing for release phase</figcaption></figure><p>I don’t care about the difference between the term “PoC” and “prototype”, but <strong>the important point is that each Definition of Done is different</strong>. The term “Definition of Done” is well known in agile development. It offers a compelling image of well-defined slices of a product and provides a checklist that defines the minimum work generally required to get a product increment to the “done” state.</p><p><a href="https://www.agilealliance.org/glossary/definition-of-done/#q=~(infinite~false~filters~(postType~(~&#39;page~&#39;post~&#39;aa_book~&#39;aa_event_session~&#39;aa_experience_report~&#39;aa_glossary~&#39;aa_research_paper~&#39;aa_video))~searchTerm~&#39;~sort~false~sortDirection~&#39;asc~page~1)">Definition of Done</a></p><p>In order to create deliverable <a href="https://www.scrum.org/resources/what-is-an-increment#:~:text=As%20described%20in%20the%20Scrum,the%20Increment%20must%20be%20usable.">increments</a> that are ready to release to customers, you will need the following checklist (it depends on your team).</p><pre>// Definition of Done (for the development for release phase)<br>- [ ] Can demonstrate the function or code?<br>- [ ] Got at least one approved in the code review from team members? <br>- [ ] Wrote automated tests to check whether your code is working? <br>- [ ] Story acceptance tests is passed? <br>- [ ] Updated the design document (if necessary)?</pre><p>This checklist can be an obstacle when conduction technical investigation under high means uncertainty. It is difficult to create test scenarios with a high level of technical uncertainty, and even if you write automated tests, there is a possibility that they will be discarded soon, which is expensive (If you are a TDD practitioner even when you are implementing a PoC or prototyping, this may not be the case). In my case, the definition of done in the PoC phase is as follow:</p><pre>// Definition of Done (for the PoC phase)<br>- [ ] Can demonstrate the function or code?<br>- [ ] Updated the design document (if necessary)?</pre><p>The demonstration is important for discussion and getting feedback for the product specifications, so it can NOT be left out here. However, I decided NOT to test with the production release in mind, assuming that I will rewrite it after the end of the PoC phase.</p><p><strong>In a sense, this can be rephrased as making time to work on </strong><a href="https://www.agile-academy.com/en/agile-dictionary/spike/"><strong>spikes</strong></a><strong> for a long time.</strong> Spike is the name for a timeboxed user story or task that is created in order to research a question or resolve a problem. It focuses on gathering information and finding answers to questions, rather than producing a shippable product.</p><p>As a reminder, it is important to agree that the artifacts demonstrated in the PoC phase cannot be used in the production environment as-is. Rebuild it in a way that meets the definition of done for the next phase.</p><p>Also, if you can just put spike issues in the normal way, that is better because it’s the simplest way for you.</p><h3>2. Self-management</h3><p>When you are welcomed in a new team, your manager has the first, second week to think of “what kind of management should give you?” and figure out which category’s issue give you.</p><figure><img alt="2x2 diagram (end uncertainty, means uncertainty)" src="https://cdn-images-1.medium.com/max/1024/1*_mlLWbDdmE9U3AG9E5JAiw.png" /><figcaption>2x2 diagram (end uncertainty, means uncertainty)</figcaption></figure><ol><li>Should give you a clear problem and solution (low end uncertainty, low means uncertainty)?</li><li>Should give you only a clear problem and let you think of a solution (low end uncertainty, high means uncertainty)?</li><li>Should tell you product concerns, and ask you to clarify a problem to be addressed and think of a solution (high end uncertainty, high means uncertainty)?</li><li>Should give you a clear solution and ask you think what is our problem (high end uncertainty, low means uncertainty)?</li></ol><p>If you wish to work with more discretion and initiative, you should show the kind of stability that allows you to tackle issues with higher uncertainty.</p><p><strong>Self-manage so that you need almost no support in your work</strong>. <a href="https://www.indeed.com/career-advice/career-development/self-management-skills">Self-management</a> skills are the abilities that allow people to control their thoughts, feelings, and actions, for example, in the following areas:</p><ul><li><strong>Organization</strong>: plan, prioritize and execute important activities</li><li><strong>Goal setting</strong>: determine what you want to achieve in a clear and well-defined manner</li><li><strong>Time management</strong></li><li><strong>Self-motivation</strong>: take initiative and finish tasks</li><li><strong>Stress management</strong>: handling stress</li><li><strong>Accountability</strong>: take personal ownership of your thoughts and actions</li></ul><p>Be proactive about these. In my case, <strong>I try to get people to review the decisions I’ve made, rather than having them decide.</strong> If you are a person who does not bring your own opinions to that table and let others decide for you, they may think that you need to manage your work in more detail there.</p><p>In fact, since a contractor position makes it difficult to take responsibility to some degree, the final decision needs to be made by a person such as a project owner, etc. However, as long as you are involved in the product development, you should have an opinion. You can say “There are several choices, and I think choice A is good for you because…, What do you think?”.</p><h3>3. Prepare in advance for the first kickoff</h3><p>As I mentioned the above, in the first or two weeks, your manager will determine the appropriate level of involvement for you. You’ll be given the overview and details about your job at the first kickoff meeting, but try to prepare in advance as much as possible. In particular, tasks entrusted to contractors will often not be specific to their product domain deeply, but rather issues in more generic technical area. The better. your understanding of the task on the first day, the more likely you are to get tasks of higher difficulty afterwards.</p><h3>4. Transparency at your work</h3><p>Make sure that other members can see what you are doing and thinking, because you’re not working synchronously. If your workplace uses Slack, it’s a good way to create a #times-xxx channel to open your working. Also, the skill of documentation is very important for remote-work as GitLab mentions at <a href="https://about.gitlab.com/company/culture/all-remote/guide/">the guide about their remote work culture</a>.</p><p><a href="https://about.gitlab.com/company/culture/all-remote/guide/">GitLab&#39;s Guide to All-Remote</a></p><blockquote>The Remote Manifesto:</blockquote><blockquote>3. Writing down and recording knowledge (over verbal explanations).<br>5. Public sharing of information (over need-to-know access).<br>6. Opening up documents for editing by anyone (over top-down control of documents).<br>7. Asynchronous communication (over synchronous communication).</blockquote><p>As a manager, they are concerned about whether your work is not dependent on individuals. You work will be asynchronous and remotely, so write enough amount of documentation and publish as much information as possible!</p><h3>Conclusion</h3><p>I explained four techniques to get results in a short time as a contractor.</p><ol><li>Shorten the iteration to get feedback frequently</li><li>Self-management</li><li>Prepare in advance for the first kickoff</li><li>Transparency at your work</li></ol><p>I wish you all the best in your work!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc2d5d45a1fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The concept map that gives a bird’ eye view of Autify for Web (2021 version)]]></title>
            <link>https://medium.com/@hgsgtk/the-concept-map-that-gives-a-bird-eye-view-of-autify-for-web-2021-version-948d3e77c409?source=rss-aec8ceaac4a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/948d3e77c409</guid>
            <dc:creator><![CDATA[Kazuki Higashiguchi]]></dc:creator>
            <pubDate>Fri, 24 Dec 2021 22:29:39 GMT</pubDate>
            <atom:updated>2021-12-29T00:23:09.988Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I’d like to introduce a “concept map” (2021 version) that gives a bird’ eye view of the features of <a href="https://autify.com/">Autify for Web</a>.</p><p>To create the diagram, I analyzed the features and the URL structure from the outside while touching the service.</p><p>Autify’s services are constantly evolving, and some features are accessible and others are not, depending on the pricing plan. Therefore, please note that the results of this analysis are for Autify for Web as of December 24, 2021, and are not a complete list of all concepts.</p><h3>Overview</h3><p>I have put together a diagram of the relationship between the concepts that you see in Autify for Web.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9hyEkOnjcM1eN2l1.jpg" /><figcaption>The concept map of Autify for Web</figcaption></figure><p>First of all, there is the concept of Organization, which describes a company or group.</p><p>From the Organization&#39;s point of view, you can add a “Member” by sending invitations. From the point of view of the invited party, the concept of User would be recognized.</p><p>You create tests in a “Workspace”. You can have more than one “Workspace” depending on <a href="https://autify.com/pricing">your pricing plan</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0qtr0otRcn7GfArK.png" /><figcaption>Number of workspaces per each plan</figcaption></figure><p>In Workspace, there are four main concepts that appear in the menu on the sidebar of the home screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uIpaq_AG2KOuHbiu.png" /><figcaption>A screenshot of the home screen of Autify for Web</figcaption></figure><p>A Test plan is created when you want to run a test on a regular basis or triggered by a deployment. A Test plan is a collection of Scenarios.</p><p>A Scenario is made up of several Steps. A Step group is a group of Steps that can be used many times in different Scenarios.</p><p>After executing the Test plan or Scenario, the Result will be created.</p><p>That’s it for the overview. Now let’s look at each concept in more detail.</p><h3>Organization / Member</h3><p>Organization and Member can be further detailed to look like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G7olxejq91ILPv1a.png" /><figcaption>A diagram describing resources and actions of organization and member</figcaption></figure><p>Each Organization has its own contract renewal date and number of test runs per month, and requests for additional test runs per month are also made in this conceptual unit.</p><p>Members can issue multiple Personal Access Tokens from their user settings and can revoke the issued one.</p><h3>Workspace</h3><p>In the “Workspace” unit, several concepts related to test creation, execution, and notification can be configured.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OIe1VYQyJq2J1ewc.png" /><figcaption>A diagram describing resources of workspace</figcaption></figure><p>Webhook allows you to set an endpoint to be notified when the test is completed. Webhook specifications can be found at <a href="https://autify.zendesk.com/hc/en-us/articles/900001791006-Creating-Webhooks">Autify for Web Help Center &gt;&gt; Create Webhook</a>.</p><p>Set up the notification for the Slack channel you want to receive the test completion notification in “Slack notification”.</p><p>Set “Basic auth credentials” to “Workspace” if you have set Basic authentication for the system under the test.</p><p>Custom hostname is available for Advance and later in <a href="https://autify.com/pricing">the current pricing plan</a>.</p><p>Autify provides an email testing environment that can be used for transition testing and verification of email content, such as new member registration and transactional emails after purchase. In the “Permanent test email address” section, you can create multiple email addresses to be used for email testing. The email addresses created here will be used when creating and editing “Scenarios”.</p><h3>Test plan</h3><p>The “Test plan” is followed by the “Trigger” which indicates when to run the test, the “Execution environment” which indicates where to run the test, the “URL replacement” which is set to support multiple environments, and the “Scenario” which is the target of the test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ECk21AUHRuFID6ZC.jpg" /><figcaption>A diagram describing resources and actions of the test plan</figcaption></figure><p>The administration screen for editing the test plan looks like the following image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5O0tc-nnpHhF-NgP.png" /><figcaption>A screenshot of a test plan</figcaption></figure><p>When you execute a “Test plan”, a “Result” will be created. For example, if you execute a “Test plan” that combines two “Scenarios”, you can check the test results for each “Execution environment” as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0lCA80xkcDAxuAFD.png" /><figcaption>A screenshot of a test result</figcaption></figure><p>Then, when you go to the results for Edge / Windows Server, you will see a list of “Scenario” results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Uj_y9KDcFZlcq3pc.png" /><figcaption>A screenshot of a test result of each execution environment</figcaption></figure><p>From there, you can see the results for each “Step” by checking the details of the execution of the “Scenario” you want to check.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GNU2FQl1kqFCbe3e.png" /><figcaption>A screenshot of each step result in a test scenario</figcaption></figure><p>From the relationship between these concepts, we can see that the structure of the “Result” is as follows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-CmfrttOzHfO5z-F.jpg" /><figcaption>The inside concept map of the result of test plan</figcaption></figure><h3>Scenario</h3><p>Now, let’s move on to Scenario. This concept refers to each test that you create. This concept includes the Window size (e.g. 1280x1024, 375x812 (iPhoneX) Beta).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5sQnFUzq9LT87XaR.jpg" /><figcaption>A diagram describing resources and actions of scenario</figcaption></figure><p>You can create a new Scenario by Duplicating from a Scenario, copying an existing one. Duplicating as a step group will also create a “Step group”.</p><p>Scenario” manages a series of “Steps”, but you can add new ones between them by inserting them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9xjky6GtGsxtA9I_.png" /><figcaption>A screenshot of inserting steps into the scenario</figcaption></figure><p>By using “Data”, <a href="https://autify.zendesk.com/hc/en-us/articles/900000826706-I-want-to-test-different-string-patterns-in-one-scenario-">you can test various string patterns in a single “scenario”</a>. For example, you can create and upload the following CSV file to be used in the Scenario.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1a0b67f98da6ccf0b8c91351bddf07b8/href">https://medium.com/media/1a0b67f98da6ccf0b8c91351bddf07b8/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uDPV-VthecclnwGE.png" /><figcaption>A screenshot describing how to use data in editing the scenario</figcaption></figure><p>When you Run now on Chrome, the scenario will start running and the “Result” will be created at the same time. The structure of the “Result” is not that different from the one of “Test plan”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Q7bllWyZddvi5HRY.jpg" /><figcaption>The inside concept map of the result</figcaption></figure><h3>Step</h3><p>Next, let’s focus on the “steps” that make up a Scenario or Step group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FxG4CUqlTzMJIVah.jpg" /><figcaption>A diagram describing resources and actions of step</figcaption></figure><p>A “Step” has an Action, which indicates what to do in your tests (e.g., click, type, page transition, execute JavaScript code). When you create a “Step” that you want to check, set the expectation of “When this step fails”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZxG4jx-0mdkE5mkx.png" /><figcaption>A screenshot of step editing</figcaption></figure><p>In addition, if you expect some text to be displayed, you can set the Text to assign (expected value). Here we can refer to the various concepts we have mentioned so far.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sNlpjR3_-Y44HBEA.png" /><figcaption>A screenshot of step editing</figcaption></figure><ul><li>Given value is the value to be entered only for this “Step”.</li><li>For the Test email address, you can use the “Permanent test email address” that you created in the “Workspace”.</li><li>Selecting the Dummy email address will generate a random, non-deliverable email address for each execution.</li><li>You can use Data to refer to the data you have uploaded to Scenario.</li><li>Other step’s result is <a href="https://autify.zendesk.com/hc/en-us/articles/900002403603-What-is-JS-Step-">JS step</a>. For example, this can be used to generate a non-overlapping string each time it is executed.</li></ul><h3>Result</h3><p>Finally, let’s take a look at the “Result”, which was briefly mentioned in the “Test plan” and “Scenario” sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WsjRb_rTiKFE9Cjm.jpg" /><figcaption>A diagram describing resources and actions of result</figcaption></figure><p>Each “Scenario” has its own execution status: Waiting, Passed, Failed, and etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vO8LQzu5cg6aVfxV.png" /><figcaption>A screenshot of the result of capabilities</figcaption></figure><p>You can download images of all the Step screenshots from Scenario.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cnWodesDXAq095yT.png" /><figcaption>A screenshot pointing the way to download images</figcaption></figure><p>When Autify’s AI detects a suspicious change in the UI, it enters the Review needed state. In <a href="https://autify.com/">Autify</a>, the AI supports maintenance of test scenarios after they are created, and monitors and detects UI changes at the time of release. This process is called Save as Failed / Passed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P8N90v1Ys9oXwwap.png" /><figcaption>A screenshot describing result and base images</figcaption></figure><p>It monitors and detects if the UI has changed and compares it to the Base image (past) for final decision.</p><h3>Conclusion</h3><p>The Autify product is designed to make it easy for anyone to create tests, so it’s unlikely you’ll get lost. But if you feel like you are lost(i.e. “Where is this function?, “Where is this concept?”), please feel free to use the “concept map”, and get a bird’ eye view of Autify for Web.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=948d3e77c409" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m joining Autify, a no-code AI-powered software testing automation platform]]></title>
            <link>https://medium.com/@hgsgtk/im-joining-autify-a-no-code-ai-powered-software-testing-automation-platform-2a6285b38fb0?source=rss-aec8ceaac4a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a6285b38fb0</guid>
            <category><![CDATA[join]]></category>
            <category><![CDATA[autify]]></category>
            <dc:creator><![CDATA[Kazuki Higashiguchi]]></dc:creator>
            <pubDate>Fri, 24 Dec 2021 05:53:50 GMT</pubDate>
            <atom:updated>2021-12-24T07:38:32.144Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m excited to share that I’m joining <a href="https://autify.com/">Autify</a>, a no-code AI-powered software testing automation platform, on January 1, 2022 (The Japanese edition is available <a href="https://note.com/hgsgtk/n/n9967ebcdf3c9">here</a>).</p><h3>Key takeaways</h3><ul><li>Autify provides an AI-powered software testing automation platform, which enables anyone to build tests easily with a no-code.</li><li>The field of test automation is currently in a period of accelerated evolution.</li><li>If you are interested in Autify services, try sending a “demo request” from <a href="https://autify.com/">here</a>.</li></ul><h3>Autify</h3><p>The mission of Autify is to “<strong>Enhance people’s creativity by technology</strong>”. Autify provides an AI-powered software testing automation platform, which enables anyone to build tests easily with a no-code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*17XE1xDcCPhxOrLuzB6kkA.png" /><figcaption><a href="https://autify.com/">https://autify.com/</a></figcaption></figure><p>With Autify, anyone can easily automate E2E testing, run them on any major PC browsers as well as smartphone browsers, then AI maintains automated testing scenarios based on your source code changes.</p><p><a href="https://autify.com/">Autify, AI-powered software testing automation platform</a></p><p>They offer two services, “Autify for Web” for browser UI services and “Autify for Moble” for mobile applications. In order to improve productivity in the software development process, they have divided their long-term roadmap into three phases to expand Autify’s capabilities and product lineup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AfZRIMRNbk60ORtJyp0vLw.png" /><figcaption><a href="https://autify.com/about">https://autify.com/about</a></figcaption></figure><p>The company was founded in San Francisco, US, and graduated from <a href="https://www.alchemistaccelerator.com/">Alchemist Accelerator</a>, a top accelerator in San Francisco, US. After that, they released Autify as its current figure.</p><p>They announced that it had raised $10M in Series A funding.</p><p><a href="https://techcrunch.com/2021/10/05/autify-advances-no-code-ai-powered-software-testing-automation-platform-with-10m-series-a/">Autify advances no-code AI-powered software testing automation platform with $10M Series A</a></p><h3>Introduce me</h3><p>I’ve worked as a software engineer at <a href="https://binc.jp/en/">BASE</a> for over 4 years. The mission of BASE is “Payment to the People, Power to the People.”, and they provide an online shop opening service “<a href="https://thebase.in/">BASE</a>”, the shopping service “PayID”, a fundraising service “YELL BANK”, and online payment service “PAY.JP”. The online shop opening service “BASE” has been chosen by many shop owners in Japan, with 1.6 million shops opened (based on information available as of December 22, 2021).</p><p>I joined BASE as a software engineer for this service and later joined its subsidiary BASE BANK from the start of its engineering organization, where I was involved in the architecture of the system from scratch and the grow-up of the engineering team. Since I joined there in October 2017, I have been involved in the development of the following products that have been press released.</p><ul><li>Fundraising service “<a href="https://thebridge.jp/2018/12/yell-bank">YELL BANK</a>”</li><li>“<a href="https://www.watch.impress.co.jp/docs/news/1352773.html">BASE Card</a>” to enable immediate use of sales from an online store</li><li>Online identity verification “<a href="https://prtimes.jp/main/html/rd/p/000000035.000049534.html">eKYC</a>”</li><li>“<a href="https://binc.jp/press-room/news/press-release/pr_20200210https://binc.jp/press-room/news/press-release/pr_20200210">Quick transfer</a>” to shorten the transfer date of sales from 10 business days to the next business day at the earliest</li><li><a href="https://www.lifecard.co.jp/news/company/press/pdf/300702.pdf">Renewal of deferred payment</a></li><li><a href="https://note.com/urerunetshop/n/n7167f8000479">Sales data download feature</a> to download sales-related data in CSV format</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Ld_LB308TggJBj3IKPIxg.png" /><figcaption>The brief timeline</figcaption></figure><p>First, I joined the company as a <strong>backend engineer</strong> who uses mainly PHP. After that, I joined the engineering team of its subsidiary at the timing of the start-up, where I was involved in the release of the fundraising service “YELL BANK”. Since then, I have been mainly involved in the growth of the service and became a <strong>tech lead</strong>. As the engineering team expanded, I introduced and promoted the agile mindset and practices to become a team rather than a collection of individuals. Then I switched from tech lead to <strong>engineering manager</strong>, and while supporting developers, I also doubled as a <strong>quality assurance engineer</strong>.</p><p>In addition to engineer work, I was also an active contributor to technology conferences, corporate blogs, and commercial magazines.</p><ul><li>Technology conferences: 59 times for 847 minutes (materials are available on <a href="https://speakerdeck.com/hgsgtk">Speaker Deck</a></li><li>Corporate blogs: <a href="https://devblog.thebase.in/search?q=id%3Akhigashigashi">39 posts</a></li><li>Commercial magazines: 2 magazines (about <a href="https://note.com/hgsgtk/n/n57df144b2034">Docker</a>, <a href="https://www.amazon.co.jp/%E3%81%BF%E3%82%93%E3%81%AA%E3%81%AEPHP-%E7%8F%BE%E5%A0%B4%E3%81%A7%E5%BD%B9%E7%AB%8B%E3%81%A4%E6%9C%80%E6%96%B0%E3%83%8E%E3%82%A6%E3%83%8F%E3%82%A6-%E7%9F%B3%E7%94%B0-%E7%B5%A2%E4%B8%80-uzulla/dp/4297110555">PHP</a>)</li></ul><p>I enjoyed working at BASE, but I made the decision to change jobs at a time when the direction of my two challenges was becoming clearer to me.</p><ol><li>Develop software products for software companies</li><li>work in a global team</li></ol><h4>1. Develop software products for software companies</h4><p>There are different types of software engineers, depending on whether they are more focused on the product itself or software development methodology. If you’re a product manager, the ratio of these concerns is like 8:2, and if you’re more focused on doing software development better, it’s like 2:8. I used to have a complex about being the latter.</p><p>However, one day, <strong>I found this complex can be solved if I was involved in product development for folks who develop and manage software services.</strong> For instance, for those who are interested in methodologies to make more effective use of software testing, the job of solving customers’ problems through products in the area of automated testing is directly linked to their interest in growing the product business.</p><h4>2. Work in a global team</h4><p>Since I started working as a software engineer, I have been working with a Japanese team.</p><p>The reason why I decided to work in the information technology field in the first place was that I visited a Canadian IT company called <a href="https://www.d2l.com/">D2L</a> when I studied abroad there for a month. That’s why the idea of working as a software engineer in a global engineering team was always in the back of my mind.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FitbaRj30wNI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DitbaRj30wNI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FitbaRj30wNI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/27b9b99c76da16f6f93d4ad2eeb9572e/href">https://medium.com/media/27b9b99c76da16f6f93d4ad2eeb9572e/href</a></iframe><p>For these reasons, I have been speaking at international conferences, <a href="https://github.com/gophercon/2019-talks">GopherCon 2019 </a>in San Diego, USA, and <a href="https://cakefest.org/archive/tokyo-2019">CakeFest 2019</a> in Tokyo, Japan.</p><p>Due to the recent situation, it was difficult for me to attend international conferences out of Japan after 2020. On the other hand,<strong> I realized that the widespread use of remote work has opened up the possibility of joining a global engineering team while staying in Japan.</strong></p><h3>Why I decided to join Autify</h3><p>After reading the job descriptions of 39 companies, 9 companies were selected based on several criteria. Out of all of them, Autify was the most attractive company for my next challenge for the following reasons.</p><ol><li>Product in the field of software testing</li><li>The impact made by SaaS of software test automation</li><li>Not learning from a company, challenging with a company</li><li>It would satisfy my curiosity as a software engineer</li></ol><h4>1. Product in the field of software testing</h4><p>Since joining BASE, I have been living a software engineer’s life with a strong awareness of software testing among development engineers.</p><ul><li>The practice of TDD (Test-driven development)</li><li>Legacy code improvement practices such as characterization tests</li><li>Practices on good quality unit testing</li></ul><p>Later, at a time when my role as a software engineer was gradually changing to team building and people management, I moved to scope software testing in general, not just from a developer perspective.</p><ul><li>ATDD (Acceptance test-driven development), a practice in the second quadrant with a more business perspective in the four quadrants of agile testing</li><li>E2E test automation</li><li>Test planning, design, and execution as a QA engineer</li><li>Performance testing, which is an area of technical product criticism</li></ul><p>I don’t know if I want to spend the rest of my software engineer’s life in the software testing field. However since I happened to be on such a path, and it was a unique part as a software engineer. That’s why I thought that the field of software testing would be a good fit for me.</p><p>Another major factor was that in the One-on-One meeting with Mr. Chikawazawa, the CEO, he told me that “Autify’s vision is not only to make E2E test automation.</p><p>Autify started out as a translation service (I heard the company name was different at that time). As a result of reflecting on the experience and practicing the concept of “<strong>Solving the burning needs to customers</strong>” taught in Alchemist accelerator, they have arrived at the “Autify” service.</p><p><a href="https://medium.com/@chikathreesix/solving-customers-burning-needs-3705cd8b1f72">Solving customer’s burning needs</a></p><p>I think this history is one of the things that make Autify stand out uniquely among test automation services.</p><h4>2. The impact made by SaaS of software test automation</h4><p>In recent years, test automation services, have been gaining momentum.</p><p>There is often a saying that “technology is a means to an end”. I half agree, but half disagree. <strong>Technology is just a means, but it’s still a big deal.</strong></p><p>For example, some programming practices are based on the use of modern IDEs (Integrated Development Environment). The IDE has had a great influent on the way we think. In his book “<a href="https://www.amazon.co.jp/Philosophy-Software-Design-2nd-English-ebook/dp/B09B8LFKQL/ref=sr_1_1?keywords=a+philosophy+of+software+design&amp;qid=1640066905&amp;s=digital-text&amp;sprefix=a+phi%2Cdigital-text%2C166&amp;sr=1-1">A Philosophy of Software Design</a>”, John Ousterhout recommends not including type information in variable names, partly because modern IDES make it easy to access type information for variables.</p><blockquote><em>“With modern IDEs it is easy to click from a variable name to its declaration (or, the IDE may even display the type information automatically), so there is no need to include this information in the variable name.”</em></blockquote><blockquote>Ousterhout, John. A Philosophy of Software Design, 2nd Edition (p. 127). Yaknyam Press. Kindle Edition.</blockquote><p>And more, in <a href="https://www.youtube.com/watch?v=4j0lekX4yzY">an interview with Bob Martin, author of Clean Agile</a>, he said that he never thought iteration would be so much faster than it was about 20 years ago.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fn5VpIr0MnuU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dn5VpIr0MnuU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fn5VpIr0MnuU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/03581ff91ee3624350595b689f82992a/href">https://medium.com/media/03581ff91ee3624350595b689f82992a/href</a></iframe><p>The cost of reducing the commit size is lower with <strong>git</strong> than with subversion, and the machine power that was lacking in the heyday of Agile around 2000 is now being used to speed up the iteration process. This is the reason for the current speed of iteration. The tools and services that we use today as a matter of course have become key parts that shape our development style and thinking.</p><p>Or, the practice of CI/CD (Continuous Integration / Continuous Delivery or Deployment) is very smooth nowadays, and I think a very big reason behind this is that CircleCI, GitHub, etc. provide high-level solutions as SaaS.</p><p>In other words, <strong>tools are a means, but folks’ thinking is constrained by tools</strong>. And the idea of test automation is being optimized in various ways within the limitations of current technology. For example, the model “Test automation pyramid” is widely spread in the engineering community (there are also several criticisms and rethinking such as DevOps Bugfiler).</p><figure><img alt="https://www.browserstack.com/guide/testing-pyramid-for-test-automation" src="https://cdn-images-1.medium.com/max/1024/0*apNTqgIBFQ8HL7Kf.jpg" /><figcaption><a href="https://www.browserstack.com/guide/testing-pyramid-for-test-automation">https://www.browserstack.com/guide/testing-pyramid-for-test-automation</a></figcaption></figure><p>E2E testing is said to be slow, more fragile, and expensive to maintain. The challenge is that E2E for systems running in a browser is often sensitive to the frequency of changes in the user interface. I think this case shows that it is not possible to overcome this issue in a. straightforward manner if we compete with the tools we currently have, but conversely, the evolution of tools can create reverse feedback to the way we think.</p><p><strong>What if AI could fix broken tests in order to solve the maintenance cost issue</strong> (i.e. tests tend to be vulnerable to change, a team can’t afford to hire dedicated test automation engineers, and etc)?</p><p><strong>What if a test automation service is designed so that anyone can easily create automated tests and maintain the created tests to address the issue of test creation costs</strong> (i.e. a team doesn&#39;t have the time to create a test infrastructure …etc)?</p><p>If the tools eliminate such issues ahead of time, then the strategy and tactics will change.</p><p>By the way, this example is exactly what Autify does.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gISRXf79kR2zLAQ7sHehnQ.png" /><figcaption><a href="https://speakerdeck.com/autifyhq/autify-company-deck-efd29263-1045-43c2-b2a0-17328638b0fe?slide=15">https://speakerdeck.com/autifyhq/autify-company-deck-efd29263-1045-43c2-b2a0-17328638b0fe?slide=15</a></figcaption></figure><p>I have struggled with automating email tests and made the decision to leave it for manual testing because of high realization costs. Right after that, I was shocked to know that Autify can create automated email tests.</p><p><a href="https://autify.zendesk.com/hc/en-us/articles/900001934846-Email-Test">Email Test</a></p><p>Also, when I introduce Autify (and other test automation services), some folks who are familiar with test automation will mention their concern about record-and-playback. Mr. Suemura of Autify explains how Autify is trying to solve the issues pointed out by traditional testing in the following entry</p><p><a href="https://blog.autify.com/record-and-playback">Is it true that record-and-playback is not an automated test? | Autify Blog</a></p><p>It concludes by saying this.</p><blockquote>At Autify, we continue to evolve our platform towards a more ideal test automation tool based on user feedback and reflecting on existing issues with record-and-playback tools. If you’ve had a bad experience with other record-and-playback tools, I strongly suggest trying Autify. If you are interested,</blockquote><p>It is often said that technology evolves in a spiral, and I believe that the field of test automation is currently in a period of accelerated evolution.</p><h4>3. Not learning from a company, challenging with a company</h4><p>I’ve worked for both my first and second companies, both of which were mid-range companies with 70–300 employees. That’s why I prefer start-ups rather than big tech companies with thousands or millions of employees.</p><p>As my next personal challenge, I would like to work in the English-speaking technical community, not only developing software services but also writing blogs and speaking at conferences. Specifically, my mid-term milestone is to publish a commercial book in the English-speaking book market.</p><p>Autify is a startup of just over 30 people currently taking on the challenge of succeeding in the global market since its foundation. As Autify becomes widely recognized and implemented globally, I would like to take on the following challenges.</p><ul><li>Contribute as a software engineer to Autify</li><li>Form a good culture as a global engineering team as the team expands in the future</li><li>Expand the scope of the engineering community I am involved with globally</li></ul><h4>4. It would satisfy my curiosity as a software engineer</h4><p>My curiosity as a software engineer is somewhat extreme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OA9A5SB8OaaNKWzARyCrzQ.png" /><figcaption>I’m more interested in orange parts.</figcaption></figure><p>It is thrilling to be exposed to abstract, longer-term, nurturing ideas such as Christopher Alexander’s Pattern Language and XP philosophy.</p><p>Another moment that brings me joy is the moment when I reveal the mechanism “behind the API”. In the case of Selenium, it’s not so much the moment I learn how to use the selenium library, but the moment I understand the specification of Selenium WebDriver behind it (<a href="https://speakerdeck.com/hgsgtk/create-go-webdriver-client-from-scratch">my slide</a>).</p><p>I was convinced that Autify would be a good fit for my curiosity for the following reasons.</p><p>The development of a test automation service has two aspects: <strong>the “needs solving” aspect</strong>, where we understand the customers and provide solutions to their problems, and <strong>the “visionary” aspect</strong>, where we develop products to realize our vision as a platform service. Thinking about the future of the service that solves the problem of software providers is directly synonymous with thinking about how to achieve lively software development.</p><p>On the other hand, Autify development is mainly the behind of “API” that is abstracted in common web application development (i.e. The specification of selenium WebDriver, deep knowledge of network protocols at RFC level).</p><h3>Join as a backend engineer</h3><p>I’m joining Autify as a “backend engineer” which role works on all layers below Ruby on Rails.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qobHNi4PSUWKcgOZuTIwZQ.png" /><figcaption><a href="https://speakerdeck.com/autifyhq/autify-company-deck-efd29263-1045-43c2-b2a0-17328638b0fe?slide=39">https://speakerdeck.com/autifyhq/autify-company-deck-efd29263-1045-43c2-b2a0-17328638b0fe?slide=39</a></figcaption></figure><p>I could have chosen to be an engineering manager or QA engineer as my career, but I chose to be a backend engineer because I could contribute more to the company.</p><p>I’ll do my best to contribute to the success of Autify’s business and products.</p><h3>Conclusion</h3><p>If this entry has made you interested in Autify services, try sending a “demo request” from <a href="https://autify.com/">here</a>.</p><p>Also, if you are interested in joining Autify team, take a look at the company deck which is available on <a href="https://speakerdeck.com/autifyhq/autify-company-deck-efd29263-1045-43c2-b2a0-17328638b0fe">Speaker Deck</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a6285b38fb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BDD is not just a test automation practice (Book review: The BDD Books — Discovery)]]></title>
            <link>https://medium.com/@hgsgtk/bdd-is-not-just-a-test-automation-practice-but-a-collaborative-practice-book-review-the-bdd-ec24b1976487?source=rss-aec8ceaac4a2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec24b1976487</guid>
            <category><![CDATA[sbe]]></category>
            <category><![CDATA[bdd]]></category>
            <category><![CDATA[atdd]]></category>
            <dc:creator><![CDATA[Kazuki Higashiguchi]]></dc:creator>
            <pubDate>Tue, 07 Dec 2021 14:20:48 GMT</pubDate>
            <atom:updated>2021-12-07T14:43:40.380Z</atom:updated>
            <content:encoded><![CDATA[<p>How many of you can explain what BDD is?</p><p>If you were writing Gherkin in cucumber, would it be BDD? Or if you use RSpec to automate your tests, is it BDD? Or is it BDD if you were creating high-level automated tests such as E2E?</p><p>If you think that any of them is the true answer, you’d better read the book I’m about to introduce. You are missing an important understanding of BDD.</p><p>Typical mistakes are to look at BDD as a tool-thing, or to think of BDD as a mechanical process, such as filling out a Given/When/Then template.</p><h3>The BDD Books — Discovery</h3><p><a href="https://medium.com/r?url=https%3A%2F%2Fleanpub.com%2Fbddbooks-discovery">The BDD Books — Discovery</a> was published by <a href="https://leanpub.com/u/gasparnagy">Gáspár Nagy</a> and <a href="https://leanpub.com/u/sebrose">Seb Rose</a> on 2018–02–23.</p><p><a href="https://leanpub.com/bddbooks-discovery">The BDD Books - Discovery</a></p><p>The BDD Book series consists of three ones, Discovery, Formulation, Automation. <a href="https://medium.com/r?url=https%3A%2F%2Fleanpub.com%2Fbddbooks-discovery">The BDD Books — Discovery</a> is the first in them.</p><p>This book is referenced within the presentations of BDD practitioners. For example, Riya Dattani and Chris James gave a presentation on <a href="https://www.youtube.com/watch?v=ZMWJCk_0WrY&amp;list=PLDWZ5uzn69ex0U5MmbKWorsTuVBgUePxw&amp;t=2689s">Acceptance Tests, BDD &amp; Go</a> at <a href="https://www.gophercon.co.uk/">GopherCon UK 2021</a> and introduced this book.</p><p>Discovery, Formulation, and Automation are three practices in BDD.</p><figure><img alt="quoted by http://www.bddbooks.com/resources/discovery/figures.html" src="https://cdn-images-1.medium.com/max/1019/0*7frbV0E29k0nX34F.png" /></figure><ul><li>Discovery: a structured, collaborative activity that uses concrete examples to uncover ambiguities and misunderstandings</li><li>Formulation: a creative process that turns the concrete examples produced during discovery into business-readable scenarios</li><li>Automation: to turn the scenarios into automated test codes</li></ul><p>This book describes the first practice “Discovery”. That’s why the table of contents is as follows.</p><blockquote>Chapter 1 — What is BDD?<br>Chapter 2 — Structured conversation<br>Chapter 3 — What is an example?<br>Chapter 4 — Who does what and when<br>Chapter 5 — How to get business involved</blockquote><p>In this book review, I will focus on the important points that impressed me and that I would like to examine in more detail.</p><h3>BDD is a collaborative work</h3><p>As stated in <a href="https://agilemanifesto.org/">Manifesto for Agile Software Development</a>, collaboration is an important factor in an agile team.</p><p><a href="https://agilemanifesto.org/">Manifesto for Agile Software Development</a></p><blockquote><strong>Individuals and interactions</strong> over processes and tools<br>Working software over comprehensive documentation<br><strong>Customer collaboration</strong> over contract negotiation<br>Responding to change over following a plan</blockquote><p>And, BDD is an agile approach that insists that detailed requirements for a feature should be defined collaboratively by the business and delivery teams.</p><p>When learning about BDD, ATDD, and SBE, many software developers overlook their collaboration aspect. This series “Discovery” focuses on their collaborative practice using concrete examples and leaves the explanations of formalization like how to use Gherkin and test automation techniques in other books (Formulation, Automation). So that readers can focus more on the collaboration aspect.</p><h3>BDD/ATDD/SBE, what’s difference</h3><p>The following link is introduced in this book.</p><p><a href="https://lizkeogh.com/2011/06/27/atdd-vs-bdd-and-a-potted-history-of-some-related-stuff/">ATDD vs. BDD, and a potted history of some related stuff</a></p><p>First, <a href="https://medium.com/r?url=http%3A%2F%2Fdannorth.net%2Fintroducing-bdd%2F">Dan North</a> started doing BDD at a unit or class level, as a replacement for TDD (late 2004).</p><p><a href="http://dannorth.net/introducing-bdd/">Introducing BDD</a></p><blockquote>At the end of 2003, I decided it was time to put my money — or at least my time — where my mouth was. I started writing a replacement for JUnit called JBehave, … (omit) <br>It would contain methods that started with the word “should.”</blockquote><p>Then, Chris Matts introduced <a href="https://martinfowler.com/bliki/GivenWhenThen.html">Given-When-Then</a> template and most people who do ATDD use it.</p><p>The author of the article “<a href="https://lizkeogh.com/2011/06/27/atdd-vs-bdd-and-a-potted-history-of-some-related-stuff/">ATDD vs. BDD, and a potted history of some related stuff</a>” said that all of them are the same concept nowadays, but called by different names.</p><blockquote>The difference is that one is called Behaviour Driven Development — and some people find that wording useful — and one (or two) is called (Acceptance) Test Driven Development — and some people find that wording useful in a different way.</blockquote><h3>One of example-driven development</h3><p>Although it is not mentioned in the book, example-driven development came to my mind in relation to the above topic.</p><p>Lisa Crispin and Janet Gregory insist on the power of guiding development with examples in their book <a href="https://agiletester.ca/more-agile-testing-the-book/">More Agile Testing</a>. They learned example-driven development from Brian Marick who is one of the signers of the Manifest for Agile Software Development.</p><p><a href="https://medium.com/@JoshuaKerievsky/example-guided-a-brief-history-f004ca19a96f">Example-Guided, A Brief History</a></p><blockquote>In the early 2000s, he named his blog <a href="http://exampler.com/blog/">Exploration Through Example,</a> spoke about Example-Driven Development (EDD), organized an “Examples” stage at the large Agile200x conference and produced a wonderful sticker:</blockquote><p>In <a href="https://agiletester.ca/more-agile-testing-the-book/">More Agile Testing</a>, they introduce BDD, ATDD (Acceptance test-driven development), and SBE (Specification by Example) are variants of Example-driven Development.</p><p>From this, we can understand that the fundamental concept is to gain a common understanding using concrete examples.</p><h3>BDD rhythm</h3><p>In this book, BDD rhythm is explained by the following diagram.</p><figure><img alt="quoted by http://www.bddbooks.com/resources/discovery/figures.html" src="https://cdn-images-1.medium.com/proxy/0*RydQv-6sbP3s0LZF.png" /></figure><p>Requirement workshop is similar to the following work, three amigos meeting, discovery workshop, specification workshop, story refinement, product backlog refinement. Many explanations of Example-driven development, not just BDD, began with one of these names. The important thing is to take the time to discuss the details of user stories with business people; the name of the workshop is not important.</p><h3>Example mapping</h3><p>This book introduces <a href="https://cucumber.io/blog/bdd/example-mapping-introduction/">Example mapping</a> as a meeting format for a requirement workshop.</p><p><a href="https://cucumber.io/blog/bdd/example-mapping-introduction/">Introducing Example Mapping</a></p><p>The work format for Example mapping consists of Story, Rule, Example, Question.</p><figure><img alt="quoted by https://cucumber.io/blog/bdd/example-mapping-introduction/" src="https://cdn-images-1.medium.com/proxy/0*iVq22KtZKPM7rSkQ.png" /></figure><ul><li>Examples illustrate the concrete behaviour of the system.</li><li>Rules are logical groupings of examples usually focusing on a particular condition. It is also called acceptance criteria, business rules, and requirements.</li><li>Questions or assumptions are any topics that would block the discussion.</li><li>User stories are starting points of discussion.</li></ul><p>This workshop seems to be very useful for those who have trouble with a blurred understanding of the system they are implementing. It is common to find out that the specification was misunderstood during sprint review stage after implementation, or just before release without noticing it during relevant iteration. Example mapping can be an effective practice to solve actual software development problems.</p><p>I think the sticky notes “Question” is useful. Since these are visible to team members, we can avoid re-discussing these topics again and again.</p><h3>Concrete example</h3><p>Concrete examples are key factors for successful BDD. I’ve understood it before but I was vague about how specific it should be.</p><p>By the way, I understood each example should mention concrete data, but I’m vague about how specific it should be.</p><p>This book give us a useful hint.</p><blockquote>Each example illustrates a single rule, and should only mention concrete data that is directly related to the behaviour being illustrated.</blockquote><p>When we try to make concrete examples, we tend to make everything unnecessarily specific. I used to be one.</p><h3>Merit for product owner</h3><p>BDD can help reduce the product owner’s workload. In BDD, product owners activities would be:</p><ul><li>participate in requirement workshops</li><li>review the scenario</li><li>give feedback about the implemented application</li></ul><p>Classic product owner activities are writing specifications, presenting the stories to the team and etc. It is difficult for product owners to continue to have to be the drafter of specifications because they tends to be busy. However, with example mapping, the product owner can get out of the situation of being the “single point of failure”.</p><h3>Reference books</h3><p>This book mentions the richness of the examples presented by <a href="https://www.manning.com/books/specification-by-example">Specification by Example</a>. <a href="https://www.manning.com/books/specification-by-example">Specification by Example</a> is linked as a great reference book by various books, so I also recommend reading it as well.</p><p>Here are some books that I’ve read when I was practicing BDD myself.</p><ul><li><a href="https://www.manning.com/books/specification-by-example">Specification by Example</a></li><li><a href="https://www.manning.com/books/bdd-in-action-second-edition?gclid=CjwKCAiAhreNBhAYEiwAFGGKPBMR8ekGqQZiyLJd88uIbzt7hgCt2wjLVLZTJxPL-XVH-L_ApJ_hDBoCKAwQAvD_BwE">BDD In Action, Second Edition</a></li><li><a href="https://www.amazon.com/Growing-Object-Oriented-Software-Guided-Tests/dp/0321503627">Growing Object-Oriented Software, Guided by Tests</a></li><li><a href="https://www.amazon.com/Test-Driven-Development-Kent-Beck/dp/0321146530">Test-Driven Development: By Example</a></li><li><a href="https://www.amazon.co.jp/-/en/Janet-Gregory-ebook/dp/B07YR4CC4B">Agile Testing Condensed: A Brief Introduction</a></li><li><a href="https://www.bookdepository.com/Agile-Testing-Lisa-Crispin/9780321534460?redirected=true&amp;utm_medium=Google&amp;utm_campaign=Base1&amp;utm_source=JP&amp;utm_content=Agile-Testing&amp;selectCurrency=JPY&amp;w=AFFBAU9SF76H8CA8V9RU&amp;pdg=pla-317692435101:kwd-317692435101:cmp-8752714707:adg-87125587846:crv-410025753095:pid-9780321534460:dev-c&amp;gclid=CjwKCAiAhreNBhAYEiwAFGGKPKRzP9W_TXBn8HSBhos4SfZ59aqHW2jrkJ1AgOwjCwGiwHB3aHE0rBoCqD8QAvD_BwE">Agile Testing: A Practical Guide for Testers and Agile Teams</a></li><li><a href="https://agiletester.ca/more-agile-testing-the-book/">More Agile Testing</a></li><li><a href="https://www.manning.com/books/test-driven">Test-Driven Practical TDD and Acceptance TDD for Java Developers</a></li><li><a href="https://www.amazon.com/ATDD-Example-Test-Driven-Development-Addison-Wesley-ebook/dp/B008G1H3EG/ref=sr_1_1?crid=14S6B7PC18NN7&amp;keywords=atdd+by+example&amp;qid=1638784649&amp;sprefix=atdd+by+e%2Cstripbooks-intl-ship%2C289&amp;sr=8-1">ATDD by Example: A Practical Guide to Acceptance Test-Driven Development</a></li><li><a href="https://gojko.net/books/bridging-the-communication-gap/">Bridging the communication gap</a></li></ul><p>All of them are good, but <a href="https://medium.com/r?url=https%3A%2F%2Fleanpub.com%2Fbddbooks-discovery">The BDD Books</a> is the best in learning the aspect of collaboration, which many books consider to be a fundamental element but fades away as readers read the book latter half of the book.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec24b1976487" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>