Recently I participated in Craft Conf 2022 which is one of the world's biggest developer conferences. There were more than 70 talks from top-notch experts from all around the world. The event was held in Budapest the capital of Hungary. Thanks to this I was able to visit the conference on-site.

Being a test automation engineer for no surprise my main focus was on listening to talks about various quality assurance topics. There were only a few talks in this category so I had the chance to listen to all of them. One of them was Fabrice Bernhard's fascinating talk about the Dantotsu method with which you can radically improve the quality of your software. I have already written my summary of that talk which you can find on my blog.

Being a Hungarian I definitely wanted to listen to the talks of the Hungarian speakers and to my luck I found one talk about test automation patterns by the Hungarian Gáspár Nagy. Jackpot.

Gáspár Nagy works as an independent coach, trainer, and test automation expert helping teams to implement Behaviour Driven Development (BDD). Gáspár's talk about test automation patterns inspired me to write this article. In the first part of this writing, I will highlight some of the topics from Gáspár's speech and in the second part I will talk about a tool Selenideium Element Inspector which I developed to automate one of the most repetitive tasks in end-to-end testing and I will also talk about 2 patterns I use in test automation.

A Brief History of Design Patterns

Have you heard about the term GoF? Not familiar? What about Gang of Four? I am pretty sure by this point most of the developers know what will I am talking about here.

It is the book Design Patterns: Elements of Reusable Object-Oriented Software. This book is kind of a bible for developers. The book has been published in 1994 which means 28 years ago. (Oh crap, I am too old) Despite being so ancient this book is still very actual many of the patterns are used by developers. By now these patterns became part of programming languages and libraries. However, Christoper Alexander came up with the concept of design patterns in 1977, this book was which made them popular.

The term design pattern was borrowed from architecture. In architecture, you do not start from zero when you would like to build something but you use previously proven patterns by which you make sure the building will function as expected.

If you are using design patterns you can progress faster, have a more reliable and maintainable code, and you also have a common language among developers. You do not have to explain the code all the time you just say I used the Builder pattern here or the Factory pattern there.

Test Automation Patterns

Test automation code should be a first-class citizen, which means it should have the same quality as production code. How can we achieve for our production code to have great quality? We can follow coding standards, do reviews, use design patterns, and of course write tests for our code. That raises a very interesting topic which was explained in Gáspár's talk in a pretty funny way: if tests should have the same quality as production code, then we need tests to make sure it has high quality, but those tests should also be the same quality as production code which results in an endless loop.

In order to break that loop, we are typically applying exploratory testing to our tests. Many testing schools like TDD say you should see your test failing first and move forward only afterward. By seeing the tests first failing you can make sure your test can actually catch some error. That is exactly what we do in TDD.

As mentioned above, using design patterns can improve the quality of your code but the good news is you can also use test automation patterns to improve the quality of your tests.

Tests are typically composed of some sort of usual tasks for example for a complex automated test you have to reset the database to a known state. Collecting these usual repetitive tasks and their solutions into a test automation pattern knowledge base can help in not inventing the wheel every time. These patterns can be useful on a team level, some of them on a company level and some of them can be also useful outside your company.

In the upcoming part, I write about a repetitive task I have automated and I also introduce two design patterns. Let's see them one by one.

Automating Locator Creation

As a test automation engineer, my daily job includes writing both API and E2E tests depending on the actual need of the project. During writing E2E tests one of the most time-consuming tasks is to find the best locator of a certain web element.

As Gáspár mentioned test automation patterns usually emerge from automating repetitive tasks and then reusing the same method again and again. This is actually what I did by developing the Selenideium Element Inspector (SEI) Chrome Extension.

Let me explain the task with an example. I have a complex form where you have to enter numerous personal information. For simplicity let's say the first name and last name are mandatory and the others are optional. I would like to test a happy path where I only fill the mandatory fields. For simplicity let's say it is just a part of the test and we won't do any assertion (more about that will come later).

So what is the task I should do? I have to determine a locator for the first name text field, the last name text field, and also for the submit button.

In an ideal world each web element has an ID or a class based on which every element can be located easily, but let's be honest very often that is not the case. Cause of this I have to come up with a locator based on ID, name, className, tagName, linkText, partialLinkText, CSS or xPath. Or at least those are the locators that you can use with Selenium Webdriver which is one of the most widely used frameworks for E2E test automation and also the one we use in combination with Selenide (more on that later) in our team.

At this point, I open Chrome dev tools and start to inspect the web elements. Let's say my first name text field has no id, but it has a class that seems unique. As I am not sure about that I open the console to run the selection in the form of a CSS selector just to realize there are other elements with the same class. Maybe it is not the best example, but if you did automation for a while I am pretty sure you encountered such problems.

So I look at the DOM again and come up with a CSS selector with which I can select the exact element. Then I repeat the procedure for the last name and also for the submit button. Of course, you can become pretty quick in writing locators still it is quite repetitive.

This repetitive task is not specific to my team, to Selenium but it is a task that has to be done by everyone writing E2E tests. Of course, some framework provides support for recording user interactions even Selenium has Selenium IDE, but I wanted a faster solution and also I did not want to leave the final choice for a framework as it can often happen that an id or class which it selects is an autogenerated value which will change on each page load.

In the end, I decided to develop a Chrome Extension with which you can automatically generate each relevant unique locator for a web element with a single click. You can not just generate the locator, but a complete line of copy-pastable code. You just have to look at the console and copy-paste the guaranteed unique selectors to your favorite IDE.

In the first run, I only implemented the code generation for Selenium Java and Selenide but I had some discussions with my colleagues from other teams during which I learned they are using TestCafe and Squish so I decided to support those frameworks too. By now I've added support for most of the other widely used frameworks including Playwright and Cypress and Selenium Javascript, C#, and Python too.

After I have developed the plugin I realized there are other similar tools like SelectorsHub, but I still prefer using my plugin as you can generate everything with a single click.

Of course, there is a lot of space for improvement one idea on my mind is to automatically generate page object models from the selected web elements. Please, feel free to share your thoughts in the comments section.

You can read more about the plugin including full source code here, here and here and you can download it from the Chrome Webstore.

The Page Object Model (POM) and Tester Pattern Duo

During the talk, Gáspár encouraged us to share test automation patterns that we use, so I decided to share two patterns I use in end-to-end test automation. However, Gáspár gave his suggestion on how to document a pattern I did not want this article to be too formal so I decided to simply explain these patterns with my own words, but Gáspár is working on a book with his colleagues which will contain many test automation patterns in a structure very similar to the GoF book. I am really looking forward to reading that book.

In order to introduce the patterns let me sketch up a simple scenario.

We have a login page with two text fields a username and a password and of course, we have a log-in button. After a successful login, the user is navigated to its profile page. In our test, we will test the positive scenario when we enter valid credentials and the user successfully logs in. After the login, we will verify the user is really logged in by making sure the user's name is visible and a logout button appears on the screen.

The Framework

As far as I know, Selenium Webdriver is the most widely used framework for web application testing. It is open-source, easy to learn, and supports many programming languages, browsers, and platforms. Well, in this article I won't use Selenium but I will use Selenide instead. Let me explain why.

Selenide is an open-source framework built on top of Selenium WebDriver whose main purpose is to make test automation simple. As it is based on Selenium WebDriver it also means we get the full feature set of Selenium WebDriver.

In addition to that, it has simpler syntax, a concise fluent API, additional selectors, simple configuration, profiler, and more. If you are interested in a more in-depth comparison just read my article Selecting an End to End Testing Framework - Selenium or Selenide?. Anyone who is familiar with Selenium WebDriver or other test automation frameworks can easily understand the Selenide tests.

Despite having the above-mentioned advantages Selenide is not as well known as it should be, so I would like to grab the opportunity to draw attention to it. However, in this example I will use very little from its functionality you can learn more about it in one of my previous articles..

The Test

For simplicity, I will use id-based locators and hardcoded test data as they are not relevant for introducing the patterns. So let's see the example code:

@Test
    public void successfulLogin() {
        open("https://mywebapp.com/");
        $(byId("username")).sendKeys("johndoe");
        $(byId("password")).sendKeys("pass");
        $(byId("login-button")).click();

        $(byId("logout-button")).shouldBe(visible);
        $(byId("user-display-name")).shouldHave(text("John Doe"));
    }

Selenide handles timeouts and the web driver in the background so we do not have to deal with them which makes our life much easier and we can also forget about the StaleElement exception. We have our test so it is time to do a little refactoring by introducing the Page Object Model.

Page Object Model (POM)

If there is only one test automation design pattern a developer knows I am pretty sure it is the POM. Using the POM pattern we create a corresponding class (Page Object) for each page in which we encapsulate all the web elements belonging to that page. In addition to that, we can also encapsulate higher-level interactions like the user login in our case.

Why we should use POM? Just imagine you have a web element that you use at multiple locations in your test code. If the element changes you have to modify all occurrences. In simple terms, we have a much more maintainable code by using the POM pattern, and also we can make our tests more readable by encapsulating multiple-step interactions into methods with meaningful names. Clean code is not just important for production code but also for tests.

Let's see our code for the login page:

public class LoginPage {

    private final By usernameInput = byId("username");
    private final By passwordInput = byId("password");
    private final By loginButton = byId("login-button");

    public void login(String username, String password) {
        $(usernameInput).sendKeys(username);
        $(passwordInput).sendKeys(password);
        $(loginButton).click();
    }

}

And also for the profile page

public class ProfilePage {

    private final By logoutButton = byId("logout-button");
    private final By userDisplayName = byId("user-display-name");

    public SelenideElement getLogoutButton() {
        return $(logoutButton);
    }

    public SelenideElement getUserDisplayName() {
        return $(userDisplayName);
    }

}

And the refactored test:

    @Test
    public void successfulLogin() {
        LoginPage loginPage = new LoginPage();
        ProfilePage profilePage = new ProfilePage();
        open("https://mywebapp.com/");
        loginPage.login("johndoe", "pass");
        profilePage.getLogoutButton().shouldBe(visible);
        profilePage.getUserDisplayName().shouldHave(text("John Doe"));
    }

Well at first look it might seem overkill to do this as from the 6 lines long test we made another 6 lines of test and 2 extra classes but imagine we have many login scenarios using the same elements again and again or having webpages with dozens of elements. From the page object, you can easily get an overview of the different elements belonging to a page. The two page objects can be moved to a before test initialization and if we have only login scenarios in this file then the webpage opening can be moved too, resulting in this code:

    @Test
    public void successfulLogin() {
        loginPage.login("johndoe", "pass");
        profilePage.getLogoutButton().shouldBe(visible);
        profilePage.getUserDisplayName().shouldHave(text("John Doe"));
    }

This code reflects our intention much more as it is clear we are doing login, but there is one problem with it. It does not reflect our intention regarding what we would like to test and here comes the Tester pattern in the picture.

The Tester Pattern

If you are not familiar with the name Tester pattern it is not your fault. I made up this name for the pattern as I have not heard about it before. I see very little chance that nobody else came up with this pattern before so if you know its original name then please share it with us in the comment section.

So what is our intention here? We would like to verify the user logged in. Let's make it clear by introducing the Tester pattern:

public class LoginTester {
    private final ProfilePage profilePage;

    public LoginTester(ProfilePage profilePage) {
        this.profilePage = profilePage;
    }

    public void verifyUserLoggedIn() {
        profilePage.getLogoutButton().shouldBe(visible);
        profilePage.getUserDisplayName().shouldHave(text("John Doe"));
    }
}

And the test after moving the tester initialization into a pretest initialization code:

    @Test
    public void successfulLogin() {
        loginPage.login("johndoe", "pass");
        tester.verifyUserLoggedIn();
    }

If we are taking into account the initialization code then we have a clear given-when-then structure which makes our test code easily understandable and maintainable.

That was my intro to the Tester pattern in a nutshell. I use it as it makes my life easier but I am pretty curious what you think about it. Do you find it useful? Or do you see some drawbacks? Share your thoughts in the comment section.

Thanks for staying with me up till this point. I am pretty sure you also have some test automation design patterns in your bag so do not hesitate to share them in the comment section.

I went to the Craft Conf with exact goals. I have written in my previous article Why Am I Attending The Craft Conf 2022 Software Development Conference? about them. I advise reading it before this writing as I will revisit my goals one by one and reflect on how much I was able to achieve from them.

Backstory

I remember I was a little nervous before the day of the conference. As I explained in my previous article, I am an introvert. The idea of being together with hundreds of software developers freaked me out a little bit.

Luckily I was not alone, as 4 of my friends came with me to the Craft Conf. I cannot exaggerate enough how much it meant for me. The idea of spending two days with my developer friends, talking about software development, and of course, about other friendish stuff made me happy and helped to reduce my nervousness.

I was not sure what to wear during the conference, but I was not alone with that problem as two of my friends also asked me about that. In the end, we decided to dress as we would go to work. For me, it meant jeans, a Hashnode T-shirt, and a shirt too which I took off in the end as it was pretty hot.

In today's fast-paced world, where new technologies emerge yearly, it is very important to train yourself if you do not want to fall behind. By now, many companies have realized how important it is to support their employees by sending them to training or giving them conference tickets. It is important for the company not just because the new learning will benefit them too, but also because this can be a factor that motivates a developer to stay with the company. At least for me, it is an important factor.

Unfortunately, my previous company hardly ever supported me in improving myself, which was also why I did not attend conferences before. Finally, after 15 years, I moved to another company in December.

My new company is different as it provides a budget and 4 extra holidays for its employees to train themselves. I have already spent one day visiting the Future of Testing Framework conference, about which you can read my report here. So I could visit the Craft Conf using two days from my holiday budget. I am not exactly sure what will I do with my fourth day. Still, if I have to answer now, then I would say I will visit the Crunch Conf, which is also organized by CraftHub, but instead of software developers, it is targeting Data Engineers and Data Scientists.

What about the imposter syndrome? Luckily I left it behind around half a year ago. So I was excited to visit the conference, as instead of thinking, "I have no place amongst these much better developers," I felt I would be in the right place with fellow developers who would be there to learn and have fun just like me.

That is enough about the backstory. Let's start the conference.

Registration

We arrived quite early at the conference as luckily my friend Szabi brought me to the location by car. Our first journey led us to the registration booth. It was quite a surprise to see the registration is on the dodgem field. Look: There were many desks where you were able to register. Almost nobody was there when we registered, but based on the number of staff there, I am pretty sure the fellow developers could register quickly too.

Catering

After the registration, we entered the building and headed directly to the breakfast area as both of us were hungry, especially me. A few (at least compared to the total number) of the developers were already having breakfast, as you can see in the picture. There were sandwiches and other food too and even dessert. I am a meat lover, so I sadly realized all the sandwiches were vegetarian, but this sadness faded as soon as I tasted the sandwiches. They not just looked good, but they were delicious too.

This was the same place where we had lunch. Luckily lunch was not self-serving, as I think it would have been chaos if hundreds of hungry developers would have appeared in an all-you-can-eat area. So the food was served by the staff thanks to which you did not have to wait too much. There were chicken, pork, beef, fish, and vegan food so that everyone could find something for him/herself.

There were many stands where you could get drinks and coffee too. Luckily there were many glasses prefilled with drinks, so you could simply grab one when thirsty. All in all, the food was delicious and as it was all-you-can-eat I am pretty sure no developer remained hungry.

Now that our stomach is full, let's look around at the location.

The Location

Craft Conf took place at the Hungarian Railway Museum. I have to admit I did not look around thoroughly, but during a lunch break I went out to see the locomotives. I have spent more than 10 years of my life traveling by train twice a week to visit my parents, then go back to school. To be honest, I did not like traveling, but I still love locomotives. I remember there was a beautiful black locomotive at the Mezőhegyes railway station. I loved that locomotive. We always jumped on it with my brother Tamás and played in the cockpit. After checking the trains it is time for a cigarette.

The Smoking Area

I have to admit, all my friends and also myself are smokers. Thanks to this our meeting point was the smoking area. After each talk, we gathered together in front of the main entrance where the smoking area was located. During smoking, we discussed the previously heard talk and also used the time to have many friendly talks. For me, that was the best part of the conference. Of course, we heard amazing talks and had a lot of fun, but spending two days with my friends was invaluable.

Talks and Speakers

More than 70 speakers were invited to the Craft Conf 2022. Most of them were there personally and the others had an online talk. Arranging the speakers' traveling, accommodation, local transportation, and creating the schedule must have been very difficult, but the CraftHub team did a great job, in my opinion.

Kevlin Henney opened the conference with the talk Non-Functional coding. His speech was fascinating and fun at the same time. Perfect start for the conference. I even brought a picture of one of the slides.

The Main Stage was full. You could even smell the scent of software development.

However, depression was not inside me this time, but it was pretty close to me as it was sitting right in front of me, as you can see in the picture above. I have no idea why the guy in front of me wore that T-shirt, but I was too shy to ask.

I used to love visiting meetups, as in addition to learning and networking, I always got a huge motivation boost for weeks. I am eagerly waiting for how long will the motivation boost last this time.

If you read my previous article, you know my plan was to visit Michael Feathers', Dan North's, and Ivett Ördög's talk.

Michael's talk was the first one on the list. So I went to platform 2 to listen to his talk. To my biggest surprise, there was a completely different speaker there. I suppose the talk was canceled, and I did not reload the schedule on my phone. Never mind. As a photographer, I loved Platform 2. Just look at the lights:

When I realized Dan North's talk was a virtual talk, I decided to watch the talk from recording and visit a real-life talk instead, as that is the beauty of offline conferences. Listening to talks of top-notch developers from all around the world in person.

Luckily I could listen to Ivett's talk, which was the last talk of the conference. She was talking about how to sell a big refactor to the management. I had expected a bit more practical advice, but the presentation was still interesting.

I found Fabrice Bernhard's talk the most fascinating at the whole conference. I have to admit I am highly biased towards QA topics as I work as a test automation engineer. Fabrice was talking about the Dantotsu method with which you can drastically reduce the bugs in your code. I will write an article about his presentation as I would like to share the Dantotsu method with my team as I am pretty sure it would benefit us too.

To sum it up, there were many great talks during these two days, and I could only listen to a small portion of them thanks to the many parallel talks. I am pretty sure I will spend hours listening to the missed talks, and I will also watch some of the talks again as I would like to write a few articles about the ones I found most interesting.

Exhibitor Booths

Many of the conference supporters had a booth in the exhibition area. Epam, Morgan Stanley, Cloudera, Tesco, and of course CraftHub just to mention a few of them.

I believe the exhibitors knew most of the developers are there to learn and have fun and not to find a job, cause of this many of them prepared some minigames which made the booth visits quite memorable. Instead of job ads, they asked for your approval to get your contact info, so they could reach us after the conference with relevant content. I already got a few emails and I am sure more is on the way.

I have visited almost all the booths and played most of the games. You could win prizes by playing. Let's mention the most memorable minigames.

Minigames

Epam had a smartphone slide challenge where you got points depending on how close you could slide your phone to the center of the target. Sliding the phone to the center gave access to the highest gift category. My first slide was too weak and the second one almost blocked the center, but I nailed it on the third try. Here is a pic of the game:

At adnovum, you had to play an AR game. You had to catch bugs using a phone's camera on which either a cake or a bug appeared when you moved your camera above a symbol on the wheel. It was quite fun so I played it both on the first and second day too.

At the Tresorit booth, you had to open a safe by getting the code of the safe by answering a few questions from which you could figure out the code. Of course, we opened it and we could even get some chocolate from the safe.

At the Tesco booth, you had to decrypt a message which pointed to a location. I couldn't solve it right there but a cigarette later I went back with the solution.

(Almost) all the exhibitors had a grand prize. You could participate in the drawing by sharing your personal info and the winners were mostly selected randomly. Unfortunately, I had not won any of the grand prizes but I was not sad about that because of the swags.

Swag Here, Swag There, Swag Everywhere

The exhibitors prepared for the Craft Conf with an extreme amount of swag. I did not realize up till now how fun it is to collect swags. There very everything you could imagine. Pens, notebooks, socks, sunglasses, t-shirts, and even rubber ducks. I have to admit I might get too excited and collected too much swag, but I had a good excuse. I have collected almost all the swags for my son. This is mainly true, but I also gave some of them to my wife and I also kept a few. Here is a pic of almost all the loot I collected at the conference. 😊

The Staff

The CraftHub staff was very kind and helpful and we could even get mango-flavored beer from them, so it was no question whether we visited them or not. At the location, there were many people with a Staff label on their T-shirts who were there to help us if we had any questions.

Despite I had a map I had no idea where the Innovation stage was so a friendly staff guided me there. Actually, it was right behind me but I did not realize it. 😊

After the second talk on the main stage, I went to the CraftHub booth and asked them to increase the volume on the speakers' mic as thanks to sounds coming from the lively exhibition area we had a hard time listening to the talks from the back rows. They were quite helpful and I am almost sure they increased the volume, as, from the following presentation, I had no problem with it.

Networking Party

Unfortunately, I could not participate in the networking party as I had to go home to be with my son as my wife had an important appointment, but one of my friends was there and he told me it was great. Epam supported everyone with 4 beer coupon so the mood was guaranteed. Maybe next year I can visit the party too.

Being a Kid Again

Even at the age of 40, I still consider myself a kid, as I never grew up. Especially nowadays, when I play a lot with my son I can enjoy such activities as playing lego, video games and much more without feeling any guilt of not spending my time on "useful things". Luckily there were many activities at the Craft Conf which brought back my childhood memories.

Dodgem

I love dodgem since my childhood and for decades I never sat in a dodgem car as I thought that was for kids. Last summer and also recently I had the opportunity to realize how enjoyable it is even for an adult. I was even able to persuade two of my friends to jump into a dodgem. It was really fun.

Mini Train

As I mentioned before, the conference took place at the Hungarian Railway Museum. They have built a mini railroad at the location on which people could sit. I did not try this activity, but I saw many of the participants sitting on it. I brought you a picture to help you imagine it.

Candy Floss

I loved candy floss as a kid and I realized I love candy floss as an adult too. Luckily there was a candy floss stand right beside Cloudera's stand so it was no question whether I tried it or not. Look at my happy face. 😊

VR game

There was a stand beside SAP where you could play Playstation games with a VR headset. As I had never tried it before, I took the opportunity. It was fun, especially as you had two handles in your hand with which you could interact with the virtual world instead of a mouse or a controller. As I learned, you can borrow these VR headsets if you have an event like a birthday party or want to have fun with your friends.

Final Thoughts

I would like to say thank you to Anna, Felhő bácsi, Médea, Károly, Barna, Vanda, Viktória, Anna, Renáta, Fanni, Bianka, Réka, Kata, Barbara, Veronika, Vivien, Marcel, Martin, Emilía, Kristóf, Gergő, László who are the people behind CraftHub the organizer of the Craft Conf. They made my first offline conference really memorable and I am pretty sure the organizers of my next conference will have a hard time outshining the Craft Conf 2022.

I would also say thank you to my friends Szabi, Fűrész, Karesz, and Laci who joined me personally for the time of the conference. I really enjoyed this 2 days and I just hope we can repeat it next year too.

As I am a test automation engineer it was no question I will listen to all the quality assurance related talks. My first pick is Fabrice Bernhard's talk called Dantotsu Radical Software Quality Improvement which definitely raised my curiosity with the unusual word Dantotsu and of course also with the promise of radically improving quality.

Fabrice Bernhard is the Co-Founder and Group CTO of Theodo a fast-growing custom digital software consultancy. They have adopted DevOps, Scrum, and lean and with their aid, they were able to grow from 10 to 600 people delivering great quality work despite the rapid growth.

The Dantotsu Book

In today's world where software is taking over basically everything, it is quite a big challenge to scale without sacrificing quality as Fabrice explained. One year ago a book by Sadao Nomura has been published with the title "The Toyota Way of Dantotsu Radical Quality Improvement" which immediately raised Fabrice's attention. His talk was about the Dantotsu method and how they adapted it for software development. Please let me share his talk in my own words.

Software is eating the world

As Marc Andreessen summarized in 2011: Software is eating the world. Starting around 20 years ago startups like Netflix, Amazon, and Airbnb disrupted whole sectors using software and this tendency is rising continuously many new players coming raising a huge amount of funds. This is of course good news for us software developers as a portion of that money will land in our pockets. It is good news for us up to the point that introducing bugs has very expensive consequences.

I think most of us heard about the Ariane 5 catastrophe. Does not sound familiar? What if I tell a rocket with 7 billion dollar development cost and 500 million dollar value exploded 40 seconds after its launch in 1996 due to an integer conversion error in a single line of code in which a 32-bit integer was passed to a function that expected a 16-bit integer.

The code which resulted in the catastrophe was responsible for the horizontal alignment of the rocket. Just a few lines above the bug the conversion for the vertical alignment was handled correctly, but for some reason, the developer(s) did not find it important to handle the same for the horizontal alignment.

When we are talking about hundreds of millions of dollars it is not surprising space industry has extreme quality processes. To mention an example adding 6000 lines of code for the GPS feature needed 2500 pages of specification and the 400k line of code for the whole system required 40000 pages of specifications which means one page of specification for 10 lines of code.

Like it or not software is everywhere nowadays, not just in your thermostat, coffee machine, and television but also in more mission-critical things like self-driving cars. Cause of this in many cases we need especially high-quality software as we are not only talking about money but even about human lives.

Unfortunately writing 4 pages of documentation for 10 lines of code is not really scalable, especially in our fast-paced agile world where you have to deliver value for your customer frequently.

On the other end of the scale there is the move fast and break things approach with which of course you can scale but you have to sacrifice quality in order to do that.

The software practices used for the shuttle produced one defect per 400k lines while the industry average based on studies is around 10-20 defects per 1k lines of code which means 5000 times more defects.

As both of the approaches has their downsides we need another approach and here comes Dantotsu into the picture.

The Dantotsu Method

The Dantotsu method has been developed by Sadao Nomura at Toyota. Toyota is well known for its high-quality standards and I think there are no software developers who have not heard about lean thinking which also originated from Toyota.

A Brief History of Dantotsu

I am pretty sure this part won't be as fun as in Fabrice's talk so I am keeping it short. Sadao Namura an executive at Toyota regularly visited each branch to understand the individual situations of those branches. As an outcome of the visits, he wrote an A3-sized paper about the problems and also about their countermeasures.

When he visited months later to his surprise he realized nothing has changed, so he gave them a similar A3-sized page and asked them to implement it this time, just to realize a few months later nothing has changed.

As Sadao realized it does not work this way he decided to make a major change in his policy and that was which lead to the birth of the Dantotsu Quality Activities.

The Method

First, let's see what are the key points of the Dantotsu method.

1. Visual quality management is highly emphasized. Tracking daily, and monthly defects on the vehicles visualized on a wall, not on a computer. And also tracking the ambitious goals on the monthly view.
2. Defects are classified by stages of outflow instead of priority. No defects should reach the customer, so they are focusing on how to detect that earlier in the flow. There are four categories of these defects as you can see in the below image. What is very important to mention is that they also classify based on the source of the defect determining whether it is coming from production engineering, from the supplier, from welding, ...
3. The team leader is highly involved in examining the product defect which is an 8-step procedure. The procedure's steps are:
   1. Team leader examines the defective part to identify the faulty process
   2. Team leader checks other parts in stocks for the same effect
   3. Team leader investigates the defect's cause through interviews with workers
   4. Team leader implements countermeasures
   5. Team leader reports on defect analysis and countermeasures during a daily meeting
   6. Team leader creates/improves standards and deploys horizontally to handle similar processes/items
   7. Team leader train workers
   8. Team leader checks if workers are performing according to standard throughout go and sees As you can see the team leader takes a significant part in all 8 steps. There is one more very important aspect of this procedure. The whole process is conducted in 24 hours. The first four steps happen during the first day and the other four happen during the next day.
4. Systematic defect analysis. They collect defect details, determine causes, and then define the required countermeasures. You can see an example below. At this point, Fabrice mention they had an ongoing debate in his team for years. The testing passionates said we could have avoided bugs by introducing more unit tests, and better end-to-end tests, and the other half of the group was of the opinion to design a better architecture, doing a better domain-driven design. Fabrice was more on the prevention side than on the testing side, but thanks to the Dantotsu book he realized the whole debate was wrong. They should do both of them.
5. Dantotsu invests in systems to leave no chance for defects to appear again. As soon as a defect appears two or three times they invest in systems that prevent the appearance of those bugs.

This was a short summary of the Dantotsu method. In order to get a better grasp on the method, it is highly recommended to read the book.

At this point you might think, it is great they found a method that can be used to radically improve quality in a factory but how can we apply it in software development. Please, keep on reading to find out as Fabrice gave an answer to that in the second part of his talk by telling what they did in order to implement the process.

Dantotsu and Software Development

The first thing that was done by his team was to standardize the definition of a defect. In the end, they agreed everything is a defect that was unexpected by the user.

Standardize the way the group measure bugs. They tried different approaches to measure the bugs they even tried it on paper as Sadao Namura emphasized you should not use a computer for that, but you should do it on paper/wall. This approach might work in a factory but in the era of remote work is not feasible, so they have built a tool with which they can track defects on different projects.

They have standardized their outflow classification by defining 5 groups:

1. A defects: Defects detected by developers
2. B defects: Defects detected by the team during code reviews or functional reviews
3. C defects: Defects detected during an inspection by PO or QA
4. D defects: Defects detected in production
5. E defects: Defects that generated a customer complaint

They also determined the source of the defects as you can see in the below diagram.

After defining the basics they went on by putting the Dantotsu method into practice. Their team lead became their tech lead whose responsibility was to analyze one bugfix a day.

The tech leads not just analyze the bugfix but if it is not clear who should fix it then the dev lead's responsibility is to fix it. After fixing the bug, all the information collected about it, even a screenshot of the code which fixed the bug. After that, the tech lead does a root cause analysis and defines the needed countermeasures. He/she analyzes how they could have detected it earlier and also how they could prevent it in the future. In terms of timing, the tech lead fixes the bug, analyzes the defect, checks other parts of the codebase for similar defects, and comes up with suggested countermeasures. During the next day, the tech lead shares his findings and the suggested countermeasures the next day during the daily bugfix analysis session. And during the next sprint, the team implements the countermeasures on which they agreed.

To mention a few examples of potential countermeasures:

• Creating Lint rules
• Adding tests
• Rewrite parts of the system
• Create or improve training material
• Train team members on identified skill gaps.

Fabrice mentioned they even experimented with A defects. They call a bug A defect when the code does not work as expected at the first manual test. They even gamified it. If your code works on the first try you get a "right the first time" award. They even have a Slack bot congratulating every time. It not just promotes the celebration of quality but also thinking before coding.

That was the summary of how you can use the Dantotsu method in your software development project. Before I close this article let me write a few words about the learnings Fabrice shared with us.

Learnings

1. Try to connect efforts better with the big picture: Putting so much effort at the defect level might result in losing the big picture. In order to avoid it, the team has a very good visual representation of the architecture on which they can map the defects to the architecture.
2. On large ongoing projects the result will take months: They have introduced the method on large ongoing projects and the sad reality is it might take several months to see the results. When they did root cause analysis there were cases when the root cause dated back 9 months.
3. They also have experience with a project which used the Dantotsu method right from the beginning. It is a small project with 5789 lines of code developed in 118 engineer days. They found 2 defects in production (D defect) and 2 defects in inspection (C defect) which means 0.3 defects in 1000 lines of code or 0.02 defects per engineer-day which is one order of magnitude better than what they saw in other projects.

To sum it up I found Fabrice's talk about how they implemented the Dantotsu method very fascinating. I really like the idea and I will definitely share this article with my team. We work on a much bigger project and I do not see much chance to have a dedicated person responsible for analyzing bugfixes and determining countermeasures daily, but having 1-2 sessions weekly by cherry-picking some of the bugs might be feasible. As Fabrice's project and their experiences are relatively fresh I am pretty curious about how their project evolved over time and I am sure Fabrice will share their learnings with us.

Preparation

Choose a Topic in Which You Are Interested

I would never write an article about a topic that does not make me enthusiastic. I do not recommend it to you either. I am pretty sure you could do it, but writing should be fun, and in case you are not enjoying you won't be happy with the result. In order to engage your readers, you have to be engaged with the topic too.

I love writing articles (however that was not always the case), and that is why I have selected this topic.

Choose One Topic Only

You can also use the Single Responsibility Principle(SRP) for articles. It is important to narrow down your scope and not write about many different topics in one article (except in case your goal is exactly to introduce many topics as a starter for an article series). It often happens that many related ideas pop into my mind which cannot fit into the current topic, in that case, I just save the ideas for later.

Have Specific Goals on Your Mind

Now you have the topic. It is a great start, but let's go one step further. Having the goal to share your knowledge is a great thing in itself, but be more specific. I like to set SMART goals. SMART is the acronym for:

• Specific
• Measurable
• Achievable
• Relevant

• Time-bound I won't explain it in detail, as others have already done it many times. Check for example this article if you are interested. So let's examine my goal:

• Specific: I would like to inspire others, to start writing articles, by providing all the necessary info to start this great journey of self-development. In addition, I would like to extend my audience.

• Measurable: In the case, that at least one person will write an article thanks to my post I will be happy. Measuring extending my audience is not that straightforward, but let's say get 10 more followers either on LinkedIn or on my blog.
• Achievable: I might be too optimistic, but I do believe I will achieve my goal.
• Relevant: I really enjoy writing articles and also reading good articles, so the more we have the better.
• Time-bound: My plan is to write at least one article every 2 weeks. So let's set a 2-week long timeframe to create my article. For reaching the goal it is harder because after reading my article somebody has to persuade him/herself to write one and they will also need at least 2 weeks. So I would say let's have one week after posting to have the 10 extra followers and 3 weeks more after that to have the first article. So in order to verify I achieved my goal, please let me know in case you write an article, I would really appreciate that. 😊

It is very useful to also have a higher-level goal, like publishing an article once a month. That will help you keep on track. My higher-level goal is to publish an article biweekly.

Find And Process Relevant Materials on The Topic

Even if you are familiar with the topic I recommend you to read/watch further to expand your knowledge on the subject, especially as you would like to give something valuable.

Instead of just getting the information try to analyze those materials using the points I will provide you in the next section. Are they following those ideas? Are they doing something better? What else can you take with you to help you write your own article?

To be honest, in this case, I did not use any extra material, I was building on my prior experience some of them are recent, and some of them are several years old.

Writing Basics

The Ugly First Draft

The "ugly first draft" term comes from Ann Hadley. The hardest part is to start writing. No matter how many words you have you should write them on your computer (or notebook if you prefer that). Maybe just one thought, a sentence, a paragraph, or whatever it is on your mind.

If you have something you can iterate on it. Extending the words to sentences. Sentences to paragraphs and paragraphs to chapters and in the end, you will arrive at the point when you have a complete article.

I have another good reason why I create the ugly first draft. I cannot keep too much thought in my head, but if I write them done, then I can start thinking about the follow-up. This method is extremely effective for me.

Choose The Right Title

I do not have to elaborate on how important the title is. In case you cannot catch the reader's attention, then they will simply scroll to the next article. You don't have to come up with the best title at the beginning. It is okay if you have a good enough one. I am pretty sure you will have great new ideas while you are writing the article.

I have chosen "How to write an article just about almost anything". It is quite generic, but I hope is still able to raise curiosity (even if some might will come with a negative attitude to see how miserably will I fail here).

Use Images

"One picture worth a thousand words." - it is even more true in today's information-overloaded world. Actually, this point should have come first, as it is more important than the title. Our brain processes visual information way faster than written text. By the time you read the title your brain most probably decided whether the info is relevant to you or not.

As the outcome of the above, I suggest always using a cover image. Ok, but what type of image should you use? As always, it depends. It depends on your audience. I do not recommend filling the article with pictures of half-naked women for example. It would surely draw lots of attention, but you have to catch the audience relevant for you.

The best is to use your own pictures, but in case that is not an option, I recommend using stock photos/graphics. Freepik is a great site where you can have unlimited image download for a few dollars a month, which can be more than enough for a couple of articles in case you think in advance. In order to cut, edit, and combine images, you can use the poor man's Photoshop Gimp. Joking apart, It is an awesome tool with more than enough features than you need.

You should use images inside your article too. Of course, you should not overdo it, and you should use images only relevant to your article. It happens very often that you need a diagram or chart. For that purpose, I use draw.io which is an awesome tool with lots of possibilities. You can save directly to GitHub, GitLab, Dropbox, and more.

For a cover image, I have chosen one of my favorite water droplet photos taken by myself a few years ago. It is personal, and colorful and hopefully, it also makes you think: What the heck is it? Is it a bottle in the water? Is it only water? Is it a real photo at all? It is a real photo indeed, no Photoshop was used except for what I needed to process the RAW image. In case you like the image you can find more on my Facebook page.

I also used 3 stock photos to represent each section.

Provide the Context

Tell the readers what you will write about, so they can decide whether they are really interested or not.

My title speaks for itself, so not much extra info is needed. And also it is a follow-up to a previous article on the topic.

Use Headings and Paragraphs

In order to make navigation easier, and make your article more understandable, you should use headings and instead of writing everything in one paragraph, you should separate your text logically. One thing is important. Do not use an H1 heading in your article as Hashnode uses H1 for the title and search engines do not like articles with multiple H1 headings.

As you can see this article is structured, having many headings and paragraphs.

Highlight Your Message

Personally, I prefer longer articles, but before reading them, I like to skim through to see if there is really something useful for me. Time is money, providing the important information easily available makes your reader's life easier. Cause of this I usually write the main takeaways in bold.

In case you read this article, you can get all the info in a few seconds. In case you are interested in the whys, then you will surely read the article, in case not, then why should we waste each others' time.

Try to Think With the Reader's Mind

Of course, everyone is different and has their own personal background but there is one common in them. They are interested in the topic you are writing about. Try to predict what questions will arise in their mind, and provide the answers to those questions. Or at least follow the next advice.

Provide Links for Readers to Further Deepen Their Knowledge

Of course, everyone can use google. A quite harsh joke about it is LMGTFY(Let Me Google That For You). In case you already researched the subject and have the best links then why should you not share it with your readers? It would be a waste of time not to do that.

However I did not use any study material for this article I still linked many tools, and pages that can be useful for you.

Use Spell-Checking Software

There is nothing more annoying than reading a text and bumping into spelling mistakes all the time. It gives a quite negative impression of you. I am not a native English speaker, so I have to be really careful not to make big mistakes.

I use Grammarly, which is available as a browser plugin and automatically offers corrections for most of my mistakes.

Do Not Repeat Yourself

It is not a good experience to read the same words and phrases all the time again, so try to not repeat yourself. Use synonyms, and different phrases to refer to the same thing. I highly recommend thesaurus.com to find synonyms and Grammarly can suggest alternatives right in your browser during writing. I still have to make myself use it more often. However it is an advanced topic, but even search engines prefer not to have the same phrase appearing again and again.

Ouch. You got me. I just wrote the word "again" twice (and now this is the third). Of course, that was a phrase that is completely okay to use. Apart from that, I tried to avoid repeating it.

Be Personal

I know some will disagree with me on this point, especially in case we are talking about technical stuff. But developers are also humans. They are not just technical people, they have feelings, humor, empathy, ...

Share some background information about yourself, an old story, or whatever you like. Show your humor. I am pretty sure not everyone will love it, but the good news is that it is completely fine. But whoever likes it will be much more engaged with you. They won't only read your articles because they are interested in the topic, but they will read them because they are written by you. It is the perfect opportunity to draw your audience's attention to different topics which might be relevant to them.

Nobody is perfect, everybody makes mistakes. I do not like the word "mistake", I prefer Robin Sharma's words:

There are no mistakes in life, only lessons. There is no such thing as a negative experience, only opportunities to grow, learn and advance along the road of self-mastery. From struggle comes strength. Even pain can be a wonderful teacher. Show you are not perfect and you are one of us humans. Tell the readers about your learned lessons. I am pretty sure it will be useful for many of them.

Of course, you should not overdo this, you should not post a picture of your dog or child in each article. Less is more in this case also.

I brought a personal image here, and also shared ways how I like working. I also put in some jokes that you might or might not notice. 😊

Do Not Leave Your Article Unfinished

You should close your article with either a summary or a conclusion. Without that, your reader will feel something is missing.

I did close my article with some encouraging words.

Get Reviewers

However I am not doing it at the moment, but in the past, I always asked for feedback from multiple people.

Whom should you ask for feedback? Again, it depends. It depends on your subject. In case you are writing about something non-technical as I do in this article, you can get almost anyone's opinion. But be careful as your family and friends will be biased towards you, despite this they can still provide valuable feedback. Ask them to point out parts that they especially loved, and also parts that were not that good, instead of asking "How do you like my article". For more specific topics it is best to have someone who has the domain knowledge, so asking your colleagues or other experts in the field would be the best option.

Whenever I wrote this article my plan was to ask my wife and some of my colleagues and friends to read this article and provide feedback before I post it, but months passed since I wrote the article and I decided to not ask for feedback about this article.

Give Time to Mature Your Article

It is often worth waiting a couple of days before you post your article. You can have new ideas, and you can get even more feedback. But do not wait too much. Release it, get feedback, learn from it and then write again and then repeat this cycle frequently. You will be surprised how much you improved in case you read one of your articles from several months ago. Developers have a saying for this: In case you look at your code after a few months, and you still think it is great, it only means you did not improve anything during those months. 😊

Well, I wrote this article around 3 months ago so I left way too much time to mature my article. I did this because I found more joy in writing other articles. But now I feel the time to publish this article.

You Cannot Fail

This is the last, but maybe the most important topic. I remember the time when I was learning Lindy Hop and I was afraid to go to a party to use my learnings in real life. Every miracle starts with the first step, which might be hard, but believe me, in case you want to improve, you have to USE what you have.

You might get negative comments, and feedback (however in case you are choosing the right reviewers or readers, they won't let you down, but suggest improvements), but use them for your own gain, consider them, and use what is useful and simply ignore the others.

Ready to Go

And that's all for now. I believe it is enough to jumpstart you on writing your first article. I am pretty sure there are a lot of other important factors which are relevant for you, but you can only find out them in case you start on this fun and valuable journey. I am sure you won't embarrass anybody (including yourself) in case you write your first article now.

As you can get used to it by now, I won't leave you here without any questions.

In case you are writing your first article: Which point from above gives you the biggest headache? I am happy to help in case you have stuck anywhere. Just post a comment or drop me a private message.

In case you are an experienced writer: What is your number one advice for newbies which is not listed here?

P.S: Support me by sharing this article if you like it👍

Hackernoon interviewed me, so if you would like to learn more about me, just click here and read it!

Become an agileish superhero!

Learn how to memorize anything in the world. In this series, I teach you everything I know about learning and memorization, including memory palaces, marker images, number memorization techniques, associations, etc.

You can already find the first videos on my Youtube channel in which I show you that it is possible to memorize such boring things as positions of circles.

Don't forget to read How You Can Become An Agileish Super Learner AKA How You Can Become A Super Thinker AKA The Proof Of Concept (POC) before you watch the videos.

Join the Agileish Superheroes Facebook group to learn memorization techniques, thinking techniques, agility, reading and learning techniques and also to get notified about new live sessions and videos

As I am a crazy person, I have open-sourced my life on GitHub on Fool's day.

I am sharing my thoughts, writings, and creations, and as I am frequently committing, I have open-sourced my thinking process, my writing process, and also my creation process.

Just click here to check my open-sourced life on Github!

My credo: The Mystery Of The Supposedly Red Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet

Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humor, and I am also happy to tell you that this is my article about which I am the proudest of now.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to, on Hackernoon and even on Instagram.

Of course, there were huge differences in terms of topic, readability, structure, and matureness in these articles, but there was one common in all of them:

They were not just able to grab my attention but also to keep it till the end of the article.

As I read the articles week by week many names started to appear again and again which made me curious. I wanted to know a little bit about the background of these great hloggers and I am pretty sure I am not the only one who would love to read about the creators of these excellent articles.

Hundreds of new articles appear on Hashnode each week cause of this it is very hard to stand out and reach the readers no matter how good are the articles we write.

I have learned about self-branding in the past and one of the main takeaway for me was the following:

If you would like to sell your product, no matter whether it is a photograph, a physical product, or an article in our case, it is not enough to have a quality product you have to make people interested in you.

Sharing personal stories, thoughts, or our everyday struggles will result in much more engagement from our readers as they realize we are also a human similar to them having the same everyday struggles as they have.

As my name Miklós means Claus and I also have a quite big belly, I decided to put my red hat on and become the secret Santa. From now on, I will approach bloggers of the Hashnode community and interview them regularly.

That's enough from the backstory, let's see who is the first Hashnode blogger. 😊

The Hlogger: Saroj Behera

If you read my Hashnode weekly articles, then you know I am not really into blockchain and crypto, still, I decided to make the first interview with Saroje Behera who is writing harticles about the blockchain.

I am not into blockchain and crypto so much that I have bought Team Fortress 2 keys for 17 bitcoin several years ago when bitcoin was not really known to the public.

Such an idiot, I guess that is what you think now. Still, I have no nightmares about that and can talk about it without having any bad feelings.

Blockchain is much more than crypto and being a beginner in the field Saroj Behera's article can help you to understand the fundamentals of blockchain technology.

Dear reader, please welcome Saroj Behera.

The Interview

Hello, Saroj! Let's start! Can you tell us a few words about your childhood? Where did you come from? How was your life before you became a software engineer?

Well, My childhood is very different from what I am today. :) I was born in district Angul in Odisha state, India. In my family, I am the elder son, including my younger sister we are 4 members. I was very distracted and always used to roam outside, enjoying and chilling In my childhood. Till the 12th standard, I studied in a private school. After 12th I got interested in computer science. Then I joined city govt college for the degree course. After that again I did my Master in Computer Application(MCA) at a private university in Bhubaneswar, Odisha.

From MCA until now, I am doing my professional career in Software Industry.

What was your first memorable moment related to your profession?

Yepp! It's interesting. When I used to learn first time coding, my trainer used to give me tasks every day. And I was not able to complete those on time. I used to forget all things.

Then I asked my mentor, and then he suggested trying the Forgetting Curve methods while learning new skills. After applying these methods, I completed all tasks on time.

Can you tell me a little bit about what your job entails? What does the day-to-day look like?

As you know, I work for Maveric Systems Limited, Bangalore, India as a Software Engineer. In Maveric, I used to work on different tech stacks like JavaScript, Node, React, etc.

My day starts with a coffee and looking through what I have to do for the day. I always make a list one day earlier. My team mainly used Jira as a ticketing system, and we have sprints.

A sprint will be a week or two. In that amount of time, I need to complete my given work to be on track with my goal. Then it comes to coding! While doing code, I always care about the test cases, code quality, and other essential factors.

Every day we used to have a stand-up meeting with my team to learn about how the project was going on and what issues are facing like that.

What was your worst moment related to your profession?

Eight months back, one day, I got an outside project. I accepted it and started working on it. My friend and I used to do that project. I handled the frontend part, and the friend is the backend part. On the day of our first demo, my friend's PC got some windows problem, and it was formatted. That day I am remembering, I was blank. Somehow I convinced the client, and we postponed it to a new date.

What was your best moment related to your profession?

Well, best moment! Once in my previous organization there is an issue with some AWS authentication logic, 2 developers were tried for 4-5 days. After that, my manager gave me that task, then luckily I did it in 1 day. That was one of the best moments in my professional life.

Do you think a degree is required to be a software engineer these days?

Great question! If you know the skills, there is no need for a degree. Of course, you should be good at logic building and a great problem solver. Yaa, the degree also matters. If anyone is looking for a degree that can help to get a job in software, then I will be recommended for Software engineering or computer science.

Also, just a degree won’t get you the job. With a degree, you must also have the skills and programming languages like Java, C, C++, etc.

Again, the most important is your passion. If you are passionate about software engineering, then only you can deliver the work. You won’t succeed without a great passion. Passion for learning new skills, passion for having patience, and passion for exploring new tech.

Please tell me 7 things you would like to share about yourself!

7 things! It’s interesting. Well, firstly, I can say I am passionate about programming. Every day I try to write something.

Second, I always believe in myself. I think if we imagine one thing, then we can achieve it. We need hard work and focus.

Third, I love to read books, any books that may be technical, self-help, or any story. I love to read. I believe every day we should read something. I called it brain exercise.

Fourth, I can't say NO.

Fifth, I love to stay with my parents and family. I believe work can be done anywhere if we know the right skills.

Sixth, I have a shallow friend circle. We will be the average of 5 people around us, that’s why I always choose the right people.

Last, my long-term goal is to make a charity where I can give free education to the needy.

That’s all my 7 things!

Do you have a specific area of interest?

Thanks for this question. I am always a learner. Every day I try to learn something new that can help my career. Currently, I am exploring blockchain and its applications. I think you already know what blockchain is. Blockchain is a great technology that may change the future.

How do you think blockchain will change the future?

Well, blockchain is an open, distributed ledger that can record transactions between two parties efficiently and in a verifiable and permanent way. It works on the decentralized network model. It means, that both data and functionality(business logic) of an application reside on multiple servers that are not owned and managed by a single entity.

With the help of this, we can build great applications. Currently, maximum applications work on central databases, where our data are not safe. But in blockchain, there is no single authority that controls our data. It works on a peer-to-peer network, where every peer acts as a server. Blockchain is immutable, which means any new data added to the blockchain network is permanent, and no one can modify or delete it. In this way, blockchain will help you to build robust apps.

Interesting! As far as I know, you are not just learning about blockchain, but you also share your knowledge with the community. Where can our readers find your writings?

Yes, I have a blog; you can find it here on Hashnode, and you can also read me on medium.

Here I write articles about blockchain and other crypto-related topics.

Can you share some insights about how you write your articles?

It was a kind of new habit for me. Till 2021 November I never ever wrote even a single article. At that time I used to train under one mentor on an online platform. He was a kind of writer also. He motivated me a lot in this new world.

After that, I tried writing one article, and luckily I got a huge response, but then I never stopped.

Normally I used to write articles on Blockchain-related domains. I believe Blockchain is a future technology.

Do you have some advice for new or wannabe bloggers?

Yes, I will advise new bloggers like, they must focus on one category like I am focusing only on blockchain-related. The also most important thing is consistency, at least try to write one article in a week and keep doing it. That's it.

Why do you like Hashnode?

Well, I like hashnode. Because it is mostly for software professionals. Also in the Hashnode, I can find great articles every day. I love the hashnode UI and personal blog domain feature.

Yepp! I also used to write articles on different platforms, but mostly I used hashnode!

Cool. Do you have a favorite fictional character? Why he/she/it is your favorite?

I believe in Ankur Warikoo. Ankur is an Indian author, investor, and businessperson. I always follow him.

Who is your favorite real-life idol? Why?

My Mother! She is working as a school teacher. Also, she always cooks for us, not only cooks but all other minor work. She is always my real-life idol.

Do you play video games? What do you do in your free time?

Interesting. I very rarely play these types of games. Instead, I love to read books in my free time and always try to learn new skills so that they will help in my professional career.

Thank you, Saroj. It was a pleasure to talk to you. Do you have any message or some closing words for our readers?

For readers, I will always say one thing, focus on your goal, and love what you are doing, always keep trying till the work is done.

Also thanks to you Miki, for giving your time to me for this great interview. it was one type of great moment for me. I hope I'll meet soon with you :)

Dear readers. Thank you for taking the time to read Saroj Behera's interview. You can follow him on Hashnode, on LinkedIn, and also on Twitter if you do not want to miss his posts.

P.S.: Something Good Will Happen To You Today!

Today in The Spotlight 🔦: Creator, Curator, Commentator, or Connector from Arvid Kahl

I have read a very insightful article from Arvid Kahl, which made me think about myself. In his article Choose Your Own Adventure: Creator, Curator, Commentator, or Connector, Arvid mentions four boxes into which you can be put on social media: Creator, Curator, Commentator, or Connector.

In short, you are a Creator if you create content. You are a Curator if you collect and share other people's content. You are a Commentator if you pick other people's content and talk about that. And finally, if you create and "manage" communities, you are a connector.

You can be in multiple boxes at the same time. I thought about this for a while, and I came up with the following values: 25% 10% 10% 20% 35%

I am writing articles. That is why I am 25% creator. I am posting the Hashnode Randomly from time to time, so I am a 10% curator. I often comment on others' articles sharing my relevant e[xperience there. I am building multiple online communities (Selenide User Group, Agileish Superheroes, so I am a connector too.

Yes, there is a fifth number too, but I won't tell you what it is as I want you to read the article, as it is worth every minute you spend on it.

Software Development

• Do you know what are progressive web apps? I have to admit I did not hear about them until last week. Vinay Krishnan gives a great intro about progressive web apps in his writing Progressive Web Apps: An introduction.
• yaox023 explains pretty well how token based authentication works.
• Are you interested in web scraping? Nicolae Rotaru explains how you can use Page2API API to scrape Reddit in his writing How to Scrape Reddit Data: Posts, Images, Comments, and more..
• Saumya Ranjan Nayak collected a list of advice on how you can advance from a coder to a software engineer in his article How to Become a Software Engineer from a Coder ?. However, he is talking about the technical side. It is equally important to improve your soft skills if you really want to become a good software developer.
• Have you ever wondered how you can build scalable and secure web applications in Python? Ashutosh Krishna gives an intro about the Flask microframework in his post Getting Started With Flask.
• Writing clean code is a must-have skill that should be learned by every software developer. It is highly advised to follow the SOLID principles whenever you write code. Ashraf Mohamed explains the dependency inversion principle in his post S.O.L.I.D Principles: Dependency Inversion Principle..
• Almost every company is moving towards becoming agile nowadays, but it is very easy to do it the wrong way. Ganesh Pilli collected some pitfalls with which a leader can mess with Agile. I also added my thoughts in the comment section.
• Being a software developer has its challenges. Brock Herion gives some advice based on his experience about the topic in his writing Things about software development I wish somebody had told me.
• Maxi Contieri continued his extremely helpful series about code smells. It is unbelievable, but he just posted Code Smell 135 - Interfaces With just One Realization, which is the 135th element of his series.
• Are you learning Python? Do you like the Hangman game? Just read Ashutosh Krishna's Hangman Game using Python article.
• Have you ever struggled with solving a problem? Saptarshi Sarkar gives you valuable advice in his How to Improve Logic Building Skills in Programming article.
• Rakesh Potnuru introduced a new solution with which you can incentivize open-source contribution in his Taking Open Source contributions and communities to next level with the Reward System post. I also did something similar with the Selenideium Element Inspector Bounty Hunting Reward program.
• Joseph Perez was a Twitch streamer and also managed a cheese store. I think that is enough info to convince you to read his story My Experience Of Becoming A Software Engineer.
• Caroline participated in the Craft Conf giveaway and won a ticket for the Craft Conf. She participated with her Five Basics Of Web Development For Beginners: "AKA Craft Conf Giveaway Participation" article.

Testing

• Sérgio Martins posts are worth reading if you are a tester or a test automation engineer. His latest post that I read was Five C's of a Test Engineer, but you can find much more valuable content on his blog.
• If you would like to test APIs, then Tiffany Lewis's Top 5 API Testing Tools For 2022 And Beyond article is highly recommended. I also recommend checking Karate DSL, which is my number one favorite for API automation.
• Have you ever heard about DevTestOps? I have to admit I heard about it the first time in KMS Solutions Blog's What is DevTestOps and how can it transform Agile? article.

Data analysis, Artificial Intelligence

• Do you know what is a serverless service? Well, I had no idea before I read Austen Collins's Deploying PyTorch Model as a Serverless Service article.
• keerthi reddy gives advice on what kind of data science project you should work on in order to make your portfolio more appealing in his Topmost data science project to add to your portfolio in 2022 harticle.
• Do you know what is topic modelling? I had no idea, but luckily we can learn it from Neurotech Africa's Get Started With Topic Modelling Using Gensim In Nlp harticle.

Networks

• Dev Valecha clearly explains what is load balancing in his post Understanding Load Balancing!! (NGINX) ft. Jethalal..

Productivity, Self-Improvement, Psychology, Soft-skills

• Did you know we develop an opinion about a person in 3 seconds? Do you also put people in boxes? moalsare33's Why We Misjudge People All the Time is definitely a good read on the topic.
• "Some people in society do not need power, they don’t need status, they don’t need, but they want someone who can work with them, who can show them the right path." This quote is from FARZANA bano short but valuable harticle called Topic: How do you use your voice to positively impact yourself and your community?. Just check it if I made you curious.
• I loved Loran L's Internal dialogue of a procrastinator harticle as he was also using a conversational style and also because I am also often a procrastinator. Luckily Meadline joined my team, so she makes sure everything will be delivered on time.
• The imposter syndrome affects many of us developers. I believe it is more common in the tech community as we have to keep face with the constantly uprising new technologies year by year and month by month. Despite this, imposter syndrome is still taboo in many places. Luckily saningo lekalantula toom the courage and gave also ideas on how you can deal with imposter syndrome.
• Nik F P introduces 5 phases of management in his very interesting Soft Skills checkup: The many phases of Managing harticle.

Blogging, SEO

• Alexander Richterich gives some advice on How should I write my first post ⁉. I also wrote a post about the topic months ago, but I did not post it yet. Maybe the time is here to share my experiences too.
• Frank Elda talks about SEO in his writing SEO for Medium writers: get more views on your articles!. It is definitely worth reading even if you are not using medium, but instead, you use your own domain with Hashnode.

Blockchain

• Have you heard about NFTs? Jamie V. talks about them in his writing NFTs - Disrupting technology or hype?.

Inspiring Stories

• Damilola Abiola is a product manager who had lots of struggles in her life, and she is brave enough to share them with us in her writing Product Manager Diaries #1. I really appreciate it.
• Julia Furst Morgado, similarly to many of us, have to learn new things while she has a full-time job. I have to admit it is very challenging to do that. However, she gives advice on how to code when you have a full-time job, her advice is equally valuable no matter what you are learning. Balancing a full-time job while learning to code
• "On days when I feel discouraged, being grateful regardless helps me to persevere and carry on without letting the false thoughts of unworthiness hinder me from pursuing my purpose in life." quote is from Eula Chua's An Attitude of Gratitude and Exam Preparation harticle. Definitely worth reading if you need a little motivation.

Tools and Resources

• Are you planning to create a website? If you are just interested in colors, then Suraj Vishwakarma's 5 Color Inspiration Website You Should Bookmark is definitely for you.

Non-Technical Articles

• I was innocently browsing through the technical articles here on Hashnode when the picture of a yummy Beans on Toast appeared in front of me. I think I do not have to say I became hungry immediately. Sandra shared the recipe in her Beans on Toast Recipe – How to Make it Perfect? writing.
• Do you play Backgammon? Do you know how ancient it is? Just read baccaratsite top's Origin of Backgammon article to learn about this game.
• Believe it or not, you can read tractor reviews on Hashnode. Just check Mukesh Gupta's Powertrac Tractor Price, Features, and Specifications- Khetigaadi article.

Newcomers

• Phillip Cooper is a developer with more than a decade of experience and many ideas. He has decided to share them in the form of blog posts. You can read his first harticle here: Beginnings...
• Puleeno Nguyen will write about WordPress and ReactJS. He was a little bit short on words, but you can still check his first post Hello Hash node.
• However, KaguraTart wrote a longer sentence in her first post Hello World!, I still do not know what she will write about. Follow her if you are interested.
• The same applies to Zubaydullo Abdirakhmonov's first article called Hello world!.
• Kyle Yu will record his programming-related learnings on his blog. Here you can find another Hello world article: Hello World.
• Việt Dũng has been working for five years in the field of SAP HCM in Vietnam. Read his first post if you would like to know what we can expect from him. You can find it here: Hello world~
• Aditya Rizki Pratama is an Indonesian kid who loves backend development, so that we can expect articles about that. You can find his first post here: Hello, it's Aditya Here

• Shivaditya Shivganesh just started blogging similarly to the others. I asked him what he would write about, but no answer had arrived yet. You can still check the first post here: Hello World

• Minnie: Despite keeping it short, it is still a lot of great list of harticles.

• Miki: Yes, I think so.
• Minnie: Where is the teaser trailer.
• Miki: Wait for it. It will come.
• McMuck: Here comes the part where we ask our readers to support us.

• Miki: You are right.

• Maudience: Dear Readers! As you might already know, Miki needs coffee not just to produce code but also for writing articles. He even hired our illustrator illustratoth to create a nice buy me a coffee image. So please support him with a few coffees if possible.

• McMuck: Where is the logo?
• Miki: We have to commit it to Github to make it live forever.
• McMuck: Ummm. Okayish. Whatever you want, just get the money.

Hackernoon interviewed me, so if you would like to learn more about me, just click here and read it!

Become an agileish superhero!

Learn how to memorize anything in the world. In this series, I teach you everything I know about learning and memorization, including memory palaces, marker images, number memorization techniques, associations, etc.

You can already find the first videos on my Youtube channel in which I show you that it is possible to memorize such boring things as positions of circles.

Don't forget to read How You Can Become An Agileish Super Learner AKA How You Can Become A Super Thinker AKA The Proof Of Concept (POC) before you watch the videos.

Join the Agileish Superheroes Facebook group to learn memorization techniques, thinking techniques, agility, reading and learning techniques and also to get notified about new live sessions and videos

• Minnie: Are we there yet?
• Miki: No, it is still the call to action section.
• Minnie: I can't wait to see it.

As I am a crazy person, I have open-sourced my life on GitHub on Fool's day.

I am sharing my thoughts, writings, and creations, and as I am frequently committing, I have open-sourced my thinking process, my writing process, and also my creation process.

Just click here to check my open-sourced life on Github!

• Minnie: And now?
• Miki: Almost, Minnie. Almost.

My credo: The Mystery Of The Supposedly Red Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet

Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humor, and I am also happy to tell you that this is my article about which I am the proudest of now.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to, on Hackernoon and even on Instagram.

• Minnie: And now?
• Miki: We are there finally.
• Minnie: So what is the teaser?
• Miki: An upcoming article series.
• Minnie: Really? About what?
• Miki: I cannot tell, but I can say similarly to Hashnode weekly, it will also be related to Hashnode.
• Minnie: Cool. I want to see it now.
• Miki: Well, it is almost ready so that you can read it.
• Minnie: Cool.

P.S.: Something good will happen to you today!

Tableish Contentish

1. Nikolai: If you do not give a sh.t about what Miki was doing during the last two months and you are only here for your weekly dose of harticles, just click here!
2. If you want to know what harticles Miki wrote since he posted the last Hashnode weekly, then click here!
3. If you would like to become a super learner, thinker, or have a super memory just click here!
4. Do you want to know how Miki open-sourced himslef? Click here!
5. Want to read the interview Miki gave to Hackernoon? Read it here!
6. If you want to know how you can get access to your brain from your code for the price of a mid-level mobile phone, or if you want to know with which article Miki is participating in the Hashnode Writeathon Click here!
7. Do you want to win a ticket to Craft Conf 2022, which is one of the world's biggest software developer conferences? Click here for details!

What has happened in the last two months?

• Minnie: Yuppie. I can't believe it. Another Hashnode Weekly. Finally.
• Miki: Yeah, I am also happy about that.
• Minnie: What happened? Why didn't you post for two months?
• Miki: You know, I read 80-100 articles weekly and I realized I could not focus on other things if I am reading so much. I also burnt out on reading a little bit, so luckily I stopped.
• Minnie: Luckily?
• Miki: Luckily.
• Minnie: Why?
• Miki: As I had time to be creative and focus on other topics too.
• Minnie: So what did you do in the last 2 months?

  Writing 9 Harticles

• Miki: Well. Let's see. I have written 9 articles:
  • How To Customize Your LinkedIn URL in 6 Easy Steps AKA How To Boost Your LinkedIn SEO AKA Lifehacks By Miki Szeles
  • How you can find a job in one round of interview? AKA Perfectish Matchish Partnerish Opportunityish From Developerishish AKA The Great Refactoring.MD
  • How You Can Become An Agileish Super Learner AKA How You Can Become A Super Thinker AKA The Proof Of Concept (POC)
  • How to Improve Your Memory With Exponential Speed AKA How You Can Become An Agileish Superhero AKA Sprint 0003
  • To Test, or Not to Test, That is Not The Question Reloaded - AKA Why You Should Replace Your Automated Tests With Manual Tests
  • Do You Want to Learn Software Development From Top-Notch Experts From All Around The World? Here is Your Chance! AKA The Craft Conf Giveaway
  • Breaking News! The Craft Conf Giveaway Submission Deadline Has Been Extended by a Week!
  • A Brainwave Based Solution With Which Completely Paralyzed People Can Communicate With Their Loved Ones Using a Muse EEG Band
  • Why Am I Attending The Craft Conf 2022 Software Development Conference?
• Nikolai: 9 articles in 9 weeks? Such a loser. Earlier, you posted daily.
• Miki: Well, you are partially right, but 4 of them are above 20 minutes read time and 2 of them above 30 minutes.
• Nikolai: You are crazy, nobody will read them.
• Miki: Well, I might be a little bit crazy, but I have employed Maudience to make sure we can keep (the attention of) our audience and make sure they can get the most out of our articles if they do not have 10+ minutes.
• Nikolai: Does that work?
• Miki: We will see. We will see, Nikolai!
• Nikolai: So that's all that you did in the last two months?
• Miki: Nope. I have worked in my full-time job as a test automation engineer and also spent a lot of time with my son, Levi.
• Minnie: Yes, family time is very important. The most important one is from all the mentioned things. I will make sure you will never lose focus on that.
• Miki: Thanks, Minnie. Return to tableish contentish!

  Helping You to Rediscover Your Inner Superhero

• Nikolai: I am still not impressed with what you did. Is there anything else?
• Miki: Yes. I have learned many many memorization, learning, and thinking methods during the last three decades of my life.
• Nikolai: I know. None of them stuck, you gave up using them after a short while.
• Miki: None of them worked up till recently as suddenly everything started to work.
• Nikolai: How is that possible?
• Miki: I have employed Metro.
• Nikolai: Who is he?
• Miki: He is our Scrum master responsible for retros.
• Nikolai: Ah, so he helps with your full-time job?
• Miki: No, he helps in almost everything that I am doing in my life?
• Nikolai: Whaaaaat?
• Miki: No matter what I am doing, I am doing it in short 15min-3 hours iterations. I do them up till the flow remains.
• Nikolai: How is that helpful?
• Miki: I have a retrospective after each session.
• Nikolai: A retro what?
• Miki: Retrospective comes from Scrum. After each sprint, the team gathers and creates a list of what went wrong, what went well, and what will they do differently.
• Nikolai: I still do not get it.
• Miki: Just read this article and you will understand.
  
  
• Maudience: So, I am happy you improved your memory and thinking process, but how can our readers benefit from that.
• Miki: I have started a live memorization series in which I show the power of the different memorization techniques by combining them, thinking aloud, and involving my audience in the memorization, so they can not just see how they can use it, but they get hands-on experience in them immediately.
• Minnie: What if somebody was not able to participate?
• Miki: I am uploading all my recordings to Youtube. Just click here to watch them.
• Minnie: What the hell was that?
• Miki: Ups. Sorry. Wrong link. Here is the correct link.
• Minnie: What if people would like to ask questions and get involved in conversations about memorization, learning, and thinking?
• Miki: They can join my Facebook group called Agileish Szuperhősök.
• Minnie: What if they do not speak Hungarian?
• Miki: Then they can join my English Facebook group called Agileish Superheroes. Return to tableish contentish!

  Open-sourcing myself

• Minnie: That's enough about memorization and learning. Have you done anything else in the last two months?
• Miki: Sure. As you know, I am a crazy person. I have open-sourced myself on Fool's day.
• Minnie: Whaaat?
• Miki: I open-sourced my thoughts, writings, and artistic creations, and as I am doing it on Github, I also open-sourced my thinking process, my writing process, and my art creation process thanks to the commit history.
• Minnie: Hmm. I have not heard of anyone else who did that.
• Miki: Me neither.
• Minnie: Is there anything else important about this?
• Miki: I believe this will be the first project on GitHub where people will go to read the comments instead of the content itself.
• Minnie: ???
• Miki: As in all the comments messages, I am talking with you, Minnie, Nikolai, and all the others.
• Minnie: Cool.
• Nikolai: You are an idiot, Miki.
• Miki: Thank you, my friend.
• Minnie: Where is the project?
• Miki: Just click here and you will find it!
• Minnie: Can they find this article there too?
• Miki: Sure. Unfortunately, I messed up the naming of the file, and you cannot read back all the comments except if you go to the project's commit history, but still you can find this harticle here. Return to tableish contentish!

  Giving an Interview to Hackernoon

• Minnie: What else you did do?
• Miki: I gave an interview to Hackernoon.
• Minnie: I know that. Here is the link!
• Miki: Thanks, Minnie. Return to tableish contentish!

  Developing a mind-controlled app and participating in Hashnode Writeathon

• Neveloper: Any programming related?
• Miki: Sure. I have developed an open-source brainwave-based app with which paralyzed people can communicate with their loved ones using a Muse EEG device.
• Neveloper: Finally. I wanted to learn Python for quite a while.
• Maudience: How can our readers learn more about the project?
• Miki: I have written an article about it with which I am also participating in the Hashnode Writeathon. Just click here to read it! Return to tableish contentish!

  Starting a Craft Conf Giveaway

• Nikolai: Ok, I am pretty sure you cannot come up with any other stuff.
• Miki: Are you sure?
• Nikolai: Yes, I am sure Miki.
• Miki: Well, then you are wrong. I have started a Craft Conf conference ticket giveaway.
• Nikolai: Craft conf? Never heard of it.
• Neveloper: It is because you have no idea about conferences and software engineering. Craft Conf is one of the biggest software development conferences in the world, featuring 70+ top-notch experts' talks. 1000+ developers take part each year.
• Maudience: How can our readers participate in this?
• Miki: They have to write an article about anything. Just click here to read the rules!
• Maudience: But Miki, the deadline is the 25th of May, which is very close.
• Miki: That is true, but they can even participate with an article they have written before up till the 11th of May, the start of the giveaway. They just have to follow the rules.
• Maudience: So, basically any of the articles mentioned in this newsletter can participate in this, right?
• Miki: Right, they just have to follow the link above and read the rules.
• Nikolai: A 399€ ticket for something which our readers would do anyway? Where is the catch?
• Miki: The winners have to write a 1000 words article after the conference about the conference.
• Nikolai: I knew it. Nobody will participate.
• Miki: We will see. Most of the fellow hloggers would write an article anyway about it if they participate.
  
  
• Minnie: There is one thing I do not understand. If you do so many things, why do you reboot Hashnode Weekly?
• Miki: As I realized, I love writing it, and I do believe it is valuable for our readers.

Return to tableish contentish!

Your Weekly Dose of Harticles

Today in Spotlight 🔦: Being a Dabbler by Jamie V.

As you might get used to it I always put one article in the spotlight, usually an article with which I can highly relate.

This week it is Jamie V.'s The Power of the "Dabbler" article. According to Jamie, he was a Dabbler during his whole life. He shares his thoughts about being a dabbler in his article. It is a must-read in my opinion.

I can highly relate to this as I am a dabbler myself too. In the past, I have started a lot of new things. Just to mention a few examples: playing poker, becoming a barista, playing go, photography, running, Lindy Hop, and creating a Facebook group. When I start something, I put 100% into it, which has usually resulted in burnout after a few weeks, months, or years.

No matter what, sooner or later, I lost my interest and gave up on them. I have considered this a bad thing for decades, up till recently.

Today I see this from a completely different perspective. I believe all of those experiences were valuable. There are many topics on which I gave up, but still, all of them helped me to become the person I am now. And from time to time, I move back to a topic like I am photographing and playing go again.

The above-mentioned topics are seemingly unrelated, but as I am always looking for ways to combine my previous learnings, I usually find a way that might result in something unique.

If you read what have I done during the last two months, you could see I have started many completely different topics.

Will I give up some of them?

I am almost sure. I have my limits, and I cannot handle as many things in parallel.

Will I give up all of them?

I doubt it. As I am doing many things in parallel, I believe I can make sure I won't burn out this time.

Which topics will I continue?

I will continue those ones in which I find the most joy, which is usually the topic that gives the most value to my followers.

Before we continue, my friend DjMic is here to play some music that you can listen to during reading.

• Miki: DjMic! What do you have for us today?
• DjMic: I know, Miki, you love pirates. You played with the iconic Pirates both on C64 and PC. You also played Port Royale, Sea of Thieves, and you live Pirates of The Caribbean too. So here is some music from the world-class Hungarian band Paddy And The Rats. Click here and start listening.

And now let's see this week's harticles:

Software Development

• Do you want to learn how you can build a complete Spring-based project from requirements up to containerization? Read marinsborg's excellent article called [URL shortener - Java and Spring complete tutorial].(https://marinsborg.hashnode.dev/url-shortener-java-and-spring-complete-tutorial)!
• Maxi Contieri is doing an awesome job as he does not just collect code smells but also gives the solution for them. He just posted the 133rd!!!! article in his series: Code Smell 133 - Hardcoded IF Conditions
• I do not know anything about Kotlin, so when I saw Vincent Tsen's How to Create Singleton Class in Kotlin? harticle I felt the urge to read it, especially as I could learn about Kotlin via an example with which I am quite familiar: the Singleton design pattern.
• You can learn the ins and outs of pseudocode from Mfon.'s What You Need to Know About Pseudocode article. I have seen way too much pseudo-code during my university years, but if you are not familiar with it, then this article is highly recommended.
• Do you want to read an inspiring story about how a woman with a tourism background became a software developer? Just read Eleanor Opiyo's Making the big switch to Software development harticle.
• Do you want more motivation to become a software developer? Read Souvik Das's My journey of becoming a developer harticle.
• Eden AI explains what is OCR, how it works, and what kind of solutions are there on the market, and he even provides an example in Javascript in his How to use OCR with JavaScript? post.
• If you are also not familiar with CSS then Ravi Kumar's The CSS Box Model is must-read. Ravi explains the CSS box model in an easily understandable way.
• Are you new to Git or GitHub? Read Ishita Keshawani's Learn Git and Github in 5 minutes harticle to jumpstart your git learning.
• I usually do not like "which is the best" articles as they are biased in most cases. Still, I read idukpaye Alex's harticle Which Frontend Javascript Framework/library is the Best?, and I did not regret it.
• Have you ever used a listener in your code? Then most probably, you used the Observer design pattern even without noticing it. Learn about the pattern from Abdulrhman Elsaed by reading his The Observer Pattern harticle.
• I do not know any other profession which has so many controversial topics as software development. It is possible it is because I am not familiar with other professions, but still Joel Tanzi was able to list five oddly controversial topics in software development. I even added one more, the "feature vs. bug" never-ending debate.
• Have you ever tried to automatically collect data from websites? Was it slow? If yes, then reading Ander Rodriguez's Speed Up Web Scraping with Concurrency in Python article is highly recommended.
• BeautifulSoup is a Python library for scraping the web. You can learn more about it by reading Ndongmo christian's WebScraping(BeautifulSoup) with Python harticle.
• Are you struggling with drawing diagrams? Just read Allen Helton's Solutions Architect Tips: How to Build Your First Architecture Diagram, and you won't feel overwhelmed when you have to draw a diagram next time.
• News API is a paid REST API based service with which you can get access to more than 5000 news sources to aid your business intelligence or monitor your company's news appearance and also your competitor's. You can learn more about it in Rajat Thakur's News API: Ultimate Beginner’s guide.
• Are you relatively new to Python like me? Do you have to use some resources like files? Is it cumbersome to make sure you always close the resources? Vojko Pribudić introducing Python context managers which are quite similar to Java's try with resource solution.
• Have you ever played Chrome's dino game? Do you want to have unlimited lives? Francis Faniku shows you how to hack the Chrome dino game
• Are you programming in JavaScript? Is it often cumbersome and error-prone to work with it? dev_avocado switched to TypeScript to overcome this problem.
• Are you new to programming? Do you want to learn another programming language?Ana Vela provides useful advice on how to do that.
• Have you ever wondered how search engines can find the right results even if you mistyped something? Levenshtein distance is the answer for you. Just read Ary Hegde's How to suggest similar words in Javascript using Levenshtein distance? article to find out the details.

Testing

• Testing articles are a scarce resource on Hashnode, so I am always happy if I read an article about testing from a fellow hlogger. Knowing the fundamentals of testing is a must if you would like to become a good tester. Do you want to learn what is white box and black box testing? Just read Matheus Gomes's Black box testing and White box testing harticle.
• Eric Ampire introduced an interesting concept called property-based testing in his harticle Create Powerful Tests using Property Based Testing. After reading it, I was not convinced about its usefulness, so I asked him some questions. I hope he will answer soon. I am pretty curious what do you think about this approach?

Writing, Blogging, Groth-hacking

• Are you struggling with making a passive income via writing? Me too. A fellow Hungarian Ákos Kőműves gave some tips in his writing Make your First Dollar online as a Creator.
• Do you want to have more Twitter followers? Get tips from Abel , who has accumulated 16k followers in 2 months: How I grew my Twitter audience to 16,000 in less than 2 months!

Self-improvement, Productivity, Psychology, Learning

• Self-reflection is a crucial part of my life, especially since Metro, who is our Scrum Master responsible for the retro, joined our team. It can highly boost your motivation if you summarize what went well from time to time. James 'Dante' Midzi asks one of the best motivation booster questions What Was Your Win This Week?.
• Do you also find it hard to keep your mental health in today's fast-paced world? Just read Linda Smith's How to Improve your Mental Health harticle in which she gives some advice.
• If you read the first section of my article, you already know I am obsessed with learning. Alejandro Napoles provides great advice on how to improve your learning in hos harticle called How to learn better with proven techniques.
• Amokrane Chentir's Solving problems through writing is short but still valuable writing.
• Is it hard for you to keep focus and achieve your goals? SURYA L provides his advice in How can you focus on your goals to achieve success?.
• Soft skills are as important as hard skills in today's world, and I am pretty sure soft skills will be even more important in the near future when AI-based programmers like Google's AlphaCode will take over coding from us. Precious Eyoh lists a list of skills that are important for a software developer in his Some Important Skills need as a Software Engineer post.

Machine Learning, Data Analysis, and Artificial Intelligence

• İlke Candan Bengi helps us to put our feet in the field of machine learning by introducing decision trees with hands-on examples in her writing Learning and Predicting, Machine Learning.
• From Neurotech Africa, you can learn how to do your sentiment analysis using Python's NLTK library. Just read his writing Sentiment Analysis With Python's NLTK Library to find out.
• Have you ever wondered how recommendation systems are working? Rahul Banerjee not just explains it but also builds a solution in his writing How to Build a Recommender System with Embeddinghub.
• Creating a machine learning based solution is one thing, but operating that is at least as crucial as implementing it. Patrick Alves gives his advice regarding the operation in his harticle [MLOps: What it is and why does it Matter?]. (https://cpatrickalves.hashnode.dev/mlops-what-it-is-and-why-it-matters)
• Tiia shows us how we can leverage machine learning to create an animated avatar that reacts to our voice.
• If you read the first section of this article, you know I am obsessed with brainwaves. I am using a Muse S EEG band which has lots of limitations. Sajal Tiwari goes multiple steps further and shows us what results can be achieved by using an fMRI device in the Deep image reconstruction from human brain activity harticle.
• I will be honest. I believe we are in a war with AI. We have already lost many battles: We lost in chess, go, Starcraft, and in other fields too. In a few years (or months), AI will beat us in programming too. Up till it is not guaranteed that AI is emphatic, understandable, non-biased, and ethical we cannot feel safe. Alao D. I. compares Humanish Intelligence (HI) with Artificial Intelligence (AI) in his blogpost The Thinking of Man: Human Vs. A.I..

Security

• Do you think you are safe and you won't be a target of cyberattacks? Well, I have bad news for you. Chidiogo debunks some myths in Cyber Security Facts and Misconceptions.
• Have you ever heard the name Snyk? Me neither, up till I started to work at my new company. Ashutosh Krishna tells us about Snyk everything in the How to Find and Fix Security Vulnerabilities Using Snyk harticle.

DevOps, CI/CD

• Kubernetes is a frequently used buzzword nowadays, but it is a buzzword with a good reason. Containerization and handling of containers became crucial in today's world. Eshan Sharma [A Simple Guide to Kubernetes] explains what is Kubernetes in his writing (https://eshansharma.hashnode.dev/a-simple-guide-to-kubernetes).
• You cannot become really agile without having a great CI/CD pipeline. Ozone Ozone tells about the history of CI/CD pipelines in his CICD Pipelines: Evolution with Time blog post.

Blockchain and Web3

• Have you ever heard the word DAO? No, I am not talking about Data Access Objects. I am talking about Decentralized Autonomous Organizations. Nonstack tells almost everything about DAOs in his writing The Complete Guide to Decentralized Autonomous Organizations. I said almost as reading his article raised a few questions in me for which hopefully I will get the answer soon in the article's comment section.
• Nonstack also wrote an excellent article from which you can learn the basics of blockchain technology. Just read his harticle called Demystifying Blockchain Technology.

Tools and resources

• Do you use Visual Studio Code? Well, I am not using it anymore, but if you do Ivan's post can be helpful for you, so here it is: 5 Of My Favorite VSCode Extensions
• Being a software developer is a never-ending journey as you have to keep pace with the continuously changing world. One of the weapons you can use is learning from a platform specialized in teaching software development. Maheshwar Ligade lists 5 online platforms with which you can grow your software engineering skills.

Technicalish articles

• My motto is: Writing is fun, reading should be fun too. Based on the inspiration coming from Leandro Melendez, I have decided to become a technicalish writer to write about technical topics in a fun (yeah, I know, my humor s.cks) way.

An interesting conversation between JVM & the Java Compiler is the first-ever technicalish article I have ever read on Hashnode. Thanks, Debashis Panda. I hope this is not the last one.

New Hloggers

• I had no idea what was DevReal, but after reading Lucas D.'s first post Ok, so I definitely belong in DevRel, I googled it. No. I won't tell, and not because it is still not completely clear for me, but because I leave the joy of discovery for you. 😊
• Eula C. just debuted on Hashnode), but she is not new to blogging as she has a WordPress blog too. We can expect articles related to cybersecurity from her.
• Utsav bhattarai is quite ambitious as he is already telling us how to write a blog in his first-ever blog post, still, I like his courage, and if you read his article My first Blog - How to write 8log🙂🙂, you can find valuable advice there.
• yash pandit started a new good habit! by starting blogging. He is a little bit mysterious as he did not tell us what he would write about, so I asked him in the comment section. I hope he will answer soon.
• We are on the same page with Markos Korvesis, who says, "The idea that my words may help even one single person is for me as good a reason as any to write them". If you would like to find out what will he post about, then just read his first post Oh no... not another one..

That's all, folks. We have arrived at the end of this article.

NoShare: Dear Reader! In case you found this article boring and useless, then please do not share it as we do not like negative marketing.

But in all other cases please share it with your social media friends, so they might also get inspired thanks to this collection of awesome harticles.

Don't forget to read the previous Hashnode Weely Newsletters:

1. Hashnode Weekly 001 by Miki Szeles
2. Hashnode Weekly 002 by Miki Szeles
3. Hashnode Weekly 003 by Miki Szeles
4. Hashnode Weekly 004 by Miki Szeles
5. Hahnode Weekly 005 Limited Edition by Miki Szeles AKA The Big Delete

P.S.: Something good will happen to you today!

My goal is to become a freelancer doing test automation in half time and doing technicalish writing in the other half. I am available to work as a technicalish writer and I would really appreciate it if you would support me if you found my writings valuable in any sense.

Hackernoon interviewed me, so if you would like to learn more about me, just click here and read it!

Become an agileish superhero!

Learn how to memorize anything in the world. In this series, I teach you everything I know about learning and memorization, including memory palaces, marker images, number memorization techniques, associations, etc.

You can already find the first videos on my Youtube channel in which I show you that it is possible to memorize such boring things as positions of circles.

Don't forget to read How You Can Become An Agileish Super Learner AKA How You Can Become A Super Thinker AKA The Proof Of Concept (POC) before you watch the videos.

Join the Agileish Superheroes Facebook group to learn memorization techniques, thinking techniques, agility, reading and learning techniques and also to get notified about new live sessions and videos

As I am a crazy person, I have open-sourced my life on GitHub on Fool's day.

I am sharing my thoughts, writings, and creations, and as I am frequently committing, I have open-sourced my thinking process, my writing process, and also my creation process.

Just click here to check my open-sourced life on Github!

My credo: The Mystery Of The Supposedly Red Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet

Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humor, and I am also happy to tell you that this is my article about which I am the proudest of now.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to, on Hackernoon and even on Instagram.

• Minnie: Finally the CTA is over. We can get to the teaser.
• Miki: Yes, finally.
• Minnie: What are you working on recently?
• Miki: I am writing an article with the title "How You Can Become a Test Automation Engineer in 2022 AKA How I Became a Test Automation Engineer".
• Minnie: Sounds fun.
• Miki: This time it won't be fun, as I am writing it alone, as this is a serious topic.
• Minnie: I see. When will you publish it?
• Miki: I do not know yet, but the draft is available on my GitHub if somebody would like to follow the birt of the harticle.
• Minnie: Cool.

• Maudience: Dear Reader! Miki likes to write. Miki likes to write a lot. The whole team tried to persuade him to write shorter articles, but Miki couldn't stop doing that. Last time he wrote an article with 42 minutes of reading time. So instead of writing less, he hired me to make sure our readers could get the most out of our articles no matter how much time they had.

So in order to make your life easier, I have created a table content like thingy for you.

Tableish Contentish

• Click here to learn a little bit about Miki's present!
• Click here if you would like to know what Miki and his brother Tomi got for Christmas several years ago!
• If you want to know which were Miki's favorite games back then, then click here!
• Miki was the perfect examplar of impostor syndrome and he is also an introvert so Miki did not attend conferences for 39 years. Click here to learn more about it.
• Miki's first conference was a disappointment. Click here to find out why.
• If you want to know how Miki fell in love with conferences on second sight, just click here!
• Click here if you want to know the short answer to why Miki is attending the Craft Conf 2022!
• If you want to know the long answer to why Miki is attending the Craft Conf 2022, then click here!
• Do you want to have a Google spreadsheet with which you can quickly create your schedule for the conference? Click!
• Are you only interested in the 20% ticket discount? Just click here!
• Do you want to have a free ice cream coupon for the conference? Just click here and claim it from our good old friend Rick!
• Do you like endless loops? Click here!

Who Am I?

HI!

I am Miki Szeles from Hungary, Budapest. I am a father, a husband, and a soon-to-be happy dog owner.

Software Engineer in Test (SDET)

I am a software developer with 15 years of work experience, from which 8 also included leading the dev and test team. At the moment, I am working as a Senior Software Engineer in Test using Selenide for E2E automation, Karate DSL for API automation, and Gatling for performance testing.

Agileish Human

I am developing software the agile way, but in addition to that, I made my whole life agile.

By introducing short 15min - 3 hours sprints walks with a retro at the end, my life has changed completely.

No matter what I am doing, I am improving rapidly thanks to the very short feedback cycle.

I believe learning is the most crucial skill of humans. In case we can learn fast, we can become better rapidly in anything we are doing.

Cause of this, I am focusing on improving my memory and reading skills.

You can read more about being an agile human with super learning, super memory, and super thinking superpowers in my article: How You Can Become An Agileish Super Learner AKA How You Can Become A Super Thinker AKA The Proof Of Concept (POC)

That's more than enough about my present, but if you still want to know more, I recommend reading this Hackernoon interview: 'I Open-Sourced My Thinking Process': Meet HackerNoon Writer & Test Automation Engineer Miki Szeles!

Click here to return to tableish contentish!

My First Contact With Computers

I will never forget the moment when a few weeks before Christmas we were jumping on our parent's bed with my brother Tomi. We accidentally jumped so high we saw a box on top of the wardrobe. We got really excited, so we tried to jump even higher to see what was that. Then we suddenly saw it, and we couldn't believe our eyes.

It was the long-desired Commodore 64.

I do not have to tell you we were so excited we couldn't wait till Christmas, so we begged our parents until we did not get it.

That was the moment when I made first contact with computers.

Click here to return to tableish contentish!

My First Programming Experience

In the beginning, we were only playing games. I had many favorites like Giana Sisters, Bruce Lee, Pirates, Defender of The Crown, and Ugh Olympics, just to highlight some of them.

It didn't take too much time, and I wanted to create my own games. There was a guy in the town who could program, so I asked him to teach me programming. He gave me 3 Commodore 64 programming books called Hetedhét, so I started to learn BASIC from those books.

I remember I was drawing pixelated graphics in a notebook, trying to figure out how the hell I could display them on the computer. I have to admit I did not really understand the binary system back then, but still, I was able to draw some sprites on the screen.

That is how my software development career started.

I won't bore you with the other details, so let's fast forward to the beginning of 2022.

Click here to return to tableish contentish!

Why I Did Not Attend Conferences

Despite attending meetups and code retreats several years ago, I have never attended a conference. When my son was born, I even gave up visiting the meetups as I wanted to spend as much time with Levi as I could.

I played with the thought of attending a software development conference, but in the end, I never went for multiple reasons:

1. I was an introvert. The thought of being together with hundreds of people whom I do not know scared me like hell.
2. My previous company did not support me in any way to attend a conference. Neither with extra free days for the time of the conference nor with conference tickets. I do believe sending your developers to a conference is an investment. It is an investment as the knowledge they get can benefit your company. If you do not support them, then 2 things can happen. a. They will simply not go to the conference. b. They attend the conference in their own time using their own money. If a developer cares about his/her future a little bit, then sooner or later, he/she will ask for the price of the extra knowledge he/she got from the conference. I guess I do not have to explain why it is better to sit down to negotiate the salary in the case in which you supported your developer to get that valuable knowledge. CraftHub, the organizer of the Craft Conf conference, even created an email template that helps you convince your employer to support you in visiting the conference. Just click here to download it!. If I wouldn't have a ticket, I would use the reasons from the email template to convince my employer personally to support me in attending the conference.
3. I was the perfect exemplar of the impostor syndrome. I was working on neural code (almost every piece of code is connected to nearly all the others) with outdated technologies. Looking through the job ads just made me feel worthless. Seeing all those long lists of technologies in those ads ensured me that I am one of the world's worst developers despite loving programming since I was 10. I knew I had nothing to do at a conference where great developers from all around the world were gathering together. It might sound funny, but that was my reality not so long ago. Luckily, in the end, I decided to start at another company, and since then, I have been thriving. I can do my daily job pretty well as I am using cool and very effective frameworks like Selenide, Karate DSL, and Gatling. Leaving behind my impostor syndrome, I realized no matter what level I am with programming. I can benefit a lot from visiting conferences. So at the beginning of 2022, I started to look for worthwhile conferences

Click here to return to tableish contentish!

My First Contact With Conferences AKA Love at First Sight? Nope!

Well, as it might happen, the first one was not the best. It is possible I had too high expectations, but it is also possible it misled me with her kind words.

She told to me we had a great future together but in the end, I realized she was living her life in the past, not looking forward to the future at all.

Despite this, she had many values, but all in all, we weren't a perfect match.

I will always remember her, as she was my first one.

Click here to return to tableish contentish!

My Second Contact With Conferences AKA Love at Second Sight

Since February, I have been attending the data analysis course at Budapest University of Economics and Technologies (BME) as an external student. It was by accident I got aware of this opportunity.

Our tutor István mentioned a conference which is about artificial intelligence (AI) and machine learning (ML) including deep learning too, of course.

This conference was the Reinforce AI conference.

I got very excited, but the excitement went away pretty quickly as I realized I only had 3 days of vacation left as I had to book all my other days at the beginning of the year. As AI and machine learning are not (yet) closely related to my current job, I couldn't ask for support from my company.

After looking at the talk topics, I still decided to invest three vacation days in this conference.

By now, I can tell you this was one of the best investments in my life. Without it, I would know almost nothing about the current state of AI, and without visiting the conference, I wouldn't write this article now. More about that later.

Reinforce AI was a 3 days long conference featuring talks of great experts from all around the world. As I later got to know, it was organized by Felhő, Anna, Médea, Károly, Barna, Vanda, Viktória, Anna, Renáta, Fanni, Bianka, Réka, Kata, Barbara, Veronika, Vivien, Marcel, Martin, Emilía, Kristóf, Gergő and László. They are the people behind CraftHub.

CraftHub organizes conferences on various topics. I stole the short descriptions from their site. I hope they won't be mad at me 😊:

• Craft Conf: Craft is an inclusive conference about software craft, giving tools, methods, and practices that can be used in the life of a modern developer or company. This conference serves as a compass for new technologies and trends shared by international experts.
• Stretch Conference: An international platform and community for leaders and managers to share stories and hands-on solutions and explore new trends and ideas to lead, fail, learn and stretch.
• Crunch Conference: A conference for people working as Data Engineers, Data Scientists, or simply interested in how to utilize data to develop their business. No matter the size of the venture or job description, everyone can find exactly what they need.
• Amuse Conference: An international conference and learning platform about user experience, product design, user research, service design, creativity, and more. An event dedicated to UX practitioners, product managers, frontend developers, designers or market researchers of digital products, or anyone who is simply interested in what’s happening on the other side of the screen.
• Reinforce AI Conference: This conference brings together world-leading experts on AI and creates a platform for discourse, innovation, and networking. It provides opportunities for learning and discussing the different fields of AI, such as ethics, production, and the future of artificial intelligence.
• Impact Conference: Impact Conference brings together people who are passionate about building amazing, high-impact products. The perfect conference if you aspire to become a Product Manager, Product Owner, Product Leader, Business Analyst or if you are simply an enthusiast who is eager for knowledge, ideas, and best practices shared by world-renowned experts.

I just read the descriptions of these conferences at the time of writing this article, but I am pretty sure I will do what I can to visit all of them.

Most probably, I will have to take out unpaid holidays, but that seems a fair price in exchange for what I can get from these conferences.

However, most of them are not closely related to my current daily job (being a Software Development Engineer in Test). I believe you can achieve great things if you combine not closely related things.

As I am always looking for these opportunities, I usually find a way to combine them. Thanks to this, my water droplet photographs came to life by combining software development, hardware tinkering, and photography. photo

In addition to organizing conferences, CraftHub also organizes Hackathons, and Meetups.

Turning back to the Reinforce AI conference, I have to tell you this was the most eye-opening event I have ever attended. I got insights about not just the present but also the future of AI.

The first speaker was Richard Boyd, who is the CEO and founder of Tanjo Inc. His talk was the most astounding technical speech I have ever heard, and I am sure it will take some time to listen to another address that can take the first place.

If you would like to know what I have heard, just read my Would You Freak Out If You Could Talk To Dead People? - Miki Szeles's Report on Reinforce AI Conference article.

Many other talks followed Richard's speech on various topics like real-time sentiment analysis, synthetic data, AI singularity, responsible AI, time series analysis with deep learning, interpretable AI, AI ethics, and more.

I took notes during almost all the talks, but I am almost sure I won't have time to write articles from them, so I have uploaded my draft to my GitHub.

All in all, this was the story of how I fell in love with conferences at second sight. Click here to return to tableish contentish!

Why Am I Attending The Craft Conf 2022 Software Development Conference? AKA The Short Answer AKA Cooperation with CraftHub, the organizer of the Craft Conf conference

Three weeks after the conference Anna Dalma Kajtár sent me a message on LinkedIn.

Anna told me they had really loved my article about the Reinforce AI conference and they would like to cooperate with me.

She asked me to write an article before the conference and after the conference too.

After a few rounds of negotiation, we came up with a deal that is beneficial both for CraftHub and myself.

This is the short answer for why I am attending the Craft Con 2022 conference.

Click here to return to tableish contentish!

Why Am I Attending The Craft Conf 2022 Software Development Conference? - The Long Answer

The first answer is a true story, but that was only the beginning. As soon as I got the offer, I started to think about how I could get the most out of this conference. So let's see why I am attending the Craft Conf in reality.

Spending 2 days with my friends

During the 15 years of my professional career and during my university years, I have met many exceptional professionals. Some of them became my friends.

Unfortunately, life has carried us away, and I am meeting regularly only a very few of them.

This is why I decided to make Craft Conf the place where we will meet each year. Cause of this, I asked for conference tickets from CraftHub instead of money in exchange for my technicalish writing.

It is not easy for me to find time to hang out with my friends, but in case we can not just spend time together, but we can learn a lot in parallel, that really makes this reunion a great opportunity for meeting with my pals. Hopefully, their employer will support them with paid vacation days.

Four of my friends and hopefully my brother Tamás will come with me this time, but I hope they will come next year too and hope other friends will join.

Listen to talks of familiar faces

I have to admit I only know three names from the 70+ speakers.

My life was quite a rollercoaster ride during the last few years, and I couldn't focus on keeping up with the continuously changing software industry.

I improved myself by Udemy courses and reading technical articles but as I was mostly interested in test automation, I did not face the speakers.

Craft Conf is the perfect opportunity to get back on track, so I will definitely listen to Michael Feather's, Dan North's, and Ivett Ördög's talks.

Listen to talks about topics I am most interested in

2019 was the last time when Craft Conf was an offline event. Back then, there were 81 speakers and around 2500 visitors.

Then Covid came, so there was no Craft Conf in 2020, but one year later, CraftHub organized the event online with 84 speakers. More than 1200 software developer was interested in Craft Conf 2021.

To be honest, not all of them were Software Developers, as many Software Designer, Agile Coach, Business Developer, DevOps Engineer, Engineering Manager, Front-end Developer, Product Manager, and Software Architect visited the event too.

I am pretty sure most of the talks will be outstanding, but I still would like to highlight some of the talks:

• Dmitry Razorionov - How AI/ML shapes EPAM into the Adaptive Enterprise (Epam)
• Eric Brewer - Open Source Security: The World Needs Our Help (Berkeley)
• Jessica Kerr - Gamification without the Garbage (Honeycomb)
• Linda Rising - About trees, agility, and me (Independent consultant)
• Marian Hartman - Using Empathy to Make Tests Easy and Code Safe (Dig Deep Roots)
• Meri Williams - 5 Things I Wish I'd Known Sooner About Scaling Teams (Chromerose)
• Rebecca Allen - Making big changes feel small: technical evolution within an organisation (Liveeo)
• Matthew Lavoie - Assumptions on the Road to Success or Failure (NASA)
• Matthew Phili - No (Lab) Jacket Required: Designing Experiments for Learning (Pfizer)
• Mohammad Aboullaite - Move fast Build things… Safely! (Spotify)

Networking with other developers

Well, I am not sure about that. My friends will be there, and I am pretty sure I will see a few familiar faces, but I am still an introvert so we will see.

CraftHub is organizing a networking party on the first day, so most probably, I will give it a try. Or not. I do not know yet.

To ride dodgem with my friends

I fell in love with dodgem when I was a child. Unfortunately, I grew up, and I thought it was awkward to play dodgem as an adult, so I gave up doing that. Luckily I have an eight years old son, Levi, so I can play dodgem again without feeling wrong about that.

The good news is that there will be a dodgem at the conference, and they will borrow a kid who sits beside you to make sure you won't feel awkward in the dodgem.

Ok, I have to admit that would be more awkward, but luckily they are not planning to do that.

Based on my experience, three common things are enough to start a relationship that might end up in a friendship.

Loving software development, being interested in conferences, and having a car accident together are more than enough to start a conversation. Especially as car accidents make people talkative, just don't forget your neck brace at home.

Click here to return to tableish contentish!

Your Craft Conf Planner

I got a Google spreadsheet from Anna Kajtár in which the complete schedule is included. I made a conference planner with which you can easily create your schedule by simply highlighting the ones you will attend. Click here to access the docu! You just have to create a copy of it, and you can start planning.

Click here to return to tableish contentish!

20% Craft Conf 2022 Discount

I've almost arrived at the end of this article. I just want to write one last closing section in which I am providing a registration link with a 20% discount on the price. I just have to figure out what to write so that I will use the Pomodorish technique.

I'm a big fan of the Pomodorish productivity technique in which a 5min-15min smoking coffee drinking session is followed by a 15min to 2 hours long writing/programming period, depending on how long the flow remains.

If my son comes after 15 minutes to play something, then 15 minutes, but if my family is sleeping or I am at my workplace, the flow can remain even for 2 hours.

As I almost finished this article, I will go out now to come up with some witty closing words. Up till then I leave here a video about the Craft Conf 2019 conference:

Re.

Believe me! I tried it! I tried it, but I couldn't come up with something funny. I have seen 1 hooded crow, I've walked 2 blocks, smoked 3 coffees, met dame Sophie 4 times, and meditated with my new Muse S for 5 minutes, but nothing came into my mind.

So here is the link. Just click here to register for Craft Conf 2022 with a 20% discount!

Thanks for taking the time to read my article. Before I leave, please let me give the mic to my marketing expert, NoShare.

NoShare: Dear Reader! In case you found this article boring and useless, then please do not share it as we do not like negative marketing.

But in all other cases please share it with your social media friends, so they can they might get inspired to visit the conference.

Miki, NoShare: Thanks! Have a nice day!

• Minnie: Pssst. Miki! Are you still here?
• Miki: Sure. I am always waiting till the end of the movie since Marvel started to put teaser trailers after the cast list.
• Minnie: Me too. I love those teasers. Shouldn't we create our trailer?
• Miki: That is a great idea.
• Minnie: What should it be?
• Miki: There will be a Craft Conf giveaway soon on my Hashnode-powered blog.
• Minnie: Cool. How can the readers get info about the giveaway?
• Miki: The details will be out in a day on my blog, and I will also update this article when I have the link.
• Minnie: Wow. I want a ticket too. How can I participate?
• Miki: You have to write articles, but more on that later.
• Minnie: I love that. Bye for now.

• Miki: Bye.

• Maudience: Minnie, Miki! The Craft Conf giveaway article is already out. Click here for details!

• Miki, Minnie, Maudience: Something good will happen to you today!

I will lead you through the development of an app with which you can detect eyeblinks using a Muse S EEG band. We will convert the eyeblinks to text using the Morse code. As a result, we will have a solution with which completely paralyzed people can communicate with their loved ones.

I will also demonstrate how you can build an app in pure Python with the aid of Kivy resulting in a program that can be packed to Android, iOS, Windows, and Mac.

Before we start coding, please let me share some moments from my life which led me to start tinkering with my brain.

The Backstory

My First Contact With Brainwaves

Let's move back 30 years in time.

I was sitting in front of my Commodore 64 computer in my room. My brother had already moved out by then, but I was not alone, as my friend Szabi was also with me.

I loved computer games. Playing games like Ugh Olympics, Pirates, Defender of The Crown, Boulder Dash, Wizard of Wor, Nebulus, and Bruce Lee gave me more pleasure than anything else in the world.

At that time, I was playing a newly discovered game called Benji. I was trying to figure out how to play the game with little success.

Suddenly I saw something in the corner of my eye, so I turned right to look through the window. There was nothing unusual except one thing.

A black figure was floating in the air above the roof of our garage.

I got scared as hell, so I asked Szabi whether he also saw the figure or not.

No! There is nothing there. - he replied.

Szabi went downstairs to tell my parents what had happened to me. My parents came up in a hurry, and they quickly realized something was not ok, so they saw me down in the living room.

I remember they asked what my name was. I started to think, but I couldn't answer as I couldn't recall it. The feeling I felt at that moment when I couldn't remember my name had been burnt into my mind for eternity.

From this point, I couldn't recall anything as I lost my consciousness. A few seconds after my parents called the doctor, my whole body started to shake unstoppably.

That was the first time when I had an epileptic seizure.

My next memory is being in the hospital. A few hours later, a nurse led me into a room, lubricated tiny thingies with a cold gel, then put a bizarre hat on my head. The hat was strange as many wires were coming out of it, all of them connected to a machine.

I had to lay down and stay calm, and then the machine drew lines on paper.

As I found out later, those were my brainwaves, and the machine was an electroencephalography (EEG) device. I couldn't understand the EEG diagram, but based on what I heard, they looked pretty bad back then.

A couple of days later, I could go home.

I was not allowed to play on computers or watch TV, and I couldn't go to the disco with my friends.

Fear became my and my family's best friend from that point as we could never know when another epileptic seizure would come.

During the upcoming years, I had to take medicines, and I also had to visit the hospital many times to have regular checkups with a neurologist. During these visits, I started to form a friendship with this EEG device. Month by month, my EEG results became better and better.

I can still remember the room's smell, the feeling of the cold gel, the long wires, the small diodes, the strange hat, and the EEG curves painted on paper.

I never had another epileptic seizure again, and after three years, my neurologist told me I had recovered.

My Second Contact With Brainwaves

The year is 1994, just two years after my epileptic seizure. My parents enrolled me and my brother Tomi in a Silva Mind Control for kids course.

I have very few memories, but I remember when I heard about delta, theta, alpha, and beta brainwaves. I have not just heard about them, but I also learned how to control the brainwaves by relaxation in theory.

I visited the Silva Mind Control training with my friend Edit four years later. By then, I understood and learned many techniques that were taught there.

Even if none of the magical techniques would work, I still learned about peg lists and relaxation.

In reality, I used the other techniques, and I do believe they worked, but as I had no parallel life (at least I am not aware of that) in which I could live the same life without doing the Silva course, I cannot tell if my achievements were related to those techniques.

One of the biggest benefits of the course was learning relaxation. Unfortunately, there was one massive problem with it:

I couldn't tell if I was really in alpha or not. More on that later.

A few years later I went to the Budapest University of Technology (BME) and I became a scientistish.

Scientistish means I do not believe in anything except it was proven by science. Thanks to this, I was sure all the Silva methods were fake similar to all the other supernatural things I have heard of.

My Third Contact With Brainwaves

Twenty-four years later, we arrive in the present. During the last years, I went through an emotional rollercoaster. I had such deep depression I was sure I would lose my job, my flat, my family left me, I became homeless, and I will even be bad for a homeless, and I die in a couple of days.

I know it sounds funny, but that was my reality back then.

It took me two psychologists, 2 psichoterapeut, a RED EQ trainer, and the support of my family and friends, but finally, I managed to come back.

This experience has changed my life forever. I am currently re-reading Eckhart Tolle's The Power of Now Book, and I see some similarities between his life and my life. However, I did not become homeless in reality, I was homeless in my mind. Now I understand much more from that book.

Also, by now, I have become a hscienistish. Hscientistish means I believe in what humans say, and I try to verify it by talking to that person and using somewhat scientific techniques.

I cannot tell exactly what the trigger was. Still, I decided to order a Muse EEG band and examine my brainwaves during experimenting with different meditation and relaxation techniques to find out which worked and which did not.

My Muse S arrived three weeks ago, but before it arrived, I had already come up with an idea in which I could combine programming and my brainwaves. Before I get to the point, please let me tell you about how I got inspired to implement my first mind-controlled app.

The Inspiration

I was googling different apps developed for the Muse band, but I realized there are almost no apps, or at least it is not easy to find them via Google. Luckily I found an article from Anush Mutyala with the title Muse 101 — How to start Developing with the Muse 2 right now.

Anush has developed a hands-free slideshow that can be navigated by using eyeblinks. He was also able to switch Chrome tabs using eyeblinks and scrolling via measuring the focus/concentration of the user using only the raw EEG data. He even made a video summarizing solutions built on brainwaves.

In addition to Anush's article, I found a fascinating project. Scientists from the University of California, San Francisco (UCSF) have developed a solution that was able to recognize words/sentences with 96% accuracy.

There are some drawbacks of their solution:

1. The number of recognized sentences is limited to 30-50 sentences.
2. Their solution is not open-source, as far as I know.

Despite this, it is a fantastic achievement as they proved it is possible to recognize sentences by analyzing our brainwaves. And this was in 2020, I am very curious about where they are at the moment.

They have published their research paper in Nature Neuroscience journal.

So, in the end, these projects were my inspiration to start my journey in the field of Brain-Computer Interfaces (BCI).

The Idea

After reading the articles, my brain started to spin, and after thinking for quite a while, I came up with the idea of developing my version of a brainwave to text application.

I detect eyeblinks via brainwaves and convert them to text using the Morse code. However, it is much slower than the UCSF scientist's solution it is still a solution with which completely paralyzed people can communicate with their loved ones.

While looking for information about detecting eyeblinks, I realized there are already implemented solutions for detecting eyeblinks and converting them to text using the Morse code. Some of them use a camera, but others use an EEG band.

Despite this, the project is still valuable for the following reasons.

1. I am building a framework that handles the whole communication with the EEG bands, so developers and neuroscientists can focus on what matters: implementing the different algorithms with which they can extract information from brainwaves.
2. There are many different EEG devices, and my goal is to support many of them. As soon as you get the raw EEG data, it does not matter which device it came from.
3. This is an open-source project, and I hope a couple of enthusiastic people will contribute to the project.
4. This is my first step in the field of Brain-Computer Interfaces. A learning project from which I learn about brainwaves, Python, and the Kivy framework.
5. I am providing a solution with which completely paralyzed people can communicate for the price of a mid-level phone (400€). My project is open-source and free, but it requires a Muse band (I recommend Muse S) and the Mind Monitor app.
6. It can be used in complete darkness as no camera is needed.

We have the inspiration, the idea, so it is time to set a goal.

The Goal

Recently, I usually set HSMART goals for myself, which is my extension of the SMART goal concept. Here are the meanings of the letters:

• Humanish: It has to be something that makes this world a little bit better, and at least a small portion of humanity can benefit from it.
• Specific: The goal has to be clear and specific.
• Measurable: To track my progress and stay motivated, the progress has to be measurable.
• Achievable: The goal has to be realistic. It does not make much sense to set an unrealistic goal.
• Relevant: The goal has to matter to you. If you are working on something not relevant to your current situation, it will be tough to find motivation.
• Time-bound: Without a deadline, you can quickly lose focus. Parkinson's law straightforwardly expresses this: "work expands to fill the time available for its completion." From this, it is easy to see if you do not have a deadline, you can work forever without any real progress on your task.

So let's see my concrete HSMART goal:

• Humanish: I believe Brain-Computer Interfaces (BCI) can make the world better if used for the good. Having a framework that can be used to develop BCI-based apps and having a solution with which paralyzed people can communicate with their loved ones is definitely humanish.
• Specific: I want to develop an app with which completely paralyzed people can communicate with others. In addition to this, I want to develop a framework with which any developer can jumpstart their brainwave project.
• Measurable: I have defined multiple milestones to measure my progress
  1. Get the RAW data from the Muse
  2. Display live brainwaves
  3. Detect eyeblinks using brainwaves
  4. Classify the detected blinks based on their length
  5. Convert the blinks to text using the Morse code
  6. Design the UI of the mobile app
  7. Develop the app
  8. Write the article to participate in the Hashnode Writeathon
• Achievable: Considering that I have a full-time job and a family, the deadline is very strict, but it is still achievable. I have time for the project when my son is sleeping which means ~2 hours in the morning and 2-3 hours in the evening, and 8-10 hours during the weekend. On weekdays I always spend ~2 hours with my son when I arrive from work. We split the day into 1-2 hours long blocks during the weekend. One block spending time together and one block me time. We repeat this from the morning till the evening, so we spend a lot of time together, and everybody has time to focus on their things.
• Relevant: I am highly motivated to put my feet in the field of brain-computer interfaces (BCI). I recently visited a data analysis course as an external student at the Budapest University of Economics and Technology (BME). We learn fundamental data analysis, machine learning (ML), and deep learning. I will definitely put my recently acquired knowledge into practice in this project.
• Time-bound: From the moment I get the Interaxon Muse S, I have 3 weeks.
  • One week to learn about brainwaves and develop the framework.
  • One week to implement the blink detection algorithm.
  • One week to create a mobile app and write an article to participate in the Hashnode Writeathon.

We have the HSMART goal, so it is time to start our project and select the technologies.

Selecting The Tech-stack

As Python is the number one programming language for data analysis and machine learning, the choice was almost straightforward. Apart from a few scripts, I have not used Python during my career, so this will be my first ever Python project. According to the TIOBE index, Python is the most popular programming language, and it is also easy to learn, so I chose Python.

At first, I wanted to develop a web app, and I selected Anvil Works as the framework for development as with it, you can create and host a web app in no time.

While reading the tutorials, I realized I have to communicate with the Muse device, which could be problematic from the browser. I will need not just a frontend but a backend implementation. To communicate with the Muse, it is highly advised to do it on a local network, which means I should host my backend locally.

After some thinking, I realized a mobile/desktop app is more suitable for my task. After a little googling and comparison, I decided to go with Kivy.

Kivy is a free open source cross-platform Python library for rapid development of applications that make use of innovative user interfaces, such as multi-touch apps and it is even GPU accelerated.

As I had no chance to learn a frontend framework like Angular in a few days, the idea of developing a mobile app in pure Python enlightened me.

However, after googling, I found Muse has an SDK (one of the main reasons I ordered the Muse). When I asked the Interaxon support for the link, they told me at the moment, there is no publicly available SDK, so I had to look for another solution.

Luckily I found Mind Monitor, which connects to the Muse and gets the RAW data, and it can even stream it using the Open Sound Control (OSC) protocol as UDP packets.

Because of this, pythonosc was a straightforward selection to grab the live EEG data.

That is enough from the tech stack. Let's start implementing the solution.

Learning About The Interaxon Muse S

The Muse S is a 4 channel band which means you can measure signals at 4 different points on your head. Thez are AF7, AF8, TP9 and TP10. AF7 and AF8 are positioned on the front of your skull, and TP9 and TP10 are placed at the back of your head. To learn more, just read the 10-20 EEG system description on Wikipedia).

You have to know that the scientist at UCSF used 120-200 EEG channels, and we only have 4. But I am completely fine about that, as having more channels would be overwhelming initially. Having such a limit inspires me to be creative, and thanks to the price of €379.99, it is affordable to anyone who would like to start developing brain-computer interface (BCI) based solutions.

However, I am pretty sure four channels will be adequate for a while. I already found the device that will probably be the next EEG device I use. It is the EPOC Flex Saline Sensor Kit which has 32 channels, but it costs four times as much as the Muse S ($1800).

Most probably, I will only get that if I find supporters for this project or in case, I hit the limits of the Muse S.

The Muse has the earlier mentioned 4 channels and 2 amplified Aux channels in the specification. It has a 256Hz sample rate and 12bits/sample resolution, which seems more than enough as usually, we are only interested in delta(0.5-4Hz), theta(4-8Hz), alpha(8-13Hz), beta(13-32Hz), and gamma(32-100Hz) waves. For more details, check this page.

The EEG band also has a gyroscope, an accelerometer, a PPG sensor (which can measure heart rate), and a thermistor.

The band comes with an app with which you can get real-time feedback about your meditation's effectiveness, and it has many guided meditations. In addition to this, it has many soundscapes and journeys that help you fall asleep and track your sleep.

That is more than enough about the Muse S band, and it is time to make our hands dirty and write some code.

The Implementation

This is my first real Python project, so I am sure my code is rather messy, mainly because I focused on the quick results.

But here comes one of the real advantages of open-source development. I can get feedback about my code and even code change suggestions in pull requests. So I am sure it only needs a few weeks, and this project will be a good starting point if somebody would like to start open-source contribution, learn Python, or brain-computer-interface (BCI) development. I will personally make sure it will be a kind and supportive community.

However, Python is a scripting language it also supports object-oriented development, so most of my code is object-oriented, but not all of them. I still have to find the balance.

Implementing Data Classes

I have created multiple Python modules. One of them is eeg_commons, which contains generic data that can be acquired from an EEG band. In addition to raw EEG data, it also supports gyroscope and accelerometer data which can be used in further applications.

I also created a WindowedSeries and an EEGSeries class to plot the data and get the median.

from enum import Enum
from statistics, import mean, median
import datetime


class DataType(Enum):
    EEG = 1
    GYROSCOPE = 2
    ACCELEROMETER = 3


class EEGChannel(Enum):
    AF7 = 1
    AF8 = 2
    TP9 = 3
    TP10 = 4
    AUX = 5


class EEGChannelMapping:
    def __init__(self, *args):
        self.index_to_channel = {}
        self.channel_to_index = {}

    def add_mapping(self, index, channel):
        self.index_to_channel[index] = channel
        self.channel_to_index[channel] = index

    def get_channel(self, index):
        return self.index_to_channel[index]

    def get_index(self, channel):
        return self.channel_to_index[channel]


class Data(object):
    def __init__(self, data_type):
        self.creation_time = datetime.datetime.now()
        self.type = data_type


class EEG(Data):

    @classmethod
    def create_eeg_data_map(cls, channel_mapping, data_tuple):
        data_per_channel = {}
        for idx, data in enumerate(data_tuple):
            data_per_channel[channel_mapping.get_channel(idx)] = data
        return data_per_channel

    def __init__(self, eeg_data_map):
        super(EEG, self).__init__(DataType.EEG)
        self.data_per_channel = eeg_data_map

    def get_channel_value(self, eeg_channel):
        return self.data_per_channel[eeg_channel]

    def channel_count(self):
        return len(self.data_per_channel)

    def get_channels(self):
        return self.data_per_channel.keys()


class Gyroscope(Data):
    def __init__(self, *args):
        super(Gyroscope, self).__init__(DataType.GYROSCOPE)
        self.x = args[0]
        self.y = args[1]
        self.z = args[2]

    def get_up_down_location(self):
        return self.x

    def get_tilt(self):
        return self.y


class Accelerometer(Data):
    def __init__(self, *args):
        super(Accelerometer, self).__init__(DataType.ACCELEROMETER)
        self.x = args[0]
        self.y = args[1]
        self.z = args[2]

    def get_left_right_pitch_acc(self):
        return self.x

    def get_up_down_acc(self):
        return self.y

    def get_left_right_acc(self):
        return self.z


class WindowedSeries:
    def __init__(self, window_size):
        self.elements = []
        self.window_size = window_size

    def add_element(self, element):
        self.elements.append(element)
        if self.window_size == len(self.elements):
            del (self.elements[0])

    def get_average(self):
        if len(self.elements) == 0:
            return 0
        return mean(self.elements)

    def get_median(self):
        if len(self.elements) == 0:
            return 0
        return median(self.elements)


class EEGSeries:
    def __init__(self, eeg_channels, series_length):
        self.time_series = {}
        self.last_stamp = None
        for channel in eeg_channels:
            self.time_series[channel] = WindowedSeries(series_length)

    def add(self, eeg_data):
        if self.last_stamp is not None and (eeg_data.creation_time - self.last_stamp).total_seconds() < 0:
            print('Data from past: ' + str((eeg_data.creation_time - self.last_stamp).total_seconds() * 1000))
            return
        else:
            self.last_stamp = eeg_data.creation_time
        channels = eeg_data.get_channels()
        for channel in channels:
            self.time_series[channel].add_element(eeg_data.get_channel_value(channel))

    def get_median(self, channel):
        return self.time_series[channel].get_median()


class EEGConverter:
    def __init__(self, converter):
        self.converter = converter

    def convert(self, data):
        converted_data = {}
        for channel in data.data_per_channel.keys():
            converted_data[channel] = self.converter.apply(data.data_per_channel[channel])
        return EEG(converted_data)

Implementing The Muse Band Handler

To communicate with the Muse band, I introduced multithreading to ensure the main thread was not blocked while getting the device's data.

As I have implemented the Observer design pattern by introducing listeners, the other parts of the code are not dependent on the used device, which means we can easily add support for new devices.

After we start the Muse plugin, it starts listening on the given UDP port to get the data from the EEG band via pythonosc.

from pythonosc import dispatcher
from pythonosc import osc_server
from eeg_commons.eeg_commons import EEG, Gyroscope, Accelerometer, EEGChannelMapping, EEGChannel
from threading import Thread

addresses = []


class MuseEEGChannelMapping(EEGChannelMapping):
    def __init__(self):
        super(MuseEEGChannelMapping, self).__init__()
        self.add_mapping(0, EEGChannel.TP9)
        self.add_mapping(1, EEGChannel.AF7)
        self.add_mapping(2, EEGChannel.AF8)
        self.add_mapping(3, EEGChannel.TP10)
        self.add_mapping(4, EEGChannel.AUX)


MUSE_EEG_CHANNEL_MAPPING = MuseEEGChannelMapping()


class MuseEEG(EEG):
    def __init__(self, *args):
        super(MuseEEG, self).__init__(EEG.create_eeg_data_map(MUSE_EEG_CHANNEL_MAPPING, args[0]))


class Muse:
    eeg_channels = [EEGChannel.AF7, EEGChannel.TP9, EEGChannel.TP10, EEGChannel.AF8, EEGChannel.AUX]

    def __init__(self, ip, port):
        self.ip = ip
        self.port = port
        self.listener_thread = None
        self.server = None
        self.listeners = {}

    def add_listener(self, data_type, data_arrived_func):
        if data_type not in self.listeners.keys():
            self.listeners[data_type] = []
        self.listeners[data_type].append(data_arrived_func)

    def notify_listeners(self, data):
        if data.type in self.listeners.keys():
            for callback in self.listeners[data.type]:
                callback(data)

    def handler(self, address: str, *args):
        if address.endswith('eeg'):
            self.notify_listeners(MuseEEG(args))

        if address not in addresses:
            addresses.append(address)
            print(address)
        raw_entry = str(address) + ':'
        for arg in args:
            raw_entry += "," + str(arg)
        # print(raw_entry)

    def start_muse_listening(self):
        disp = dispatcher.Dispatcher()
        disp.map("/*", self.handler)
        print("Connecting to  " + self.ip + ":" + str(self.port))
        self.server = osc_server.ThreadingOSCUDPServer((self.ip, self.port), disp)
        print("Connected")
        self.server.serve_forever()

    def start(self):
        self.listener_thread = Thread(target=self.start_muse_listening, daemon=True)
        self.listener_thread.start()

    def stop(self):
        print('Shutdown OSC server')
        self.server.shutdown()

That's it. With these few dozens of lines of code, we can get all the data from the Muse EEG band.

Let's talk about more exciting things.

Detecting and Classifying Eyeblinks

Usually, eyeblinks are considered artifacts that should be removed to have an artifact-free EEG for processing, but in our case, this is the only relevant information.

The eyeball acts as a dipole with a positive pole oriented anteriorly (cornea) and a negative pole oriented posteriorly (retina). Thanks to this, it highly affects our EEG data.

Here are the different types of blinks and how they appear in our EEG diagram. Normal eyeblink:

Short eyeblink:

Long eyeblink:

I have even created a short video demonstrating how detected brainwaves change when we do things like moving our eyes, blinking, and clenching our jaw.

The detection algorithm is straightforward. After some observation, I realized eyeblink results in a considerable drop, then a slight rise in the EEG signal and the time between the fall and the rise is the length of the eyeblink.

Here is the detection code:

    def detect_blink(self, data):
        self.eeg_series_lock.acquire()
        base_level = self.eeg_series.get_median(CHANNEL_USED_FOR_DETECTION)
        self.eeg_series_lock.release()
        channel_value = data.get_channel_value(CHANNEL_USED_FOR_DETECTION)
        if channel_value > self.max:
            self.max = channel_value
        if (channel_value < base_level - BLINKING_START_FALL) and (self.blinking_start_time is None):
            self.blinking_start_time = datetime.datetime.now()
            if self.pause_timer is not None:
                self.pause_timer.cancel()
        if (self.blinking_start_time is not None) and (channel_value > base_level + BLINKING_STOP_RISE):
            blinking_end_time = datetime.datetime.now()
            blink_length = (blinking_end_time - self.blinking_start_time).total_seconds() * 1000
            blink = BlinkDetector.classify_blink(blink_length)
            for callback in self.blink_listener_callbacks:
                callback(blink, blink_length)
            if blink == Blink.VERY_LONG_BLINK:
                # Resetting conversion
                self.blinks.clear()
            else:
                self.blinks.append(blink)
            self.blinking_start_time = None
            if blink == Blink.SHORT_BLINK or blink == Blink.LONG_BLINK:
                self.pause_timer = Timer(1, self.pause_detected, args=['Pause detected'])
                self.pause_timer.start()

After having the eyeblink, I can classify them based on their length. I have experimented with different lengths of blinks, and I have defined the thresholds based on that.

There are the normal blinks which are very short. There are short blinks that are a little bit longer than the natural eyeblinks.

Then comes the long blink and the very long blink.

Here is the code for the classification:

    def classify_blink(blink_length):
        if blink_length < NORMAL_SHORT_BLINK_BORDER:
            blink = Blink.NORMAL_BLINK
        elif blink_length < SHORT_LONG_BLINK_BORDER:
            blink = Blink.SHORT_BLINK
        elif blink_length < LONG_VERY_LONG_BLINK_BORDER:
            blink = Blink.LONG_BLINK
        else:
            blink = Blink.VERY_LONG_BLINK
        return blink

That was it. As you can see, there is no magic here. I did not even use Fourier transformation as it was unnecessary for this first step, but I will definitely introduce it soon.

We have almost all the logic in place, and we can start implementing our mobile app using Kivy. But before that, let's sketch our UI.

Sketching the UI

Whenever I have to draw a diagram, create a UI mock, or create a mind map, my one-to-go tool is draw.io.

Draw.io is free, and it contains many flexible elements you can use to create whatever you want.

So here is my mockup:

Finally, we can start using Kivy to implement our UI.

Implementing the UI using Kivy

In Kivy, layouts are used to arrange widgets within a component. If you have ever worked with a frontend framework, you probably already know these.

I have experience with C#, Java Swing, and Windows Forms regarding the frontend. Most of them are outdated by now, but most of the frontend frameworks have similarities.

We split the main widget into an upper and lower part using BoxLaxout. The upper part is also a BoxLayout which will contain the two Labels and TextInputs. Again, if you have ever worked with a frontend framework, you are already familiar with most of the widgets which can be used. At least I am pretty sure you used labels and text input fields.

The bottom panel has a GridLayout, containing all the Morse code-letter pairs functioning as a dictionary to aid communication.

The UI can be created using Python code or Kivy's design language kv.

I have created my user interface using Python code. Here it is:

class MainWidget(BoxLayout):
    def __init__(self, **kwargs):
        super(MainWidget, self).__init__(**kwargs)
        self.orientation = 'vertical'
        self.morse_code = ''
        self.converted_text = ''
        Window.clearcolor = (1, 1, 1, 1)
        self.top_panel = BoxLayout(orientation='vertical', size_hint=(1.0, 0.5))
        self.padding = (15, 15, 15, 15)
        self.color = (1, 1, 1, 1)
        self.orientation = 'vertical'
        self.add_widget(self.top_panel)

        self.morse_code_label = Label(text='Morse code', font_size=NORMAL_FONT_SIZE, size_hint=(None, 0.1),
                                      halign='left', color=(0, 0, 0, 1))
        self.top_panel.add_widget(self.morse_code_label)

        self.current_code = TextInput(multiline=False, font_size=NORMAL_FONT_SIZE, size_hint=(None, 0.1))
        self.current_code.readonly = True
        self.top_panel.add_widget(self.current_code)

        self.output_text = Label(text='Text output', font_size=NORMAL_FONT_SIZE, size_hint=(None, 0.1),
                                 halign='left', color=(0, 0, 0, 1))
        self.top_panel.add_widget(self.output_text)

        self.text_output = TextInput(multiline=True, font_size=NORMAL_FONT_SIZE, size_hint=(1.0, 0.7))
        self.text_output.readonly = True
        self.top_panel.add_widget(self.text_output)

        self.bottom_panel = GridLayout(size_hint=(1.0, 0.5), cols=6, rows=6)
        self.add_widget(self.bottom_panel)
        for name, member in MorseCode.__members__.items():
            if name.startswith('N_'):
                text = member.code + ' ' + name[2:]
            else:
                text = member.code + ' ' + name
            print('text: ' + text)
            self.bottom_panel.add_widget(Label(text=text, font_size=LARGE_FONT_SIZE, color=(0, 0, 0, 1)))

And here is the result:

It could look better, but as my main goal is to create a useful open-source app, it is completely fine for me. It does what it should do.

We only have one final step to finish our application. We have to implement the eyeblink to text conversion and display it on the UI.

Implementing Eyeblink to Text conversion via Morse Code

Here is the Morse code enum:

class MorseCode(Enum):
    A = ('a', '.-')
    B = ('b', '-...')
    C = ('c', '-.-.')
    D = ('d', '-..')
    E = ('e', '.')
    F = ('f', '..-.')
    G = ('g', '--.')
    H = ('h', '....')
    I = ('i', '..')
    J = ('j', '.---')
    K = ('k', '-.-')
    L = ('l', '.-..')
    M = ('m', '--')
    N = ('n', '--')
    O = ('o', '---')
    P = ('p', '.--.')
    Q = ('q', '--.-')
    R = ('r', '.-.')
    S = ('s', '...')
    T = ('t', '-')
    U = ('u', '..-')
    V = ('v', '...-')
    W = ('w', '.--')
    X = ('x', '-..-')
    Y = ('y', '-.--')
    Z = ('z', '--..')
    N_1 = ('1', '.----')
    N_2 = ('2', '..---')
    N_3 = ('3', '...--')
    N_4 = ('4', '....-')
    N_5 = ('5', '.....')
    N_6 = ('6', '-....')
    N_7 = ('7', '--...')
    N_8 = ('8', '---..')
    N_9 = ('9', '----.')
    N_0 = ('0', '-----')

    def __init__(self, character, code):
        self.character = character
        self.code = code

    @classmethod
    def get_character(cls, morse_code):
        for name, member in MorseCode.__members__.items():
            if member.code == morse_code:
                return member.character
        return None

The conversion happens the following way:

If we detect a short blink, we convert it to a "." and if we have a long blink, we convert it into a "-" character. As soon as we do not detect a blink for 1 second, we transform our Morse characters into a letter or a number and display it in the "Text Output" widget.

If we detect a very long blink of 1,2 sec or more, then we delete the last converted character. Believe me, with the current state of the app, you will use this quite often. 😊

Here is the code:

    def blink_detected(self, blink, blink_length):
        print(str(blink) + ' with length: ' + str(blink_length))
        if blink == Blink.SHORT_BLINK:
            self.morse_code += '.'
        elif blink == Blink.LONG_BLINK:
            self.morse_code += '-'
        elif blink == Blink.PAUSE:
            try:
                char = MorseCode.get_character(self.morse_code)
                if char is not None:
                    self.converted_text = self.converted_text + char
                    print('Converted "' + self.morse_code + '" to ' + char + ' full text: "' + self.converted_text + '"')
                self.morse_code = ''
            except AttributeError as e:
                logging.critical(e, exc_info=True)
                print('Invalid Morse code: ' + self.morse_code)
                self.morse_code = ''
        elif blink == Blink.VERY_LONG_BLINK:
            self.morse_code = ''
            self.converted_text += 1
        Clock.schedule_once(self.update_ui)

There is no magic here, except in the last line. It is needed as the UI cannot be updated from an arbitrary thread. Our EEG handler runs on a separate thread, so the last line schedules the call of our UI update with zero delays. As soon as there are no other jobs in the queue, our UI will be updated.

We are ready with the development so it is high time for the demo.

The Demo

I could say the demo did not go well, but that wouldn't be true. I wanted to demonstrate the current state of the blinkish to textish app. As you can see from the video there is space for improvement. I already have many ideas but in case you have too, do not hesitate to contact me.

Here is the result of 3 weeks of work:

We have only one step remaining, which is packaging our app to have an Android app.

Creating Our Android App

Here comes the beauty of Kivy:

You have to write only one application, and you can generate an app for Android, iOS, macOS, and Windows.

As I am developing on Windows and as I have an Android phone, my choice is to make an Android package (APK).

There are multiple ways to do that:

• Using Buildozer
• Packaging with python-for-android
• Packaging your application for the Kivy Launcher

According to the documentation, Buildozer is the easiest. You can find all the info here regarding packaging.

Just follow the instructions, and you will have an app in no time.

I have included the necessary steps in the Readme.MD file of the project.

You can find the project on my GitHub.

Huh. That was quite a ride, but I have good news:

That's all, folks. We are completely ready with our application. We are not just ready, but we implemented a mobile/desktop app using only pure Python. I think this can be called "Implementing a mobile app the Pythonian way." Or, because I am not too good in Python yet, I would call it "Implementing a mobile app the Pythonianish way".

Before we leave, let's talk about my plans for the future.

Plans for the future

I have not overthought the future as I was focusing on the present, but here are some ideas I came up with:

• Instead of using hardcoded values for blink classification, a training feature could be introduced which guides you through the process of doing eyeblinks with different lengths. Based on this info, you can immediately start using the app with little or no error, and later when you get used to it, you can calibrate again to achieve a better speed.
• Make the application more robust by filtering artifacts like jaw movement and eye movement.
• Modify pythonosc, or implement our solution to grab the OSC data streamed by Mind Monitor to access the timestamps based on which we can rearrange the samples.
• Making a more robust solution by analyzing only the relevant part of the frequency spectrum using Fourier transformation.
• Using data like eye movement, gyroscope, and accelerometer to implement a much faster brainwave to text solution.

That's all, folks. I hope you enjoyed it.

I would love to hear from you. Whether you are just thinking about starting your own brainwave-based BCI project or have already developed something, just contact me and let's have a friendly chat. I am pretty sure both of us can benefit from that.

P.S.: Something good will happen to you today!

Hackernoon interviewed me, so if you would like to learn more about me, just click here and read it!

Become an agileish superhero!

Learn how to memorize anything in the world. In this series, I teach you everything I know about learning and memorization, including memory palaces, marker images, number memorization techniques, associations, etc.

You can already find the first videos on my Youtube channel in which I show you that it is possible to memorize such boring things as positions of circles.

Don't forget to read How You Can Become An Agileish Super Learner AKA How You Can Become A Super Thinker AKA The Proof Of Concept (POC) before you watch the videos.

Join the Agileish Superheroes Facebook group to learn memorization techniques, thinking techniques, agility, reading and learning techniques and also to get notified about new live sessions and videos

As I am a crazy person, I have open-sourced my life on GitHub on Fool's day.

I am sharing my thoughts, writings, and creations, and as I am frequently committing, I have open-sourced my thinking process, my writing process, and also my creation process.

Just click here to check my open-sourced life on Github!

My credo: The Mystery Of The Supposedly Red Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet

Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humor, and I am also happy to tell you that this is my article about which I am the proudest of now.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to, on Hackernoon and even on Instagram.

• Minnie: What do you have for today?
• Miki: Nothing.
• Minnie: Nothing nothing?
• Miki: It is so nothing it is not even nothing.
• Maudience: Stop it. We are losing our readers!
• Miki: But there is nothing else to read here.
• Maudience: Fair enough.

Participate in the Craft Conf giveaway!

I just realized most of you are busy with writing your submission to Hashnode Writeathon. The deadline has been extended by one week, so you can participate in both the Writeathon and the Craft Conf giveaway too.

The new deadline is 25th of May.

I am looking forward to your article.

P.S.: Something good will happen to you today!

UPDATE 2: As most of you are most probably busy with writing an article for the Hashnode Writeathon the deadline has been extended by one week, so the new deadline is the 25th of May.

• Nikolai: What is this bul.shit again? -Miki: This is not bul.shit, this is one of the biggest conferences about software development.
• Nikolai: YAC!
• Miki: What does YAC mean?
• Nikolai: Yet another conference.
• Miki: YAC!
• Nikolai: My YAC?
• Miki: My YAC!
• Nikolai: What YAC?
• Miki: This YAC.
• Maudience: Guys! Stop it! We are losing our readers!
• Nikolai: So what does your YAC mean?
• Miki: Yes, Another Conference!
• Nikolai: But this is your third conference this year. Just recall the first conference about the Future of Testing framework. That was a huge disappointment.
• Miki: You are right, we heard almost nothing about the future, but it was still very valuable. Anyway, do you remember Reinforce AI? That was a great conference.
• Nikolai: Sure. I have been waiting to give me life since you wrote Would You Freak Out If You Could Talk To Dead People? - Miki Szeles's Report on Reinforce AI Conference.
• Miki: Who knows, maybe in the future when you will have enough digital footprint. I might resurrect you then.
• Nikolai: I have to admit, it was a very eye-opening conference, even I enjoyed it, but how can you tell based on that Craft Conf will be a great conference?
• Miki: There were multiple successful Craft Confs during the last years.
• Nikolai: Ok, but is there anything else,?
• Miki: Sure. There will be more than 70 talks.
• Nikolai: 70+? That is crazy.
• Miki: Yep. 70+ talks from experts from all around the world.
• Nikolai: You almost convinced me to visit the conference, but is there anything else with which you can come up?
• Miki: Sure. This conference is organized by Felhő, Anna, Médea, Károly, Barna, Vanda, Viktória, Anna, Renáta, Fanni, Bianka, Réka, Kata, Barbara, Veronika, Vivien, Marcel, Martin, Emilía, Kristóf, Gergő and László. Nikolai: Who are they? Miki: They are the people behind CraftHub, the organizer of the Reinforce AI conference.
• Nikolai: Ok, that conference was pretty cool. I was amazed at where AI is at the moment. You convinced me. Where is my ticket?
• Miki: Ok. If you want your ticket right now, just click here, and you can buy a ticket at a 20% discount.
• Maudience: Can our readers use this link too?
• Miki: Yeah, sure. But I do advise them to keep on reading.
• McMuck: Are they paying for this article? You should definitely ask a huge some for this.
• Miki: Not for this article, but I made an agreement with CraftHub regarding other articles.

• Nikolai: So why do you write this article?

• Miki: I want to make a giveaway to reward our readers. My plan was to offer 3 tickets from mine, but they were so nice they gave 3 tickets for this giveaway.

• Nikolai: Cool. Will you be at the conference personally then?
• Miki: Yep.
• Nikolai: Can I go?
• Miki: All of us will go, which means 30+ characters.
• McMuck: We will go bankrupt. Do we have to pay for tickets for all of us?
• Miki: Easy, McMuck. Easy. We will be disguised.
• McMuck: So we create a wooden horse, and all of them will get into it?
• Miki: No, we will look like one normal person.
• McMuck: Who?
• Miki: We will look like as Miki Szeles 😊
• McMuck: Huh. We are saved.
• Nikolai: Ok, so can we get back to the conference?

• Miki: Sure.

• Nikolai: So, we have decided we will go. I do believe it is time to make our schedule.

• Miki: You are right. How will we create our schedule?
• Maudience: Don't worry, Anna from CrafHub provided a Google Spreadsheet containing the schedule, so based on that and our readers can easily create their schedule too.
• Miki: Cool. Where is it?
• Maudience: It does not exist yet.
• Miki: What?
• Maudience: I will need 1-2 hours to do that.
• Miki: But we will lose our readers by then.
• Mikaru: Do not worry. I brought here a great Japanese anime. I am pretty sure they will stick to the screen.
• Miki: Oh. I think I know what you will bring. You will get the anime which inspired me to play go back then.
• Mikaru: Exactly. It is the Hikaru No Go anime. The whole series is available on Youtube. Click here to watch it.

Creating Our Schedule

• Manality: I am back.
• Miki: Wow. You have finished in 10 minutes. Cool.
• Manality: I have not finished.
• Miki: What? But I wrote a script for you to collect the talks and the names.
• Manality: That is true, but I have not found any schedule on the homepage,
• Miki: Ouch. What will we do then?
• Minnie: I have an idea!
• Miki, Nikolai, Manality: Hello Minnie!
• Minnie: Hi. Sorry for being late. I just had the data analysis class taught by experts from Dmlab at the Budapest University of Economics and Technology (BME).
• Miki: Cool. What have you learned?
• Minnie: I learned about time series, but to be honest, I could not focus as Meadline pushed me to do my work as the deadline was very close.
• Maudience: Minnie, guys! Focus. Focus. You know, our audience...
• Miki: We know, Maudience. We know.
• Minnie: So we can write the end of the article, and as we will meet Anna today, we can ask for a schedule from here.

• Miki: Cool. Then let's write the Giveaway section.

• Miki: I have finished with the giveaway section. By now, you can find the schedule on the Craft Conf homepage, and we also got the spreadsheet.

• Minnie: Cool.
• Miki: DJMic! Can you please provide us with some music.
• DJMic: Sure. This time I brought a world-class Hungarian band.
• Miki: Cool. Who are they? The Carbonfools?
• DJMic: This time, I will play Paddy and The Rats.
• Miki: I know them. I love it. I love pirates since I played Pirates back then on my C64 and PC.
• DJMic: Me too. Just click here and start the planning!

Really Creating Our Schedule

• Miki: Just one note before we start. The schedule might slightly change, so I advise you to check the conference's page a few days before the conference to avoid unpleasant surprises.

Just click here, make your own copy, and you can already start your planning.

• Minnie: Cool. Let's start.
• Miki: There will be 4 offline stages: Main stage, Platform 2, Blue stage, and Green stage. The green stage is different from the others as that is hands-on, which means you can make your hand dirty by writing code.

There will be 2 online stages Pink stage and the Red stage. As the speakers are from all around the world, not all of them can travel to Hungary so that they will have a virtual talk.

• Miki: There will be 3 speakers I know. I know Micheal Feathers and Dan North as they were already very famous back then before my Udemy course era (I am learning almost everything related to software development from Udemy courses). And I know Ivett Ördög personally.
• Minnie: Holy moly! Michael Feathers, Daniel Terhorst-Nort and Ivett Ördög at the same conference. I hope we can visit all three. Can we?
• Miki: Yes, luckily, there is no overlapping. All of them will be on the 3rd of June. Here are the talks in CET time:
• 11:25-12:10: Team Autonomy and the Capability-Aware Organization by Michael Feathers - Platform 2
• 13:40-14:25: Rethinking Transformation by Daniel Terhorst-North (VIRTUAL TALK)
• 16:40-17:25: How to sell a big refactor or rewrite to the business? by Ivett Ördög
• Minnie: Oh. Dan North will have a virtual talk. That is almost the same as watching it later from recording.
• Miki: You are right. We might choose a different topic. We will see.
• Minnie: I am especially happy about Ivett's talk as we had a conversation recently about testing and business, and selling a refactor was also mentioned, of course.

• Maudience: Guys! We are losing our readers. Move on!

• Miki: The first talk will be Non-Functional Coding by Kevlin Henney. As there will be no other talks, it is an easy choice. The table is quite colorful, so I will use cyan color to highlight the selected one.

From 10:50, there will be 6 talks:

• Squaring the circle - mastering the next level of architectural design by Uwe Friedrichsen
• Driving effective Prioritization for optimal business outcomes by Smruti Patel
• Taking the 737 to the MAX! by Nickolas Means
• Domain-Driven Design and Team Topologies: Architecting for Fast Flow by Nick Tune & Zsófia Herendi
• 5 Things I Wish I'd Known Sooner About Scaling Teams by Meri Williams (VIRTUAL TALK)

• Dantotsu Radical Software Quality Improvement by Fabrice Bernhard (VIRTUAL TALK)

• Minnie: What a pity we cannot listen to all of them.

• Miki: Don't worry, all the talks will be recorded, and they will be available to all the participants.
• Minnie: Cool. So which will we choose?
• Miki: It is not an easy choice. Some names are quite mysterious, like "Taking the 737 to the MAX!" but I guess it is about the Boeing 737, but I can be totally wrong, of course.
• Minnie: So will we listen to that?
• Miki: Looking at the five talks, "Dantotsu Radical Software Quality Improvement" by Fabrice Bernhard is the most relevant in our current situation.
• Minnie: Why?
• Miki: As you know, I work as a test automation engineer, so ensuring quality is my number one prio.
• Minnie: I would like to listen to "Domain-Driven Design and Team Topologies: Architecting for Fast Flow" by Nick Tune & Zsófia Herendi, especially as there will be a Hungarian speaker.
• Miki: You can watch the record later.
• Minnie: Oh, you are right. I almost forgot about that. So what will we listen to from 11:55?

• Miki: As Nick Tune & Zsófia Herendi talk is longer, there will be 5 talks:

• Balancing Coupling in Software Design by Vladik Khononov

• Applying Friction for Development Productivity with Circuit Breakers by Frank Chen
• How To Build Your Own Heroku in 2022? by Viktor Farcic
• Micro-Frontends anti-patterns by Luca Mezzalira (VIRTUAL TALK)

• When life gives you Orange, make data speak volumes! by Drishti Jain (VIRTUAL TALK)

• Minnie: I've seen the Heroku name so many times in the last few months, so I would like to listen to that.

• Miki: I think in order to get the most out of this talk, we should have basic Heroku knowledge, so maybe next time.
• Minnie: Which will be then?
• Miki: After reading Frank Chen's bio, it is a clear choice:

  At Slack, Frank focuses on making engineers' lives simpler, more pleasant, and more productive in the Developer Productivity group.

They have a productivity group which is fantastic. I have fallen in love with the idea of a productivity team since I heard Kathryn Koehler's talk. in which she explains Netflix has a productivity engineering team that is focusing on helping other teams to be more productive.

I hope sometime in the future there will be such a team in my employer's company. It is a little bit similar to the automation engineer idea about which I was talking in To Test, or Not to Test, That is Not The Question Reloaded - AKA Why You Should Replace Your Automated Tests With Manual Tests.

• Minnie: So, what's next?
• Miki: Lunch.
• Miki: I am hungry too, but I meant what will come in the schedule.
• Miki: Lunch.
• Minnie: Stop it, Miki. It is not lunchtime yet.
• Mictor: I am hungry too. Where is my mustard?
• Miki: No! No! I mean lunch is the next part of the conference.

• Minnie: 🤦‍♀️

• Miki: So let's continue. Here are the talks from the next etap:

• Stop Focusing on Tech Debt by Aviv Ben-Yosef

• Open Source Security: The World Needs Our Help by Eric Brewer
• Delivery through Retrospection for Improvement by Anjali Leon & April Jefferson
• Loosely or lousily coupled? Understanding communication patterns in microservices architectures by Bernd Rücker (VIRTUAL TALK)

• Engineering for Software - How to Amplify Creativity by Dave Farley (VIRTUAL TALK)

• Minnie: Which one will be your selection, Miki?

• Miki: You know, Minnie, one of my goals is to become more creative, so I will listen to Dave Farley's "Engineering for Software - How to Amplify Creativity".
• Minnie: Cool.
• Meadline: I am sorry for the interruption, but it is time to stop this planning part and talk about the giveaway as we have to post this article today, and we also have to develop a mobile app and write an article about it in order to participate in the Hashnode Writeathon. The deadline is only 4 days away.
• Miki: Ok. Let's talk about the giveaway.

The Craft Conf Giveaway AKA Your Chance To Win an Online Craft Conf Ticket

Dear fellow (wannabe) Bloggers!

I would like to inspire you for writing articles, so I have decided to have a giveaway in which you can win a ticket for the Craft Conf 2022.

I do not believe in luck, so I will personally select the winners.

There are 3 categories in which you can participate:

1. Funniest technical article. Writing is fun, reading should be fun too. I would like to awaken the technicalish writer in you.
2. Most inspiring article. I was inspired multiple times by your writings, so I would like to encourage you to continue posting new valuable content.
3. Any other article. I do not want to exclude any type of article, as all of them are valuable. In the worst case, if nobody reads it, it is still valuable for the writer as you can learn a lot by writing about a topic.

You can participate with multiple articles.

The selection process will be sobjective, which means it will be subjective as there is no single person in the world who can be totally objective, and it will be objective as my whole team will evaluate the articles, which means 30+ different viewpoints.

Rules of participation:

1. You have to write and publish an article.

In case you have no blog yet, I highly advise using Hashnode because I do believe this is the best blogging platform for software developers. Both for reading and writing high-quality, valuable articles. I highly recommend reading my summary of my first month on Hashnode: My First Month on Hashnode - A Retrospection About Blogging on Hashnode Developer Journaling Platform by Miki Szeles.

Here is my Hashnode referral link. I do not get anything if you use it (I am already a Hashnode Ambassador), but it would be motivating to see how many people I inspired to start Hashnode blogging.

The article's title has to end with "AKA Craft Conf Giveaway Participation".

The deadline for the submission is the 25th of May.

I will share all participating articles on my LinkedIn and Twitter.

1. In case you will be selected as a winner, you have to write a 1000 words article about the conference in exchange for the ticket. It can be a general article or an article about one or more talks. I need this as that was the agreement between CraftHub and me. I will share the article on my LinkedIn and Twitter, and CraftHub will also share it.

2. In order to participate, you have to comment the following sentence under this article:

"I am participating in the Craft Conf giveaway, and I will write a 1000-word article about the conference if I win."

How will I find your article

I will follow everyone who is commenting the above-mentioned sentence under this article if they are from Hashnode, dev.to, or medium.com, as I can only follow you on a platform where I am registered.

I highly recommend posting the link here for 2 reasons:

1. To make sure I won't miss it
2. Others can also find and read your article.

Dear Syed Fazle Rahman, Gyanesh Samanta, Bhagya Kithmini, Saroj Behera, Lorena Gongang, Sparkful Studios, Cynthia Mwihaki Kamau, Sylvia F., Dipankar Medhi, Roshaan, Swati Sarangi, Opemipo Disu, Designegy Creatives, AliciaBytes, Joaquim Da Costa, Eleftheria Batsou, Kim Minori, Yuri Lee, Devhouse, Rafael Câmara, Deepa Goyal, Paloma, Jewel 💎 , Yoshi, Carlos Balbuena, Pacifer York, Ji Ho Yoo, Angela Ni, Maxi Contieri, Diego Ballesteros (Relatable Code), Atharva Shirdhankar, Mr. Bud, chryzcode.dev, Ahmed Ramy, Ebere Vivian , Victoria Lo, Amr Khaled, Chris Bongers, Kenya Carl, Alvin Karanja, Jinesh Shah, Jonathan Chirk, Chris Nunez, KobbyDom (Dominic Adomako Darko), Tosin Adewale, Alyssa Drum, Saurabh Suresh Powar, Brian Scramlin, Nwokocha Maruche, Fadya Joudah, Abdelmadjid Cherfaoui, Jorge Romero, Rajiv Verma, Alex Kates, Kamaljot Singh, John Amiscaray, Vinamra Jain, Samina, Geek Tech, Wampamba David, Richard Fernando, Jake LaCaze, Anosh Bhakare, Abhiraj Bhowmick, Marcin Wosinek, Sam Sycamore, Raghav Singh Gulia, Bence Hornyák! You already impressed me with your articles, so I would love to read more from you, especially as you just have to do what you would do anyway: Write insightful articles. 😊

Dear followers AKA dear Northon Barbosa, Leonardo Antonio Tovíaz López, Frederico Canoeira, Mehdi All, Rakshitha Prakash, Timothy Mayor, Joshua Omobola, Vaishnavi Dontha, Marah Nairat, Hafsa Jillani, Amberly Buys Gwin, Hope Davids, Hiram Moises Lugo Rodriguez, Vinith Kumar M, Tahseen, Ramakanth Putta, 💻🖱📺📟🕰🎛, Daniel Zietsman, Azza bahaa, 0yewale mustapha, Kozeem Hammed, Sathish Kanna, Мэндбаярын Цагаанбаяр, deepak reddy, 8MediaTech, Aurélien Bouteiller, Zully Chumpitaz, Kishore Beniwal, Razgui Wahiba, Varun Sen, Siva, Mark Julius Uy, Mostefa Terbeche, Dang Ky Bong88Xs, Edward Rowling, Haha, MANAS DEWARI, Basheer Garba, Kenny Yekeen, Jd King, Pam Botelho, Анна Скобелева, Shahnawaz Khan, Miki, light atelier, Udayraj Dhavande, Rizwan Riaz, Nguyễn Công Dũng, Sidu Ponnappa, Eval Exec, Charry G., Ron N, David Zheng, HASSAN MAKAOUI, Kevin Mulhall, Dorian Coleman, Benita Ogamba, T Kumagai, Moruf Tadese, Utkarsh Mishra, Jayjay Declaro, Tarek Ahmed, Cyberdevil, Deepa Goyal, samson ogunyemi, Lucas, Sajed Taha, mouna bassim, 65CE Ifat Jagirdar, Max Hegel, Artur Muradov, Korede Balogun, Ilxam Xaytmanov, Adel Ashraf, Gabriel Correia, Akinyemi Shalom, ABHISHEK SINGH, Servizio Civile Usellus, Michael Esoimeme, Olaoluwa Michael, duck melon, Adekunle Adedokun, Abdus Salam, Kenneth Nancy Chidera, TomTom Developers, Adewoyin Sodiq, Ayodeji Eluyemi, Ahmed Bolarinwa, Ioannis Katri, Theodor Abi-Mansour, Davide Tessari, Rohit Jaiswal, Freddy Sossa, elalfy mohamed, Matt Wilson, Tashfi Hossain, Saksham Kohli, Murad Akverdiyev, Riccardo Di Benedetto, Kasomelojr Mwadui, Nwamini Emmanuel Onyedikachi, corporate19 shivamkosta, Manav Gupta, Ayush Verma, Caroline, Tấn Hoàng, Ethan, xuanling11, Dimos Kolouas, Shivanand Prabhu, Pang Meng, BUSHRA NAZISH, Hussain Ahmed, Aliyu Baba, Richard Gichuki, Anushka Gupta, Krishna Arya, atiqah, atiqah, Sophie Tai, UI Lib, hubi, Ben Weese, Saima Afroz, Jenap User, Honeywildbear, maqibin, min-sam kim, Ridwan Kareem, Nuharu, Renan Franca, Abdelmadjid Cherfaoui, Julio Pochet Edmead, Henry, Oluwatobi Aruna, Shreya Tabjul, Aizaq Lee, kawaljeet gulati, Eddy, Saroj Behera, Astrologer Rahul Gaur, Abdallah Mahmoud Yousef Aqtash, Robert Ejiogu, Adith sanra, Milind Mishra⚡️, Saddam Hossen, Muhammad Bello, Saheed Adekunle, Mr. Louis, mahmoud elaraby, Ahmed Aziz, Noah Henry, Aghiles Lounis, Paloma, Lucy Karimi, Marco Gancitano, Joy Choudhury, Roshaan, Designegy Creatives, Franklin56, Manish Purohit, Vince Cheung, NOURADDIN ABDURAHMAN ADEN, sümeyye öndaş, Nikunj Shingala, Khaled Anas, The Distracted Mind, Lydivine Mugisha, Ngo Quang Nhat Duy, jephthah buabin, Murtaza Kanorwala, Yoshi, Franco Sampietro, Nelson Omondi, Ariyibi Baseet, Salman Shaikh, Den Sovan, Irshad Ali, L.O. Adienge, Raman Sharma, Jewel 💎 , ScienceKaari Singh, Devhouse, Sandeep Panda, Abanoub Ashraf, Andrei Tiburca, Maja Iwinosa Sanne Nche, lina julie, Rafael Câmara, Erick Larsen, Lenworth Roper, Farouk Badmus, Allison Villarreal, Raviteja Mannam, mostafa, Ji Ho Yoo, Hrishikesh Pale, Shiju, 見える, Allister Beharry, Christianah, Ganga K, Joshua Personal, Chukwuebuka Collins, Vienna Adiele, Muoki Nzangi, Tamás Szeles, Milan Sachani, Rajesh Sagayanathan, Ravikumar R, Gabriel Uzowulu, Rakesh, Hu LiHong, Merja Shourov, Dheeraj Choudhary, Yash Khanduja, Jym Cheong, Ahmed Essam, Gegi Pirtskhalava, victor umeh, Ranojit Kumar, Swati Sarangi, Tam Pham, Danquah Bernard White, Utsanjan Maity, Ka Fai, Thiyagarajan, Saurav Pati, Shively, Marco Neumann, Randy Knight, Ninotna, Tanishq Singh Anand, Joseph Wallace, Bojan Skrchevski, Rustam Niyazov, Balint, Derek Rodger, Yassine BENNKHAY, Zsolt Ilonczai, Szabolcs Retfalvi, Bruce Wells, Alemoh Rapheal Baja, Prashant Singh, Ahmed HZAMI, Mr. Bud, Sahesh, Vectorly, Ahmed Ramy, Péter Teszáry, Miss Rin, Chris Bongers, Favour Okunowo, Amr Khaled, Israel Santiago, Amanuel T, Rakisol Hembrom, Denis Cabrera, Ebere Vivian , Jorge Romero, Kaizen + Joy | 🦄1337code grinder, Moureen Caroline, Tosin Adewale, Chris Benjamin, KobbyDom (Dominic Adomako Darko), Alyssa Drum, naveenkumar j, Lizhiyu, Shai Almog, Saurabh Suresh Powar, Brian Scramlin, Victoria, Fadya Joudah, Rajiv Verma, Mahmoud Shabana, Raghav Singh Gulia, Wampamba David, Jake LaCaze, Bence Hornyák! You already honored me by following me, it would be awesome to read your articles.

I am looking forward to your articles.

NoShare: Dear Reader! In case you found this article boring and useless, then please do not share it as we do not like negative marketing.

But in all other cases please share it with your social media friends, so they can they might get inspired to visit the conference!

Cheers,

Miki

P.S.: Something good will happen to you today!

BECOME AN AGILEISH SUPERHERO!

Learn how to memorize anything in the world with me. In this series, I teach you everything I know about learning and memorization, including memory palaces, marker images, number memorisation techniques, associations, etc.

You can already find the first videos on my Youtube channel in which I show you that it is possible to memorise such boring things as positions of circles.

Don't forget to read How You Can Become An Agileish Super Learner AKA How You Can Become A Super Thinker AKA The Proof Of Concept (POC) before you watch the videos.

The next session's date is still under discussion, join the Agileish Superheroes Facebook group to learn memorization techniques, thinking techniques, agility, reading and learning techniques and also to get notified about new live sessions and videos

As I am a crazy person, I have open-sourced my life on GitHub on Fool's day.

I am sharing my thoughts, writings and creations and as I am committing frequently, I have open-sourced my thinking process, my writing process and also my creation process.

Just click here, to check my open-sourced life on Github!

My credo: The Mystery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet

Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humour, and I am also happy to tell you that this is my article about which I am the proudest of now.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to, on Hackernoon and even on Instagram. 😊

I have good news for you:

You can get rid of it completely.

And you can even write anything there. For example, you can write your job title in it, which might aid your SEO as search engines consider the URL a significant source of information.

So how can you do that?

1. Click the Me icon at the top of your LinkedIn profile!
2. Click the View Profile button!
3. Click Edit public profile & URL link!
4. Click on the pencil icon right after your URL!
5. Change your URL to whatever you like! I advise you to consider SEO, so to boost your search results, you should put all your keywords into it.
6. Click the Save button to save your new unique URL.

Thanks for reading!

Please hack your friends' lives by sharing this article with them and your social media friends.

Are you blogging on Hashnode? Yes? Cool. No? What are you waiting for? Hashnode is my number one blogging platform as a developer.

Please use my referral link to join Hashnode and become a Hlogger (Hashnode Blogger)!. I do not get anything for it as I already became a Hashnode Ambassador by referring 3 of my friends, but it would be awesome to see how many people I have inspired to start blogging. 😊

In case you want to understand why Hashnode is the best developer blogger platform, just read my My First Month on Hashnode - A Retrospection About Blogging on Hashnode Developer Journaling Platform by Miki Szeles harticle (Hashnode article)!

In case you are still not sure why you should start blogging, please read my harticle:
Start writing now! Seriously! is the first harticle in the series in which I share my learnings, which can be valuable for newcomers and advanced bloggers.

My credo: The Mystery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humour, and I am also happy to tell you that, this is my article about which I am the proudest of now.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to, on Hackernoon and even on Instagram. 😊

Contribute to the open-source Selenideium Element Inspector Chrome Extension, with which test automation teams can save hours daily by automatically generating all the relevant selectors for Selenide, Selenium, Cypress, Playwright, Squish and TestCafe.

Follow the Selenideium Element Inspector Twitter channel to get updated on the latest happenings regarding Selenideium, to get help, to share your experience and also to talk about any (test automation) related topic! 😊

Join the Selenide User Group on LinkedIn to connect with more than a hundred test automation engineers and learn and get help regarding the most astounding e2e test automation framework: Selenide.

Join the Selenideium Element Inspector Bounty Hunting Reward Program and earn ☕s by contributing to this open-source project. 🚀 This is the perfect opportunity to make the first step into open-source contributing, and also in case you would like to learn about JavaScript and Chrome extension development. 😊

I am building a friendly, supportive, knowledgeable community around Selenideium. I did not dare to contribute to any open source project for a very long time. I was afraid that the developer community would take my code and myself into parts. And to be honest, seeing the sad fact that there are rude and ignorant people in the dev community too, most probably that is what has had happened back then.

This is why I guarantee that Selenideium Element Inspector is the perfect project to start your open-source contribution; I will also make sure it will stay like that. No matter how genius you are, if you do not respect the community members, this project is not for you.

To show my gratitude and motivate you, I will invite you for ☕ for every contribution.

I will even give a shoutout to you both on Selenideium and on my personal Twitter accounts in case you contribute.

• Minnie: Where are you?
• Miki: I am here, I just bought popcorn, but I guess I only missed the ads.
• Minnie: Miki, the story is over.
• Miki: Whatttt?
• Minnie: That's it. We can go home.
• Miki: You are trying to trick me, Minnie.
• Minnie: I am not tricking you. Why do you think that?
• Miki: As Miki, Szeles wouldn't write any story which is shorter than at least half an hour.
• Minnie: Fair enough.
• Miki: However I should have known that based on the short title which is definitely not usual from Miki. What should we do now?
• Minnie: We should watch another story.
• Miki: Which one do you recommend?
• Minnie: Do you like science fiction? You know, robots, fremens, Skynet.
• Miki: Sure.
• Minnie: Then we should watch Miki Szeles's Adventures in The Field of Data Science - The backstory.
• Nikolai: No way, Miki. Self-promo again? Really?
• Mictor: Such professionalism.

too. Read more here: Migrating to Germany as a Software Developer Richard Gichuki is a young graduate from Kenya. He has a civil engineer background,d but he turned towards software development. You can find his introduction here: Civil Engineer to Software Developer

• Minnie: We are ready. That was a rather lengthy interview.
• Miki: Yeah, sure, but it was not as dry as the previous ones.
• Minnie: Miki, we still have a few sentences to say, but we already have 54 minutes. I think you will get the longest harticle on the Hashnode badge with it.
• Miki: It would be awesome. But there is a problem.
• Minnie: What is it?
• Miki: There is no such badge. Not yet. Not yet.
• Minnie: Miki, you cheeky bastard. Where is the link for the feature request?

• Miki: Here it is. Please upvote. 👍

• Minnie: It is already Tuesday, and you have not read a single harticle yet. Do you think you can still create Hashnode Weekly 006?

• Miki: I have high doubts. I am on holiday with my family, so I only have time while they are sleeping. Except for t for his time, I got a few extra hours yesterday to finish this article, but I did not make it.
• Minnie: So what is your plan?
• Miki: To post the Hashnode Weekly less frequently.
• Minnie: But don' you think our readers will be mad at us.
• Miki: It is possible, but I will make it somehow if they show their interest by reacting and commenting to this harticle.
• Minnie: And what if they won't like it?
• Miki: Then I guess I will be more strict and read fewer harticle.

• Minnie: Fair enough.

• Minnie: I have noticed you are constantly changing your style. Don't you afraid we will lose our readers?

• Miki: I don't want to persuade anyone to read my articles. There are so many spectacular fellow hloggers they can follow. This is who I am: a constantly moving target. I am always looking for improvements, so I have to experiment.
• Minnie: For example, you have this new conversational style. By the way, thanks for letting me speak too.
• Miki: It is my pleasure, Minnie. I like this format for multiple reasons.
• Minnie: What are they?
• Miki: First, I can show my thinking process to my readers, and I can also answer any questions which might pop into their minds.
• Minnie: Sound good. What is the other?
• Miki: It is much more probable that people are joining an existing conversation than contacting a speaker who is talking alone.
• Minnie: I see. I am still curious what our readers think about this new conversational style. So let's ask them. 3..2..1..Go!
• Miki, Minnie: Dear readers! Do you like What do you think about this new conversational style? Share your thought in the QA section!.
• Minnie: Why did you change the question?
• Miki: Because, in case you want a real conversation, you have to ask open-ended questions. Do not you think?
• Minnie: Yes, I think so.
• Miki: Do you see it?

• Minnie: Oh Miki, you tricked me again.

• Minnie: Miki, people are talking. I heard rumours you are working on a new series called Science for Kids (and for adults too).

• Miki: Yes, that is true. My 8-year-old son, Levi, inspired me.
• Minnie: But you are an adult. How will you talk to the kids?
• Miki: I am not an adult. However, I have grey hair. I am still a kid inside.
• Minnie: Me too. So what will you write about?
• Miki: I will teach the kids how to sort using the comb sort algorithm.
• Minnie: Why would kids be interested in sorting algorithms?
• Miki: As I won't talk about algorithms, we will play with Fifa 365 football cards.
• Minnie: Seriously? How?
• Miki: Haha. I won't tell. Just read my upcoming article.
• Minnie: Do you think you can make some change in education on your own?
• Miki: Of course, no. But I am pretty sure many of my fellow parents have at least one similar fable in their pocket.
• Minnie: Yeah. I also have one about Edward De Bono's six thinking hats.
• Miki: I am eagerly waiting to read your story.
• Minnie: We will get there too in a couple of weeks. But Miki, how will you make sure we can find other people's posts on the internet?
• Miki: I would like to keep this series on Hashnode, but as there is no "Science for Kids" tag yet, I have created a feature request. Please upvote!. 👍
• Minnie: What about parents who do not want to use Hashnode?
• Miki: Then they should use the #scienceforkids hashtag.
• Minnie: Ok. And what about parents who do not know how to write or publish an article?
• Miki: I will happily help them. They can contact me via Facebook.

• Minnie: I think that is the perfect thought with which we can close this conversation.

• Minnie: I see you have created the cover illustration already. Can we publish the article?

• Miki: Well. We have a little problem.
• Minnie: What is it?
• Miki: Do you remember we have employed a writing expert Grammarly Premium to raise our writing quality to the next level?
• Minnie: Yeah, I am pleased about that. So what is the problem?
• Miki: She made a few suggestions.
• Minnie: Nooo. How many?
• Miki: 619!!!

Thank you very much, dear readers, for joining us for today's Hashnode Weekly.

• Miki: Thank you very much too.
• Miki, Minnie: To make sure the whole world can read awesome harticles from fellow hloggers, I kindly ask you to share this post on social media!

WTF just happened?

• Minnie: Hey, Miki! What was this?
• Miki: These were the remainings of deceased the Hashnode Weekly 005.
• Minnie: No way. I can't believe this. Sorry for your loss Miki.
• Miki: Sorry for your loss Minnie.
• Minnie: What has happened?
• Miki: Do you remember we employed a new writing expert to raise our writing quality to the next level?
• Minnie: Sure. It was my suggestion.
• Miki: No, it was mine, but it does not matter. So after around 15 hours of writing, I ended up with a more 10000 words article with a more than 60 minutes read time. I think I broke the Guinness record of the longest harticle.
• Minnie: That is awesome. By the way, I think you broke your record, which you earned with Why You Always Have To Close Your Article With A Call To Action AKA A Brief Introduction To Hashnode Widgets By Miki Szeles. It had 42 minutes of reading time. I doubt there are any harticles longer than this.
• Miki: It is possible, Minnie, but I cannot be happy about this. I could cry.
• Minnie: What has happened exactly?
• Miki: Right after I finished writing Hashnode Weekly 005, I consulted with our writing expert Grammarly Premium, and she suggested more than 600 changes.
• Minnie: Wow. That is brutal.
• Miki: Yeah. So I started to quickly check them one by one and approve most of them. Then when there were only around 50 remaining suggestions, I went to preview mode to check how it looked, then I realised a tragedy had happened.
• Minnie: What kind of tragedy?
• Miki: Our good old Grammarly mother deleted 95% of my harticle.
• Minnie: No, waaaay. Why did not you use the undo operation?
• Miki: Cause Hashnode does not save the change history when you switch between writing and preview mode.
• Minnie: What a pity. Have you.
• Miki: Yes, here is the feature request link. Please upvote! 👍
• Minnie: Wow, Miki. You can see into my mind.
• Miki: Well, we have a shared memory.
• Minnie: So true, Miki, so accurate. I am pretty sure you did not give up so quickly. So what else did you try? Miki: As I enabled GitHub backup, I went immediately to GitHub to realise articles are only saved when either you publish them or update them, but drafts are not saved at all. Here is the feature request. Please upvote! 👍
• Minnie: What else?
• Miki: I checked whether I could get it back from google cache.
• Minnie: I guess it did not work as it was not seen by google yet.
• Miki: Yeah, you are right. So I tried to get it back from the local Chrome cache. But that does not save history, so I could only get back to the latest state.
• Minnie: Anything else?
• Miki: Sure. I tried to hit the back button a few times. Maybe it would work, but it did not.
• Minnie: You tried hard, Miki.
• Miki: That is not all. I have searched on google maybe Windows 10 automatically backs up my files. But no, it does not back up the Chrome local cache. It would not make sense for most of the users.
• Minnie: Yeah, sure. I still have an idea.
• Miki: What is it?
• Minnie: You could contact Hashnode Support as they probably have a daily backup from which they can get back your draft.
• Miki: Already done. I contacted Eleftheria Batsou and Sandro Volpicella.
• Minnie: Then you are saved, Miki. They are very kind and helpful people.
• Miki: Yeah, I know, but they probably said they wouldn't be able to get it back, but they are still trying.
• Minnie: That is very nice of them.
• Miki: I think so.
• Minnie: Miki, I think we can still build a castle from this sh*t.
• Miki: How Minnie? How?
• Minnie: Don't ask, just follow me.
• Miki: Ok.
• Minnie: How many harticles did you collect last week?
• Miki: 77.
• Minnie: Wow. That might be a new record in the short but successful life of Hashnode Weekly.
• Miki: Yeah, it is possible?
• Minnie: And how many of them you featured.
• Miki: Zero.
• Minnie. What? People like featured articles, and people like being featured, as you let them know they have done something spectacular.
• Miki: That is true, Minnie, but I realised I like all the harticles, so instead of making a competition of this, I put articles into the spotlight.
• Minnie: Isn't this the same Miki.
• Miki: No, it is not.

Today in Spotlight 🔦: Jorge Romero

• Minnie: Umm. Okay. So who did you put into the main spotlight?
• Miki: Jorge Romero.
• Minnie: Why?
• Miki: That guy annoys me like hell.
• Minnie: Why, Miki? Why?
• Miki: He writes and posts a harticle each day.
• Minnie: Sorry, what?
• Miki: Let me repeat it. He writes a harticle each day.
• Minnie: OMG. But why does that disturb you?
• Miki: Cause I cannot bear being second.
• Minnie: Fair enough. Is there anything else annoying in him?
• Miki: Yes. He always has a unique cover image.
• Minnie: I see, but you also composite your cover images on your own to resonate with your writing.
• Miki: Yes, but this guy is drawing his cover images with his bare hands.
• Minnie: I can't believe that.
• Miki: It is valid for sure. Here is one of his articles: 01. Lygometry. He was figuring out what I don't know yet.
• Minnie: I have to admit that mushroom is gorgeous.
• Miki: On whose side you are, Minnie?
• Minnie: Of course, I am on your side, Miki. But I still love it. By the way, I tried to scan this harticle, but I couldn't understand half of it.
• Miki: That is another thing that annoys me like hell. This guy is knowledgeable in every topic in the world. In every topic.
• Minnie: I can believe that. Is there anything else that annoys you?
• Miki: Yeah, for sure. Every time I check Hashnode Top 10 on Discord, this guy is always there. Almost always.
• Minnie: I can understand, Miki. Why do you hate this guy?
• Miki: I hope you heard the irony in my voice!
• Minnie: Irony? Umm. Sure, Miki. Sure.
• Miki: And do you know what is the worst thing in this situation, Minnie?
• Minnie: Nope.
• Miki: I cannot be angry at him, as right after I have announced the Selenideium Element Inspector Bounty Hunting Reward Program, this guy immediately submitted a bugfix.
• Minnie: No way. How rude is that!
• Miki: Yeah, I think so. I know he only wants the ☕s
• Minnie: ☕s?
• Miki: Yeah, I invite anyone to a cup of ☕ who contributes to this project. I want to build a helpful community around this open-source project, so it is the perfect opportunity put your feet on the land of open source.
• Minnie: I want ☕s Miki. I will go and contribute to the project.
• Miki: You cannot even code in Javascript.
• Minnie: Not yet, Miki. Not yet. I think it is enough from Jorge Romero. Let's see who else can we hate this time.
• Miki: I don't hate anyone.
• Minnie: Me neither, Miki. Except sometimes you.
• Miki: Same here.

Today in Spotlight 🔦: Parvin Eyvazov and his band JSON-Translator.

• Minnie: So who was in the spotlight from the Software Development and Testing category?
• Miki: It was Parvin Eyvazov and his band JSON-Translator.
• Minnie: And what is JSON-Translator?
• Miki: That is an excellent tool with which you can translate your language JSON files to any language supported by Google Translate, which I guess means all the wording of the world.
• Minnie: Wow. Miki. That is pure awesomeness.
• Miki: I know Minnie. Damn, I hate this guy too. I wish it would be my project.
• Minnie: But wait, Miki. It can still be your project. This is an open-source project, so that you can contribute to it anytime.
• Miki: Fair enough. I even suggested to my colleagues to use it as, at the moment, our solution Adamos only supports English and German.
• Minnie: And?
• Miki: Well, I learned that we are employing a professional translator company as our texts are very domain-specific. But I will use it if I implement UI for Selenideium Element Inspector.
• Minnie: Any last words about JSON-Translator, Miki?
• Miki: Yep. I came up with a catchy title.
• Minnie: What is it?
• Miki: JSON Translator - Let your app speak to your users in their language - An AI-based solution.
• Minnie: The first part is catchy, but why did you write an AI-based solution?
• Miki: No matter how good your product is, nobody will give a sh*t in case you do not put the AI buzzword on it.
• Minnie: Fair enough, Miki. Fair enough.

Today in Spotlight 🔦: Hashnode Toolbox

• Minnie: As far as I remember, your second category is always "Writing, Blogging and Journaling".
• Miki: Yes, that is true.
• Minnie: So who is in the spotlight today?
• Miki: Hashnode Toolbox.
• Minnie: Hashnode what?
• Miki: I think you see why I am featuring them.
• Minnie: So what is Hashnode Toolbox?
• Miki: Did you know Hashnode has its writing team?
• Minnie: No way. I did not know that.
• Miki: Me neither up till I read Andrei Tiburca's Top 10 Free Blogging Platforms for Developers In-depth Review harticle. In the end, I saw it was published on Hashnode Toolbox, so I followed the white rabbit, and that is the story of finding Hashnode Toolbox.
• Minnie: Cool. Can you tell me precisely what it is?
• Miki: The Hashnode Toolbox is where a handful of writers share their favourite tools, conferences, books, courses, and more.
• Minnie: Such a lovely sentence.
• Miki: It is not my sentence, bro.
• Minnie: Sis. But where did you steal it from?
• Miki: From here.
• Minnie: I will be honest, Miki, there are dozens of similar sites on the internet. Why should I care about Hashnode Toolbox?
• Miki: Well, they even have a goal, which is not that usual nowadays.
• Minnie: What is it?
• Miki: To become the go-to resource for developers and people in tech. If you are looking for the best deals and getting the biggest bang for their buck when it comes to development resources, the Toolbox is the place to find them.
• Minnie: Fair enough. I am starting to love this team. Is it possible to join them? Who are they looking for?
• Miki: Yeah, sure. They are looking for hloggers passionate about technology and who is knowledgeable in writing and SEO.
• Minnie: Mikiiii. It seems like the perfect fit for us. We should apply.
• Miki: I already did. But I am afraid you cannot apply as there is a catch here.
• Minnie: What is it?
• Miki: You already have to have some high-quality harticles.
• Minnie: But Miki, we have already published 40 harticles so that I can apply.
• Miki: Listen, Minnie! How many articles have you published under your name?
• Minnie: Ummm. Zero.
• Miki: You got the point, right?
• Minnie: Mikki. Can you please lend me some article? I really would like to join the Hashnode Toolbox.
• Miki: We will solve Minnie. We will solve it.
• Minnie: Thanks, Miki. You are kind as usual.
• Miki: But be cautious. There is another catch here.
• Minnie: I knew it sounded too good to be true. What is it then?
• Miki: They pay $300/harticle.
• Minnie: Wait, what? $300/harticle for something I loves doing? I can't believe it. This must be some scam.
• Miki: I doubt it, but we will find out soon.

Today in Spotlight 🔦: Sylvia F. and the dyslexia

• Minnie: Miki, your next section is always Productivity, Psychology, Learning, Self-improvement, Time Management and Everything Else you Cannot Fit Into Other Categories. Who was in the spotlight here?
• Miki: It was Sylvia F. and the Dyslexia.
• Minnie: Why?
• Miki: Can you imagine Sylvia having to struggle with this every day?
• Minnie: OMG. That s*cks.
• Miki: Yes, I think so. Still, Sylvia was able to beat this bastard, and she became a self-taught developer. I can highly relate to her, as despite not having a constant learning diffculty, there were two periods in my life when I was deeply struggling with learning.
• Minnie: Strange. I can't remember that.
• Miki: It is because you did not exist at that time.
• Minnie: Fair enough. Can you tell us about them?
• Miki: Sure. The first one was in grammar school. I was pretty good in Math and Computer Science, but I struggled with Hungarian Grammar, Literature, Geography and History.
• Minnie: That suc*s. Those are the essential subjects to make sure you will be able to deal with life as a grown-up.
• Miki: Sure, Minnie. Sure.
• Minnie: And what was the other period?
• Miki: Well, that was not so long ago. It ended a few months ago.
• Minnie: Really? Tell us about it?
• Miki: The last few years were the worst period of my life, both personally and professionally.
• Minnie: Really? I cannot see that on you.
• Miki: Really. I had depression for several years, and I was the perfect exemplar of the impostor syndrome. My mind was constantly spinning around negative thoughts, and I couldn't think and learn at all. Whatever I read, I forgot immediately. I went so deep I knew I was the worst developer.
• Minnie: I am sorry, Miki. I saw many fellow hloggers who were brave enough to post their stories about these problems. Do not you want to write your own story? It could be helpful for the readers.
• Miki: I already wrote it under the title "Confessions of a Software Developer". But I was not brave enough to post it.
• Minnie: I can understand that Miki, who knows, maybe the time will come.

Today in Spotlight 🔦: Roshaan and her Bad Art

• Minnie: Who is the next one in the spotlight?
• Miki: It is Roshaan and her bad art, but I will be honest I do not remember what was the category.
• Minnie: Never mind. Why did you choose her?
• Miki: As again, I can highly relate to her. She has stopped painting as she felt she is not good at it. I went through the same with my photography.
• Minnie: I wrote a few hundred words, but I won't repeat them. If somebody is interested in it, he/she/it can contact me anytime.
• Miki: Fair enough.

Today in Spotlight 🔦: Amisina Juniors Academy

• Minnie: Let's talk about Data Analysis. Whom did you put into the spotlight this time?
• Miki: Amisina Juniors Academy and the Python Online Training Will Teach You How To Use Python For Data Analysis. Cause I love both data analysis and Python.
• Minnie: I checked the link, but I think there must be something wrong here as it points to Python training for kids.
• Miki: It is possible, but it is also possible that it is intentional. The techniques kids can learn effectively are also working for adults, which is not true vice-versa.
• Minnie: Ok, but there is a catch here. It is not free. You have to pay for it.
• Miki: There is nothing wrong with getting paid for all the time you put into making yourself an expert, mainly if you teach the next generation.

Today in Spotlight 🔦: Lorena Gongang and the DIY Sentiment Analysis

• Minnie: What about SEO, Sentiment analysis and marketing? By the way, what is sentiment analysis?
• Miki: It analyses how people talk about you in the online world. There are many paid tools for that, but Lorena developed her solution and shared it with the world.
• Minnie: That is pure awesomeness.
• Miki: Yes, it is.

Today in The Spotlight 🔦: Atharva Malvade and the Bandwith

• Minnie: Hey, Miki. I saw this time you brought the Bandwidth from Atharva Malvade.
• Miki: Yes. And?
• Minnie: Do you have a separate Networks section?
• Miki: Nope.
• Minnie: Then why did you do that?
• Miki: I want to find out how many of my readers remember this?:
• Minnie: That was horrible. My ears hurt. It is like two robots are talking to each other.
• Miki: You are very close, Minnie. You are very close.

Today in The Spotlight 🔦: Bushra Nazish And The Markdown

• Minnie: Mikie. Do not say to me you also have a section for Markdown.
• Miki: Of course not, Minnie. But I have an idea.
• Minnie: What is it, Miki?
• Miki: My idea is to make the Spotlight category independent.
• Nikolai: You are an idiot Miki; if you put more than one thing in the spotlight, you lose the spotlight's primary goal to draw the focus on exactly one item.
• Miki, Minnie: Hello Nikolai. How is it going?
• Nikolai: Life suc*s as usual. I just applied Hashnode Toolbox, but they turned me down.
• Minnie: Really? Why?
• Nikolai: They said I am a too black-hatted person.
• Minnie: Nevermind, Nikolai. We still highly admire your work. Right, Miki?
• Miki: What? Ah. Yes. Sure. The world without you would be much less fun.
• Nikolai: Thanks, guys. I appreciate your kind words, even if you have no idea what are you talking about. I have to leave. Bye!
• Miki, Minnie: Bye.
• Minnie: Phew. I haven't heard he is here.
• Miki: He is always here. Always.
• Minnie: So what did you bring to us regarding Markdown?
• Miki: - Bushra Nazish's Markdown basics article.
• Minnie: But Miki, you are improved so much in markdown recently, you even became a markdown purist by writing your articles in Notepad++ not using the additional features of the Hashnode markdowns.
• Miki: Yeah, that is true. I almost closed the article at the half, but luckily I didn't.
• Minnie: What has happened?
• Miki: I found something new.
• Minnie: Really?
• Miki: Yeah.
  Click here to learn something new!

  You can easily create collapsible by using the following code: <details> <summary> Click here to learn something new! </summary> You can easily create collapsible by using the following code: </details>

Blockchain, Crypto - In The Spotlight 🔦: ApingNFTs

• Minnie: Hey Miki, I know you are not into blockchain and crypto. Am I right?
• Miki: Lamboooo!
• Minnie: Sorry, what?
• Miki: Lamboooo!
• Minnie: What is wrong with you?
• Miki: Lamboooo! Lamboooo! Lamboooo!
• Minnie: Miki! I am scared as hell.
• Miki: Lamboooo!
• Minnie: Nikolai! Are you here?
• Miki: Lamboooo!
• Nikolai: Sure, I am here.
• Miki: Lamboooo!
• Minnie: What has happened to Miki?
• Miki: Lamboooo!
• Nikolai: I think he became the victim of Aping.
• Miki: Lamboooo!
• Minnie: I have never heard of that. What is it?
• Miki: Lamboooo!
• Nikolai: Just read @xuanling11's Crypto Comics - What is Aping writing report, and you will get it.
• Minnie: Ah. You are right, Nikolai. What should we do?
• Nikolai: Lamboooo!
• Minnie: What?
• Miki, Nikolai: Lamboooo!
• Minnie: Nooooombooo.
• Nikolai: Lamboooo!
• Miki: Lamboooo!
• Minnie: Uncle Nikolaus. Are you still here? I need your help.
• Miki: Lamboo!
• Uncle Nikolaus: Lambooo-ho-ho dear kids.
• Minnie: Luckily. What should we do?
• Nikolai: Lamboo!
• Uncle Nikolas: I have no idea.
• Miki: Lamboooo!
• Minnie: I know what we should do. I saw the word NFT too much recently. Maybe we can turn it to our advantage.
• Miki, Nikolai: Lamboo!
• Uncle Nikolaus: How?
• Minnie: We should promise them that we will make an NFT from some of their photos if 1000 hlogger tells them they are interested in their upcoming writings.
• Miki: Lamboooo!
• Uncle Nikolaus: Great idea, but I doubt Miki will reach 1000 followers.
• Nikolai: Lamboo!
• Minnie: Well, I am a positive person, but ok, then change it to 500.
• Uncle Nikolaus: Miki, Nikolai! Listen to me! If you reach 500 hollowers, we will make an NFT from 8 of your photographs.
• Miki: What has happened? Can you please repeat it?
• Minnie: If you reach 500 hollowers, we will make an NFT from 8 of your photographs.
• Nikolai: I have high doubts it will work.
• Minnie: We cannot lose anything.
• Nikolai: Except for 320 bucks.
• Minnie: I will happily pay $320 to get back my Miki.
• Nikolai: Fair enough.

Games, Game Development, Design, UX - In The Spotlight 🔦: Rohit Jaiswal and The Metaverse

• Minnie: As far as I know, we only have one remaining topic. It is Games, Game Development, Design, UX
• Miki: Yeah, you are right.
• Minnie: Miki, I saw you have sold yourself and picked Metaverse instead of Mr Bud.
• Miki: Yes, that is true. But luckily, Mr Bud is frequently posting, so I am sure he will be in the spotlight soon.
• Minnie: But why did you do that, Miki? Why?
• Miki: For two reasons: First Rohit Jaiswal's The Insider's Guide to Metaverse article is full of colourful images.
• Minnie: Umm. Okay. What is the other?
• Miki: I wanted to share my views about Metaverse, and I also would like to hear the thoughts of the fellow hloggers.
• Minnie: Ok. So what do you think about Metaverse?
• Miki: The coming of Metaverse was inevitable; it is the same as nuclear energy.
• Minnie: But people made nuclear bombs from nuclear energy.
• Miki: Yes, that is true, but they also made nuclear plants much cleaner than the usual energy sources.
• Nikolai: Except for the remaining nuclear waste.
• Miki: That is correct.
• Minnie: So what is your point, Miki?
• Miki: Metaverse is just a tool that can be used for both good and bad.
• Minnie: Makes sense. Do you think FacebookMeta will use it for the good of people?
• Miki: I have high doubts about that.
• Minnie: Why?
• Miki: Meta is a company from the business world, so their most important goal is to earn as much money as possible.
• Minnie: So the idea of the Metaverse is completely flawed then?
• Miki: No. But we should put it in the hands of non-profit organisations. Or they should come up with their Metaverse.
• Minnie: Would that be good?
• Miki: Sure. Just look at Jane McGonigal's SuperBetter(Android, iOS). She used gamification to help millions of people with anxiety and depression to recover from it.
• Minnie: Wow, that is cool, Miki.
• Miki: Yep. I brought Jane McGonigal's TED to talk to our readers, to inspire them and make them think. Here it is:
• Minnie: This is so cool, Miki. By the way, I also heard you would have a TED talk soon.
• Miki: Yep, I was chosen to speak at our company's TED talk HeiTED.
• Minnie: That is cool. Are you excited?
• Miki: Sure, but I am scared as hell.
• Minnie: Why?
• Miki: I found out I will be one of the opening bands before László Mérő's speech.
• Minnie: Who is László Mérő?
• Miki: He is a world-famous scientist. He is a psychologist and also a famous science writer. He wrote many excellent books about topics like Game Theory, and he even has his own game developer company.
• Minnie: That is cool.
• Nikolai: You can be happy you will have the first speech and do not have to talk after him. That would be very embarrassing.
• Miki: I have to admit. You are right, Nikolai.
• Minnie: I thought, Miki, we should create our non-profit organisation to do great things.
• Nikolai: You would fail miserably.
• Miki: You do not have to create a non-profit organisation to make good to people.
• Minnie: Fair enough, Miki. Fair enough. Do you have any advice for the world regarding Metaverse?
• Miki: It should be forbidden for children under 18!
• Minnie: Makes sense, Miki.

Prologue

• Minnie: We have arrived at the end. Do you think we can still keep our readers with this short harticle?
• Miki: I hope so.
• Minnie: I think we can still do something to make this work?
• Miki: I am full of ears.
• Minnie: Well, this harticle is wholly messed up. So in case, we think a little bit positively, we can say this is a unique Hashnode Weekly that we never had before and which we will never have in the future.
• Miki: Yeah. Sort of. So what should we do?
• Minnie: We should put the label Limited Edition on it.
• Miki: OMG. That is a fantastic idea. People are worshipping Limited Editions, which is usually just a way to get more money from them.
• Minnie: Do you think we will be able to get more money from our readers?
• Miki: I have doubts, but give it a try:
• Minnie: Nice try, Miki. Nice try.

Miki, Minnie: Dear readers. Thank you very much for taking your time to read the resurrected Hashnode Weekly 005. We are pretty sure it was quite an unusual experience.

We would like to ask you to share this harticle on hscocial hmedia kindly, so the hwhole hworld hwould hbenefit hfrom the hawesome harticles of hfellow hloggers!

The Miracle

• Miki: Pst, Minnie. Are you still here?
• Minnie: Sure. I am always here till the end since Marvel started to put teaser trailers after the cast list of their moves.
• Miki: I love that.
• Minnie: Do you think there will be something at the end of this article?
• Miki: We will see Minnie. We will see.

• Minnie: Cool.

• Miki: Minnie! You won't believe what has happened.

• Minnie: Give it to me.
• Miki: I was switching through my Notepad++ tabs, and then I suddenly saw something.
• Minnie: What? Your notes from the Data analysis class?
• Miki: Yeah, I saw that too, but there was something else there.
• Minnie: Don't play on my nerves, Miki, just tell it to me.
• Miki: I found the last remainings of Hashnode Weekly 005. I found the previous view markdowns I have generated with Hasnode Newsletter Generator.
• Minnie: That is awesome, so we can still share some of the hawesome harticles?
• Miki: All of them, Minnie. All of them.
• Minnie: Whaaaaat?
• Miki: I had an idea, and I pushed CTRL+Z. At first, some of the lines disappeared.
• Minnie: What happened then, Miki. What has happened?
• Miki: You know Minnie, I love to delete stuff.
• Minnie: Wait. What? I did not know that.
• Miki: Most of the fellow hloggers use Hashnode either in a read-only or a write-only mode. I like to use the full potential of the CRUD operations.
• Minnie: CRUD? What does it stand for?
• Miki: It is a term used when we are talking about database and service interactions and also when we are talking about Hashnode bloggers. It means Create-Read-Update-Delete.
• Minnie: I understand creating and reading, but what about updating?
• Miki: As you know, I often update my articles after I publish them. For example, to fine-tune my call to action section.
• Minnie: Yeah, I know that. But what about deleting? Are you destroying the work you put into writing articles?
• Miki: I have learnt during my photography career that your pictures are only as good as the weakest ones.
• Minnie: Can you please explain this to me?
• Miki: People usually only remember the best things and the worst things. They reflect the worst things, more to be exact.
• Minnie: Ok, I understand it. That's it?
• Miki: People are looking for similarities. As soon as they find something similar, they start to compare it. This is why I never post two photos about the same thing, no matter how good are they. I cannot tell which will be the most liked one, but I don't want to give a chance for comparison.
• Minnie: Fair enough. Is it also true for writing?
• Miki: Sure. There are millions of excellent articles on the internet. In case you cannot be unique, then you are lost.
• Minnie: So, how do you try to be unique?
• Miki: Well, I am always coming up with a catchy title, and I am compositing my unique cover images.
• Nikolai: I have to admit that is a good start, but that is not enough to grab and keep people's attention.
• Miki: You are right, Nikolai. That is why I am doing one more thing.
• Nikolai: What is it?
• Miki: Instead of talking from the podium, I invite my readers to a conversation.
• Nikolai. Damn. That is clever, Miki.
• Minnie: Thanks Mikiiii, for letting us also join the discussion. It is so kind of you.
• Miki: You were always here, Minnie and Nikolai, but I was so rude, I never introduced you to our readers.
• Nikolai: You bastard. You wanted all the fame for yourself.
• Miki: Yeah, fame. Sure, Nikolai. Sure.

• Minnie: We lost our focus again, Miki. So why do you delete your work?
• Miki: To make it better by excluding the boring parts. Fun story, once I got so addicted to deleting, I have deleted all single lines of text from my article.
• Minnie: No way. So nothing remained?
• Miki: Only the title.
• Minnie: Really?
• Miki: No, I was just joking around. But I will do that shortly.
• Minnie: So I understand you are always handpicking the parts you are deleting.
• Miki: Yeah. Except once. This time.
• Minnie: What do you mean?
• Miki: This time, the Creator/God/Grammarly Premium/The communist/Aliens/NSA/Universe has deleted my story.
• Minnie: Yeah, that is true. What a pity.
• Miki: I have to admit, I almost cried when it happened, but I am happy about it now.
• Minnie: Cause it deleted the bad parts of my story.
• Minnie: But it also deleted the excellent parts.
• Miki: Yeah, but I have 70% of my writing in my head so that I could resurrect the deceased Hashnode Weekly 005 from its ashes.
• Minnie: That is true.
• Miki: And not just resurrected, but I also had a second chance to make it even better.
• Minnie: Do you think you were able to do that?
• Miki: We will never find out. Except the Hashnode Team can recover my article. In that case, I will post that too.
• Minnie: Miki, you are so good at catchy namings, don't you think we should give a name to this tragedy?
• Miki: I already have it on my mind.
• Minnie: Give it to me!
• Miki: Hashnode Weekly 005 Limited Edition by Miki Szeles AKA The Big Delete.
• Nikolai: That title su*ks, Miki.

• Miki: We will see Nikolai, we will see.

• Minnie: Miki, you did not finish the CTRL+Z story.

• Miki: Sorry. So as I pushed one CTRL+Z after the other, the lines started to disappear, but then, when no other lines remained, the miracle happened.
• Minnie: Oh. I love miracles. What has happened?
• Miki: I hit CTRL+Z one more time. And it was there.
• Minnie: What was there?
• Miki: All the markdowns for the deleted articles.
• Minnie: No way! So we can share the whole list with our readers?
• Miki: Sure. Here it is:
• Nikush Dalia You can't do everything*
• Saroj Behera How does the Blockchain work?
• Ashutosh Jha Some websites to get free illustrations and Front End Resources...
• Gyanesh Samanta Getting the most out of Search Engines
• Timothy Tomas My Introduction 👋
• Shreya Tabjul What's your career agenda? A startup or an enterprise?
• Atharva Malvade Bandwidth
• typogram team Debugging Is a Lonely Business
• Madza 12 Creative Animations to Make Your Projects Stand Out ✨💯
• Bhagya Indimagedara Introduction to NoSQL
• Alex Ciotirla Finally, I pulled the trigger and...
• T.I.M.I.B.O.I Journey Of A Thousand Backend Developers.
• Davide Bellone Clean Code Tip: AAA pattern for tests: why is it important?
• Caroline Web3 and Women: How Can Women Embrace The Future?
• diconium How to Improve Your Coding Efficiency Immediately
• Bhagya Indimagedara Getting Started with Angular
• Jorge Romero Categorially-represented non-monotonic logics. Or how I think I broke an AI
• Precious Abubakar Getting Started in Tech: A Concise Guide for Newbies
• Maxi Contieri Code Smell 122 - Primitive Obsession
• Saroj Behera What are Decentralized applications?
• Rin I wasted a month.
• Eamonn Cottrell Sacred Geometry with Adobe Illustrator
• Manav Gupta Get started with the Hashnode API
• abdellah hariti Promises: async/await vs .then(), how we got here and why I use both
• Robert Ejiogu How To Think Like A Programmer
• Sasi Datta Devops - First post
• Chineta Adinnu The Journey continues...
• Seven Mentor Top programming languages: Java takes an unexpected leap forward
• Johnny Evans I'll change the world
• Hamody Hackthebox Traverxec Walkthrough
• Lorena Gongang Sentiment analysis on streaming Twitter data using Kafka, Spark Structured Streaming & Python (Part 2)
• Radosław Lewandowski Cukedoctor - when test automation meets living documentation
• Sparkful Studios Stop Adding Limits To Your Game!
• Cynthia Mwihaki Kamau What Is Cloud? An Introduction.
• German Cocca Debugging: History, tools and thoughts
• Bence Hornyák Commonly used http methods
• Sylvia F. The Code to being Dyslexic in Tech.
• Amisina Juniors Academy Python Online Training Will Teach You How To Use Python For Data Analysis
• Ethan MediaRecorder API Tutorial
• Tobias Finnson A quick story about flash player and browser games golden age
• Dipankar Medhi Self Driving Car using Tensorflow
• Phillip Johnson Is it time to redefine TDD?
• Devhouse Why HR in tech is a really big deal. Interview with Angelina Golovchenko.
• Dorcas Bitrus Tips For Technical Writing Newbies
• Anushka Gupta 9 Pro Tips for Developer Productivity
• Omar Ben. Why 2022 will be Exciting for Developers
• Andrei Tiburca Top 10 Free Blogging Platforms for Developers In-depth Review
• Arya Bharti Building A Clean And Readable Codebase - Key Takeaways
• Shreya Sahani Application of Sentiment Analysis in Different Industries.
• nishit chittora What are digital tokens and how its different from cryptocurrency?
• Maddy What Is The Software Engineering Career Path?
• Economize How to get free Google Cloud Platform (GCP) Credits
• Swati Sarangi Introducing one of the Investors of Hashnode
• Jorge Romero Quick! I need a cheap trick! I'm running out of writing ideas!
• Parvin Eyvazov FREE! Translate your language JSON file to any languages.
• Opemipo Disu Aurora: An application that helps fight cyberbullying.
• xuanling11 Crypto Comics - What is Aping
• Harsh Agrawal Lessons I learned from my failed side project
• Priyanshu Mourya Day 1(0% idea of how to proceed!)
• howbeginners Professional Blogging How To Create A Blog And Make It Thrive
• Matthew Sechrist How I created NextRead, an author recommendation web app that finds authors who wrote/are mentioned in book endorsements
• Yingyi Mo console.log(’Hello, world!’, ‘-introduction’);
• Victoria Quattrociocchi Datasets públicos!
• Richard Gichuki Civil Engineer to Software Developer
• Taimoor Sattar How Do I Build A Platform To Sell My Course?
• Deepak Kumar The Notion of a Good Algorithm
• Srishti Trivedi Curiosity plants the seed of Innovation
• Roshaan I have decided to create bad art [Again]
• BUSHRA NAZISH Markdown basics
• Andrés B. Aldaz Elements of Leadership
• Heloisa Moraes How to determine your goals and metrics to adopt a data-informed culture
• Fortune Adekogbe Getting Started with Machine Learning: The Quantum Edition
• Sergey Laptick Make Sure Your Business App Won’t Turn to Dust. Major Testing Methodologies Overview
• Rohit Jaiswal The Insider's Guide to Metaverse
• Damilola Oyetade It's World Sleep Day, 2022! Are You In The Same Shoe As Me?
• Elijah Okello Supervised Learning. Introduction to Neural Networks !
• Md Abu Taher Scraping data from bot-protected websites using proxy api

Thanks for reading my article. 😊

In case you enjoyed it, then please share this harticle on hscocial hmedia, so the hwhole hworld hwould hbenefit hfrom the hawesome harticles of hfellow hloggers! 😇

In case you were suffering during reading, then please share this harticle on hscocial hmedia, so the hwhole hworld hwould hsuffer htoo! 😈

Don't forget to read the previous Hashnode Weely Newsletters:

1. Hashnode Weekly 001 by Miki Szeles
2. Hashnode Weekly 002 by Miki Szeles
3. Hashnode Weekly 003 by Miki Szeles
4. Hashnode Weekly 004 by Miki Szeles

My credo: The Mystery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humour, and I am also happy to tell you that, this is my article about which I am the proudest of now.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to, on Hackernoon and even on Instagram. 😊

Contribute to the open-source Selenideium Element Inspector Chrome Extension, with which test automation teams can save hours daily by automatically generating all the relevant selectors for Selenide, Selenium, Cypress, Playwright, Squish and TestCafe.

Follow the Selenideium Element Inspector Twitter channel to get updated on the latest happenings regarding Selenideium, to get help, to share your experience and also to talk about any (test automation) related topic! 😊

Join the Selenide User Group on LinkedIn to connect with more than a hundred test automation engineers and learn and get help regarding the most astounding e2e test automation framework: Selenide.

Join the Selenideium Element Inspector Bounty Hunting Reward Program and earn ☕s by contributing to this open-source project. 🚀 This is the perfect opportunity to make the first step into open-source contributing, and also in case you would like to learn about JavaScript and Chrome extension development. 😊

You can expect a friendly, helpful community, and you can even earn ☕s.

I will even give a shoutout to you both on Selenideium and my personal Twitter accounts in case you contribute.

• Minnie: I like Marvel movies, not just because I love superheroes, but also because they always hide a short trailer after the cast list. Let us do the same too from now on.
• Miki: Ok.
• Minnie: So Miki, what will you write about next?
• Miki: I will write about (IT) recruiters.
• Minnie: Wow. Do you already have the title?
• Miki: Sure:

My All-Time Top 3 Favourite (IT) Recruiters

QA Session

Holi

Holi is a popular ancient Hindu festival. It has many different names:

• Festival of Spring
• Festival of Colours
• Festival of Love

I would like to take the opportunity to wish a happy Holi to the people of India:

Happy Holi Dear Indian Friends!

Apologize

As you might already notice, I am always one day off, so that is why I am only writing today.

I was very busy writing my article Why You Always Have To Close Your Article With A Call To Action AKA A Brief Introduction To Hashnode Widgets By Miki Szeles.

It took some time as I spent 12 hours to write this article, but I do not regret it, as this is my best writing up till now.

It has a 42 min reading time according to Hashnode, but I still highly recommend reading it, in case you would like to raise your writing to the next level and also in case you would like a little bit about how to activate your readers and also in case you want to learn a little bit about marketing.

As you might already know, most of my readers are from India, so I thought today is the perfect opportunity to learn and share a little bit about the Indian culture by doing some research on Holi.

What is Holi?

The Holi festival celebrates the eternal and divine love of Radha Krishna.

It also expresses the triumph of good over evil, by celebrating the victory of Lord Vishnu as Narasimha Narayana over Hiranyakashipu.

As I am an outsider basically I know nothing about Holi. I saw photos of people pouring colourful powders on each other. However as a photographer, I am obsessed with colours (and with monochrome photos too), I did not really understand why this is happening.

Why do people pour colourful powder on each other?

As I did not know why do people pour colourful powder on each other, I did some research and I found the info here.

The ritual of throwing colourful powders draws on the story of Krishna and Radha.

As a child, Krisha was jealous of his beloved Radha’s fair complexion, which was much lighter than his own blue face.

He complained to his mother Yashoda, who playfully told him to colour Radha’s face in whatever colour he liked – which he did.

During Holi Hindus throw colourful powder, known as gulal, to celebrate Krishna, Radha and their love for each other.

Who is Krishna and Radha?

I do not like to rephrase good writings, so I will just quote what I found about Krisha on britannica.com.

Krishna

Krishna, Sanskrit Kṛṣṇa, one of the most widely revered and most popular of all Indian divinities, worshipped as the eighth incarnation (avatar, or avatara) of the Hindu god Vishnu and also as a supreme god in his own right. Krishna became the focus of numerous bhakti (devotional) cults, which have over the centuries produced a wealth of religious poetry, music, and painting. The basic sources of Krishna’s mythology are the epic Mahabharata and its 5th-century-CE appendix, the Harivamsha, and the Puranas, particularly Books X and XI of the Bhagavata-purana. They relate how Krishna (literally “black,” or “dark as a cloud”) was born into the Yadava clan, the son of Vasudeva and Devaki, who was the sister of Kamsa, the wicked king of Mathura (in modern Uttar Pradesh). Kamsa, hearing a prophecy that he would be destroyed by Devaki’s child, tried to slay her children, but Krishna was smuggled across the Yamuna River to Gokula (or Vraja, modern Gokul), where he was raised by the leader of the cowherds, Nanda, and his wife Yashoda.

Radha

Radha, in Hinduism, the gopi (milkmaid) who became the beloved of the god Krishna during that period of his life when he lived among the gopas (cowherds) of Vrindavan. Radha was the wife of another gopa but was the dearest of Krishna’s consorts and his constant companion. In the bhakti (devotional) movement of Vaishnavism, the female, Radha, is sometimes interpreted as symbolizing the human soul and the male, Krishna, as symbolizing God.

Well, this was a brief and dry introduction to The Festival of Holi, but I am pretty sure there are much more in it than I just briefly described here.

Dear people of India!

What does Holi mean to you?

Share your thoughts and photos in the comment section.

I wish you a Happy Holi again. 🌏🌼🌈❤

To let the world know about Holi, please share this article on social media!😊🧡

My credo: The Mystery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humour, and I am also happy to tell you that, this is my article about which I am the proudest of now.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to, on Hackernoon and even on Instagram. 😊

Contribute to the open-source Selenideium Element Inspector Chrome Extension, with which test automation teams can save hours daily by automatically generating all the relevant selectors for Selenide, Selenium, Cypress, Playwright, Squish and TestCafe.

Follow the Selenideium Element Inspector Twitter channel to get updated on the latest happenings regarding Selenideium, to get help, to share your experience and also to talk about any (test automation) related topic! 😊

Join the Selenide User Group on LinkedIn to connect with more than a hundred test automation engineers and learn and get help regarding the coolest e2e test automation framework: Selenide.

Join the Selenideium Element Inspector Bounty Hunting Reward Program and earn ☕s by contributing to this open-source project. 🚀 This is the perfect opportunity to make the first step into open-source contributing, and also in case you would like to learn about JavaScript and Chrome extension development. 😊

You can expect a friendly, helpful community, and you can even earn ☕s.

I will even give a shoutout to you both on Selenideium and my personal Twitter accounts in case you contribute.

What are you waiting for?

Check out Breaking News! Selenideium Element Inspector Bounty Hunting Reward Program Is Here ☕ for more details! 😊

Let me outline a short story for you.

Mumbling on the street with a bucket on your head

You get up, early in the morning. To boot your day, you drink a coffeeand maybe also smoke a cigarette (at least I do that).

A quick shower, dress up, and 10 minutes later, you are down on the street.

It is still quite early, but many people are walking to work, not looking up from their phones at all.

You stop at the side of the street.

You clear your throat, take a deep breath, put a bucket on your head and then.

You start mumbling.

One word leaves your mouth after the other.

Sometimes you pause for a second, but then you continue in a hurry.

After a few minutes, you stop.

You take off the bucket from your head and go home.

A few hours later, you are at home wondering.

Wondering because:

You have no idea whether somebody was on the street around you.

You have no idea whether somebody has heard your words.

You have no idea how long were they listening.

You have no idea whether they were women or men.

You have no idea where the listeners are from.

You have no idea how old are they.

You have no idea whether somebody has understood what you were trying to say.

You have no idea how many of them liked what you were saying.

You have no idea what do they think about your message.

You have no idea whether your message changed their thought process.

You have no idea whether your message affected their actions or not.

You have no idea whether they are spreading your words or not.

And finally,

You have no idea whether you had a message at all.

Is this story sounds familiar?

No?

Well, this is the story of my first few weeks of blogging on Hashnode.

Luckily I am continuously improving myself, not just in development, testing and personality-wise, but also in writing.

The RWRR(Read-Write-Reflect-Repeat) method to raise your writing to the next level

There are 4 steps that you have to do to radically improve your writing:

1. Read
2. Write
3. Reflect
4. Repeat

Let's examine them one by one.

Read - The 1st pillar of quality writing

Reading!

To learn writing, you have to read—a lot. And even more than that.

By reading a lot, you will quickly realise how easy to skim through an article if it is well-structured, but you also learn that it is hell to read an article that consists of one paragraph.

No matter what, I almost always immediately close such articles. It is just not efficient to waste my time on it.

You also quickly get a good grasp of what a good title looks like.

You can get a hell of a lot of ideas for your upcoming articles, too.

And you can even create your Newsletter from the articles you read.

Do not you believe me?

Just check the latest Hashnode Weekly 004 by Miki Szeles. 😊

There is much more thing you can learn from reading, but I am already writing a separate article on this topic so that I won't list more here.**

But to raise your curiosity I leave the title here for you:

How to write an article just about almost anything?

Stay tuned. It will come in the next few weeks. 😊

I am personally reading 80+ Hashnode articles weekly. That is 80+ opportunities to learn something new or have new ideas. Weekly.

Write - The 2nd pillar of quality writing

Learning the theory is good, but it does not worth anything in case you do not put it into practice. That is why the 2nd pillar of excellent writing is:

Writing itself!

By now, you already read a lot, especially about the subject you would like to write about.

Stop for a second and slap yourself on the back; you are already better than 90% of the bloggers in the world (No, of course, I am not talking about Hashnode bloggers (Hloggers™️). Hloggers are cool. Hloggers are very cool. 😊).

So by doing it, you can put everything you learned by reading into practice.

You can find a catchy title and an even catchier cover image.

You can structure your writing so your users can easily navigate it.

And much more. Just read my upcoming article to learn more. 😊

Experiment with different writing lengths to find the size which best suits you.

Of course, you can write articles of any length, but it is good to be aware of which is the perfect length for you.

At the moment for me, this is around 13 minutes of reading time, but it tends to get longer.

Last but not least:

Read your article multiple times. Don't ask why; just do it! It is enough to say thank you to me later, whenever you realise the value of self-reading. 😊

Reflect - The 3rd pilar of quality writing

Here we are at the 3rd pilar of excellent writing:

Reflection!

You have already read and written so it is time to think about what you can learn from it.

This is the point where you realise you have nothing based on which you can reflect on your previous writing.

If you are lucky, you might have got around a dozen reactions and 1-2 thanks comments on your article, but that's all you know.

So the question which is emerging from this situation, which I will answer in this article, is:

How to collect the feedback for your writing and how to reflect based on that?

But before answering the question, let's talk about the 4th pilar of excellent quality.

Repeat - The 4th pilar of excellent quality

Doing the Read-Write-Reflect once is great, but you won't improve too much in case you do not do it regularly.

I count as a Hashnode newbie, as I am only blogging here for 1,5 months, but I already had 38 iterations during this short period.

I am not telling you to do the same, as not everybody is as crazy as I am, but I do recommend doing it just a little bit more often than you are comfortable with.

In order to progress, it is crucial to step out of your comfort zone every time. Just a little bit, but still every time.

I cannot tell you exactly how much I improved during this time, but here is a list that I count as advancement:

• I went from 0 to 200+ daily views which I was able to achieve during the last weeks consistently. On my best day, I had 4479 page views, and I was able to attract more than 1000 readers for four consecutive days
• My follower count went from 0 to 143
• The average reading lengths of my posts went from ~2 to 10+.
• With Hashnode Weekly, I can consistently reach 200+ views
• I have developed a Call To Action consisting of 6 elements. More about this later.
• From starting blogging on LinkedIn and Hashnode, I have greatly extended my audience by blogging also on Medium.com, dev.to and hackernoon.
• I became much better at coming up with catchy titles
• From the point of primarily using a stock image, I arrived at the point where I usually composite my cover photos from multiple images.
• I got contacted by a company, to write articles for them, of course. This is still a secret, but I will let you know when I will start posting also on their platform.
• I use way fewer expletive words
• My English grammar and vocabulary improved so much I very often think in English instead of Hungarian. I also started to take notes in English at the university on the Data Analysis class (which is educated in Hungarian), as I can easily reuse my notes for my blog posts this way.
• However finding your unique voice is a never-ending process, but I still think I was able to form a style, from which even people who do not know I am the writer of the article could recognise I wrote it. Of course, I might be wrong, so please share your thoughts in the comment section. 😊

I am sure I could continue the listing, but let's focus on keeping focus.

That was the Read-Write-Reflect-Repeat (RWRR) method.

Haha. If you googled for the abbreviation RWRR, you must know by now that there is no such thing as the Read Write Reflect Refactor Method.

At least there was no such method up till now.

Happy 0th birthday, dear Read Write Reflect Repeat(RWRR) method. ❤🎂😊

Let's back to the main questions:

How to collect the feedback for your article and how to reflect based on that?

Please let me bring back my story from the beginning of this article.

I have updated it.

Can you spot the difference?

Mumbling on the street with a bucket on your head revisited

You get up early in the morning. To boot your day, you drink a coffee and maybe also smoke a cigarette (at least I do that).

A quick shower, dress up, and 10 minutes later, you are down on the street.

It is still relatively early, but many people walk to work, not looking up from their phones.

You stop at the side of the street.

You slip out a small camera from your pocket, put it beside you and hit the recording button.

You clear your throat, take a deep breath, put a bucket on your head.

You start mumbling.

One word leaves your mouth after the other.

Sometimes you pause for a second, but then you continue in a hurry.

After a few minutes, you stop.

You took off the bucket from your head, slip you're camera into your pocket and went home.

A few hours later, you are at home wondering.

Again.

But this time, it is different.

You have a video recording.

Analyzing the recorded video

You cannot record your reader with a video camera, can you?

However some companies still think the best way to motivate people is to record their screen and web camera while they are working, you should not do that.

But I have great news.

You do not need to do that, as there is a better solution for that:

Analytics!

Whether it is Hashnode's built-in analytics, Google Analytics or something else.

So let's revisit our questions to see which of them can be answered by analytics.

You have no idea whether somebody was on the street around you

It is straightforward. Just check the visit count of your article, which will tell you how many people passed the road.

You have no idea whether somebody has heard your words

This one is called bounce-rate.

Bounce rate is the percentage of users who immediately left after opening the page without spending a second.

Fun fact #1: This was the first time I used an equation in an article. I have used a free online formula editor mathcha.io. It is straightforward to use. 😊

So let's calculate how many people heard my mumbling for some of my articles:

• Save dozens of minutes daily during writing Selenide and Selenium E2E automated tests using the Selenideium Element Inspector Chrome Extension!:
• How Google Tests Software - What we can learn from Google? - A book extract By Miki Szeles :
• How to Create a Legendary GitHub Profile?:

So we already know how many people heard us mumbling.

This will be useful, as all other measurements are relative to this value.

You have no idea how long were they listening.

This one is also simple as you can get it from the analytics directly:

• Save dozens of minutes daily during writing Selenide and Selenium E2E automated tests using the Selenideium Element Inspector Chrome Extension!: 4:31.
• **How Google Tests Software - What we can learn from Google? - A book extract By Miki Szeles: 5:14.
• **How to Create a Legendary GitHub Profile?: 4:33.

Quite impressive numbers, especially the last one, as it is an article with 2 minutes read time.

I have no idea what the hell my readers were doing on that page. 😊

We know how long the people were listening to our mumbling. The logic is very simple here:

The more, the better. 😊

You have no idea whether they were women or men

I support gender equality from all my heart and mind.

I even dedicated two articles to the Women in Tech:

• Happy International Women's Day - Miki Szeles's words about Women in Tech 💝
• Hashnode Weekly 004 by Miki Szeles

My articles are gender independent. I won't use a different tone, and I won't have another message because I have more women or men readers.

But depending on the topic you are writing about, it can count for you.

If you are writing a blog about parenting or you give tips on makeup, you should know how many women and men are reading your articles, as you can tailor your articles to them.

You have no idea where the listeners are from

Here are my statistics:

At the moment, I am using this information for two purposes:

• Finding the right time for posting. I am in GMT+1, but as most of my readers are from India, posting my articles when they are awake might make sense.

The daily distribution of your readers can also be determined by Google Analytics so that it might make more sense to time your posts based on that.

• To guess the name of my readers. True story. Read my article "QA Vs Dev AKA Bug Vs Feature AKA A Never Ending Debate AKA The 7 Testing Principles Explained By Miki Szeles" which will come in a few days. Don't forget to follow me so you won't miss it. 😊

You have no idea how old are they

Well, this information is not relevant to me. I am targeting the whole (tech) community.

Just look around here on Hashnode.

There are 12 years old bloggers and also 50+ bloggers here on Hashnode.

Blogging is ageless.

But again, this might be relevant for you.

You might write cause you would like to help teenagers get into the tech world or give career advice to people who would like to become software developers.

In these cases, it is important to know their age, as you can better tailor your articles towards them.

It does matter whether the teenagers or their parents are reading your articles.

You have no idea how many of them liked what you were saying or not.

• Hi Miki! Thanks for joining us for an interview. I am thrilled you are here. I just heard your mumbling on the street the other day, and you raised my curiosity.
• Hi Miki! Nice to meet you. Yeah, I was mumbling. I am happy to get to know that I was able to grab your attention. It is very hard these days.
• Yeah. I know. Can we start?
• Sure!
• As you said, you have no idea how many of your readers liked what you were saying.

You can count on me. So you have one listener indeed.

• Thanks, that is very kind of you.
• So, how can you tell whether your readers liked your story or not?
• It is easy, Miki, we have ten different emojis with which you can react to a post:

👍🦄👏❤🍺🏆💰😍🎉🚀

And there are even crazy bloggers like you who push all the 10 in case they like an article.

• Yes, that's valid, but I am sorry to say this, bloggers are lazy as hell get tired by the time they read your article.
• So what is the solution then?
• You have to ask them nicely to react to your article, and of course, you have to lead by example. 😊

Fun fact #2: This was the first time I used strike-through in an article. Unfortunately, I have not found a way to do it with Hashnode markdown, but as Hashnode also supports embedded HTML, you can easily do it by:

<s>bloggers are lazy as hell</s> get tired when they read your article.

Fun fact #3: As I did not want to look like a loser, I checked the Hashnode markdown guide, and I found out Hashnode supports Latex equations. Let's try it out quickly: $$ \lim\limits_{visitors \to \infty} \exp(visitors) = to the Moon $$

In case you open your article, and you see all the ten emojis are there, you can be almost sure that:

1. Miki Szeles read your article.
2. Miki Szeles found your writing valuable.
3. Your article will be featured in the upcoming Hashnode Weekly.

You have no idea whether somebody has understood what you were trying to say.

• To find this out, you have to talk to your listeners/readers.
• Ok, but how do I talk with my listeners? Should I call them on the phone one-by-one? I do not even have their phone number.
• In the comment section, of course. That is the only reason for its existence.
• Ok, but how do I convince my readers to comment on my article?
• As usual, lead by example, but I will tell more about this topic later.

You have no idea what do they think about your message.

• How can you figure out what are they thinking about your mumbling?
• This can be learned with the procedure mentioned above:

You have to ask them.

You have no idea whether your message changed their thought process.

• What about changing their thinking? Same as above.

You have no idea whether your message affected their actions or not.

• From what can you tell how your mumbling inspired for taking action?
• Just follow your readersso you can easily find out, and of course, ask them in the comment section.

You have no idea whether they are spreading your words or not.

If you want to change the world, it is not enough to be an alone prophet, you need missionaries, who spread your words in the world.

• Yeah, that is true, for sure. My advice is to follow your readers on social media platforms like LinkedIn, Twitter and Facebook, especially on Twitter as that is where real things happen.

You have no idea whether you had a message at all

• What is the final question which is more crucial than all the others Miki?
• The most crucial question is: What is your message?
• Miki, I don't have a message. Is that a problem?
• I wouldn't call it a problem; it is much more a waste of opportunity.
• Ok, but why?
• Because your readers have read your article, and now they are listening to you, eagerly waiting for what else will you tell.

You should not articulate your message to your readers. Instead of that you should tailor your article to radiate your message.

It works much better if you let the readers figure it out for themselves.

And that was it. We were able to answer almost all of our questions.

• Thanks Miki for the explanation. By now I know much more about my readers/listeners. But how can I active my readers?
• By asking them nicely, to do something. There is a term for this in marketing. It is called:

Call To Action - AKA Miki Szeles's 6 commandments asks for favor

No matter whether you are marketing your product, yourself, or you just shared your knowledge with the community,

You (should) have a message for your readers.

• Ok, but why?

You wrote a high-quality article, put in several hours to research and to register your essay, you post it, but still:

You have no idea whether somebody was on the street around you.
You have no idea whether somebody has heard your words.
You have no idea how long were they listening.
You have no idea whether they were women or men.
You have no idea where the listeners are from.
You have no idea how old are they.

You have no idea whether somebody has understood what you were trying to say.
You have no idea how many readers liked what you were saying or not.
You have no idea what do they think about your message.
You have no idea whether your message changed their thought process.
You have no idea whether your message affected their actions or not.
You have no idea whether they are spreading your words or not.

In order to find this out, you need the Call To Action.

Miki Szeles's 6 commandments asks for favor

Many marketing experts would tell that you should only have one call to action, but I see it differently, but of course, I do not trust in gut feelings, I test everything, as you might already know, my motto is: Testing is the soul of everything

My first article had 0 calls to action. I am not 100% sure, as I already updated it multiple times.

But during the 1,5 months I have collected six different calls to action, so please let me share them with you to help you find your ones.

Commandment #1 - Share this article

• Hey Miki, I put a lot of effort into my article, I posted it on Hashnode, Dev.to, Medium and Hackernoon, so my followers will see it. And I also shared it on Twitter, LinkedIn and even on Facebook, so all my followers will see it.
• You are wrong.
• Why?
• Social media platforms are living from advertisement.
• And?
• Why would you pay for marketing if all your followers could see all of your messages?
• Umm, to reach also my non-followers?
• Right, but social media platforms like LinkedIn and Facebook are so poor they have to find and exploit all potential monetisation options.
• Ok, I can understand that. Poor social media platforms. I hope they get enough money to feed their children. Maybe I should start an ad campaign, to make sure that.
• Sad fact: Only 6% of your followers see the content you posted on Facebook.
• Sorry, what?
• Let me repeat this: Only 6% of your followers see the content you posted on Facebook.
• What the heck?
• Yes, I can understand your feelings. Do you see why it is crucial to have real followers and not artificially grow them by paying a few bucks to get a few thousand random followers?
• Umm, not really.
• Let's suppose you have 100 real followers and 900 followers you got by paying for them. By the way, I am pretty sure that 1/3 of those 900 are robots.

6 per cent of 1000 is 60. That is quite a bad result, but six is even worse.

Only 6 of your real followers will see your article!!!

• Ok, but I do not have money to advertise my article, so what can I do?
• You can hack the system.
• Hacking? How?
• 6% is only an average.

The more reactions and comments are on your article, the more people you will reach.

• Ah, cool, thanks for the in-depth explanation, Miki.
• It was my pleasure, Miki

So, by now, you already know how crucial it is to share the articles of your fellow bloggers even without asking. But to be on the safe side, I kindly ask you to share this article if you find it helpful. 😊

How to measure the performance of your article?

• Managers love KPIs.
• Umm. I don't want to sound stupid, and I know I could Google it, but as I think we are friends, Miki, I ask you: What are KPIs?
• KPI means Key Performance Indicator. KPI is a measurable value that demonstrates how effectively you are achieving your key business objectives.
• Ok, so what is the big deal with these KPIs?
• Managers do not just like it, they fetishise them so much they are putting them on a board called a dashboard, so they can sink on their knees and worship these excellent looking KPIs. Look:
• Wow. It looks gorgeous.
• Yeah, I think so. I like the shades of orange and yellow. I have to admit, I can understand why managers are looking at these beautiful masterpieces all day long.
• Mikiii. Do these managers also make KPIs to their employees' happiness?
• I don't think so, but maybe they will at least start to think about it after they read this article.

Joking aside, KPIs are very valuable even for us bloggers. It is so helpful I even come up with my own KPI. Who knows maybe at some point this number will be included in the Hashnode Analytics. However I know some of the Hashnode team members are usually reading my articles (thanks, Eleftheria Batsou 😊), but to make sure they won't miss it, I have created a feature request. Please upvote it if you find this idea valuable. 👍

So, let's calculate this value for some of my articles:

• Selecting an End to End Testing Framework - Selenium or Selenide?: I just realised my first article reached 372 readers.

It had three comments and four reactions.

Here is the calculation:

• Miki! That number is as small I cannot even see without my glasses. We should not show that to the CEO as the whole team will be fired immediately. 😱
• You do not have glasses, Miki, but you are right about the numbers, let's tweak it a little bit so that the upper management will be happy.

In order to make sure you won't get fired</>reach the full potential of KPIs, you have to compare them to samples taken in the past.

I have decided to use my first article with 200+ views as the baseline.

I will compare the performance of my articles to that. Of course later, whenever I will constantly have 1000 reads per article, I will use a different baseline. 😊

So we have to adapt our calculation by dividing it by 0.0188.

Sht, I *forgot to use the Hashnode Markdown for equations. Let me make it good.

$$ \frac{\frac{numberofreactions}{visitorcount} +3 * \frac{numberofcomments}{visitorcount}}{0.0188} $$

I needed many iterations to learn the correct syntax and during this, I experienced a bug, which I also saw earlier, but this time it was annoying.

Whenever I switch between the write and preview mode, the view scrolls to a completely different position. Usually, it missis the position by several pages.

Here is the bug report, please upvote it if it also annoys you. 👍

Let's get back to our calculation.

For the first article, it will result in 1 of course, as we are dividing with itself.

That's boring, so let's check 2 of my other articles:

• My First Month on Hashnode - A Retrospection About Blogging on Hashnode Developer Journaling Platform by Miki Szeles: $$ \frac{\frac{132}{457} +3 * \frac{17}{457}}{0.0188} = 21.3 $$
• Wow, Miki. That is awesome. That is what management would like to see. We might keep our jobs. I am so happy.
• Hold on. Managers are sotille. From now on, they will measure our results using this as a baseline.
• Ahh, you are right. What should we do?
• Obvious, we should never show this article to them.
• Ok, Miki, but we have to come up with something.
• I know exactly what should we do. There was an article that got more than 12k views, but I was so dumb that I did not add any call to action.

• Wow. More than 12k readers. That is pretty awesome. Show me the results!

• How to Create a Legendary GitHub Profile?: 0.44

• Hah. We got it. That looks much better. I hope management will use that as the baseline.

• Yeah, we will show this one to the management, but let's be honest, this result is delusory. You are right, but it is too late to do something, Miki.
• I still have an idea with which we can improve the situation.
• Really? That would be awesome. What should we do?
• We go back in time and add our six commandments to it.
• That is an exciting idea, but we cannot go back in time, Miki.
• You are right again, Miki. As always, you are more clever than me. So what is what we can still do?
• As this article still has some momentum, we update the article and add the call to action to it.
• Wow. What a fantastic idea.

Dear reader! I will be right back. Just give me some ⏰ to update my article.

Up till then, I suggest the same to you. 😊

• Are you back, Miki?
• Yeah, sure.
• Why did it take so long?
• Well, I tried to use Hashnode Widgets to save time.
• Wow. Hashnode Widgets. Can you tell me a few words about it?
• First things first, Miki. I will get back to it.
• Ok, so what was the problem?
• Well the result was utterly messed up. Look:
• Ouch. Have you created a ticket about it?
• Sure. If there is no ticket about something, that thing does not exist. You can find it here. Please upvote it in case you would also like to use Hashnode Widgets.👍
• In the end, I made six commandments.
• Wow, that is awesome. Just five more to go, and we will beat Moses.
• Hey, Miki. Did you know it is not okay to joke about religion in our PC world? I know, but I do believe religious people also have humour, and I hope they won't get it offensive. But I kindly ask you to let me know, and I will immediately remove this section. 😊
• Ok, so what is commandment #2?
• Before I answer it, let me show you the result: How to Create a Legendary GitHub Profile?

Commandment #2 - Read my best article!

• What do you mean by this, Miki?
• Your readers have read your article, most probably they enjoyed it as they have read it till the end.
• So what?
• It would be a waste not to grab this opportunity.
• Arrrr. What do you mean? I cannot follow you, Miki. You are mysterious as usual. Your kind reader liked your article; it is the perfect opportunity to show your best article, an article which is your essence, your story, the one writing you are most proud of.
• Ahh. That makes sense. How do you do that?

• Let me show you mine: My credo: The Mystery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humour, and I am also happy to tell you that, this is my article about which I am the proudest of now.

• Wow. You are so clever, Miki. You pasted it here. You make sure your readers will check it.

• Yeah, of course, but don't worry, I will paste it to the end of my story too, to be on the safe side. 😊 By the way, I noticed you recently started to use the word AKA. What does it mean?**
• Do you want to hear the answer? It is pretty long.
• Yeah, sure.
• So AKA has many meanings:
• AKA is a language in Sudan and the Central African Republic and also in India(Hruso).
• many people are called AKA, like the South African rapper Aka).
• AKA is a village in Japan, India, Iran, and Hungary. By the way, I had never heard this name before, only Ajka. They might have misspelt it. I could list many other meanings, but instead of that, just check Wikipedia.
• Thanks Miki for this in-depth explanation, but it does not make any sense. Is there any other meaning of AKA? Sure, I just wanted to play with you a little bit.

AKA means Also Known As.

• Ahh. Cool. Don't you think you are overusing it, and it will make your readers annoyed?
• I am pretty sure there will be some readers who will stop following me cause of this, but it makes it easy to recognise my articles just by the title.
• Makes sense. But Miki, you should not have written this here. What if other people will also start using it?
• Of course, I also thought about that, but I can quickly adapt so that I can come up with other titles, and in addition to that, I am compositing my images to make a unique cover.
• Yeah, I like them. Especially the one in The Mystery Of The Small But Cute Refrigerator On The 3rd Floor - My First 3 Months At DMG MORI HEITEC Digital Kft.. So do you think this is enough to make you stand out from the thousands of bloggers?
• Of course, I am not sure. But I have two more ways to achieve that.
• Really? Give it to me!
• 1. The Hashnode Weekly by Miki Szeles
• Yeah, that is unique at the moment. It might be even better than the featured section of Hashnode as you write a few sentences teaser for all the articles.
• Yep.
• But what if other people will start making newsletters too?
• That is precisely my goal. I am even developing a Chrome Extension called Hashnode Newsletter Generator to encourage the Hashnode community to come up with their newsletter.
• Yes, that would be awesome to see many, many newsletters.
• I even have a motto.
• Really? What is it?
• Show me your newsletter, and I will tell you who you are.
• Haha. That was funny.
• It is not a joke. I am completely serious.
• Um. Okay. But do not you afraid you will lose your uniqueness when others start to create their newsletter?
• Nope.
• Why?
• Because nobody else can make a Hashnode Weekly by Miki Szeles newsletter.
• Fair enough.
• You said you have one more thing which makes you unique. Can you tell me what it is?
• Of course. I am writing long articles. Very looong reports with 15+ minutes reading time.

• Ok, I have to admit, that is not usual nowadays when people get distracted every minute.

• Miki! I think we should ask one thing from the Hashnode team.

• Really? What is it?
• Is it possible to write multi-level lists in Hashnode markdown language?
• Great questions.
• Let's ask it together. Are you ready?
• Yepp. 3..2..1.. Go!
• Dear Hashnode Team, is it possible to create multi-level lists in a Hashnode post?
• Thanks in advance.
• There is a problem, Miki.
• What is your problem again, Miki? I am getting tired of you.
• As I earlier said, if there is no ticket about something, then that never happened.
• Ok, but is it a bug, or is it a feature?
• It is a bug, of course. It is always a bug.
• Can you elaborate on this?
• Just wait a few days, and you can get an in-depth explanation in my upcoming story: QA Vs Dev AKA Bug Vs Feature AKA A Never Ending Debate AKA The 7+1 Testing Principles Explained By Miki Szeles.
• Hmm, that sounds interesting. But how the hell could you push so many topics into one article? I am pretty sure your readers will get tired after a few paragraphs.
• Well, I remember the time when I had to prepare for the ISTQB CTFL exam, and I had a tough time memorizing the seven testing principles.
• Yeah, me too. It has su*ked.
• Yeah, and as I am such a nice guy I mentioned one more principle completely free.
• Wow. What an excellent marketing trick. This always works. People like free stuff. They never realise if something is free, then you are the product with which you pay for the free stuff.
• Ahh. I did not know that. Thanks for sharing.
• Ok, so testers will read your article, but what about developers?
• Hehe. I also thought about them.
• So what did you do to keep their attention?
• Well I brought a never-ending debate on the Bug vs Feature to make sure they will stay with me. I even did some detective work again, similarly to what I did in The Mystery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet.
• Do you think is that enough?
• Well I came up with a solution to the problem. And again, it is entirely free. They are lucky, as in the case I have proposed this solution as a consultant, I would have asked for a hell a lot of money.
• Clever Miki. Very clever.
• One last question Miki: Do you think this was enough promo for our upcoming story?
• Yeah, I think so, but to make sure they will read it, I brought a teaser from it:
• Wow, Miki. This is cool. I also want to read it.

• Calm down, Miki. Just a few days and everybody can read it.

• Focus Miki. Focus. You have written 5616 words, and you have told almost nothing about Hashnode Widgets.

• Yeah, you are right, just wait a little bit we will get there after one more thousand words.

• So I went to the Hashnode feature request page, and I wanted to ask the question.

• And? This sounds easy-peasy.
• Well, I only had two choices. Feature request and bug.
• So what? - It would be awesome to have a third option: Question.
• Ok, where is the feature request ticket, Miki? I got to know you by now, so I am sure you have already created it.
• Haha. Here it is.
• Miki, do you think we should ask our readers again to upvote this? Won't it get annoying?
• Yeah, it is very annoying, but still, that is the best option we can do.
• Are you sure? I think there is one more option to emphasise the importance of a feature request.
• Really? What is it?
• I have a universal answer to that: 42.
• Will it answers the Ultimate Question of Life, the Universe, and Everything?
• Yeah, that is precisely what it answers.
• Can you give a little bit more clear answer?
• Ok, my answer, which is as universal as 42 is:

Write an article about it.

• Miki, you son of a bich. *Don't you think the Hashnode team will be mad at you?
• Nope, they are charming people. Usually, they answer my questions very quickly.
• Really? All of them?
• Well, almost. I still have two unanswered questions I sent via email, as there was no question type issue.
• Ah, I see. I am pretty sure you will get an answer soon.

• Me too. 😊

• You lost focus again, Miki. It is high time to move to commandment #3

• Sorry, but this is how my mind works.

Associating and then associating and then again associating, then it gets back to the original idea again.

Anyway, you are right. Let's see commandment #3.

Commandment #3 - Contribute to the Selenideium Element Inspector Chrome! Extension open-source project.

Here it is: Contribute to the open-source Selenideium Element Inspector Chrome Extension, with which test automation teams can save hours daily by automatically generating all the relevant selectors for Selenide, Selenium, Cypress, Playwright, Squish and TestCafe.

• Do you agree, this section is self-explaining?
• Yeah. We can see commandment #4

Commandment #4 - Follow the Selenideium Element Inspector Twitter channel!

Follow the Selenideium Element Inspector Twitter channel to get updated on the latest happenings regarding Selenideium, to get help, to share your experience and also to talk about any (test automation) related topic! 😊

• That is interesting.
• Yeah. As you might know, I got addicted to not just Hashnode but to Twitter too.
• Really? Why?
• Because it is such a vibrant community. You can hear about the most recent news, there are many many fun posts, and who the hell knows what else. It even radically improved my writing.
• Really? How?
• Haha. I won't tell.

At least not now.

But in a few weeks, I will post an article with the title:

How 2 Months Of Tweeting Radically Improved The Quality Of My Writing.

• Wow. That's what I call a catchy title. We might even beat the record of How to Create a Legendary GitHub Profile?
• Stop dreaming, Miki, that is only possible if that article will also be featured daily. dev.

But you know what?

• What?
• I just opened daily. dev to find the link to my article, and I discovered a pretty cool feature.
• What is it? Show it to me!
• You can generate your own dev card. Here it is:
• Wow, Miki. This is an excellent feature. By the way, you look gorgeous.
• No, I am not just looking at my hair. I will be 40 in a month, and my hair is entirely grey.

To be honest my hair started greying 15 years ago.

• Ah. Do you know the reason? What has happened at that time? I do not know the exact cause, but that was when I started working, but also when we got together with my ex-girlfriend.
• Wait, what? I thought she became your wife.

• Yes. That is precisely she is my ex-girlfriend.

• Miki let's get back to the Selenideium Element Inspector Twitter Channel!

• Sure. So let me tell you why I have created it.
• Ok.
• So, I created it to connect and grow the Selenideium Element Community, so they can get help, exchange thoughts and contribute to this open-source project.
• I think that is enough about the Selenideium Element Inspector Twitter channel.
• Yeah. Just one last thing. I wrote an article about it from which you can get more info: Breaking News! Selenideium Element Inspector is Available Both on testdev. Tools and Twitter.
• Why I am not surprised you wrote an article about it? But anyway I started to think.
• Thinking about what?
• To create my own Twitter account.
• What???? We already have a Twitter account.
• Yeah, but that's yours. I want my one.

• No comment.

• Go on, Miki, just two more commandments, and we are ready. I suggest making it short not to lose our last reader too.

• Ok, I will do that. Except if not.

Commandement #5 - Join The Selenide User Group!

Join the Selenide User Group on LinkedIn to connect with more than a hundred test automation engineers and learn and get help regarding the coolest e2e test automation framework: Selenide.

When I started using Selenide, an end-to-end test automation framework based on Selenium Webdriver, I immediately fell in love.

I fell in love with it as it is superior to Selenium as it is built on top of it, so it has the same functionality and much more:

1. No more StaleElementReferenceException (in 95% of the cases, to be exact 😊).
2. Easier syntax
3. Advanced selectors
4. Built-in profiler And much more.

Read more about it in my very first article:

Selecting an End to End Testing Framework - Selenium or Selenide?

Publishing that article was the first step I made on the beautiful writing journey.

At that time I did not know about Hashnode, so I posted it on LinkedIn.

I have noticed something. A guy called Andrei Solnstev liked my article, who is the developer of Selenide.

You cannot imagine how proud I was.

As there are many test automation-related groups on LinkedIn, I looked for a Selenide group, but I realised there is no such group.

So I took the courage and wrote a DM to Andrei in which I explained my idea.

Luckily, he liked it, so the next day, the Selenide User Group was born.

• Ok, Miki. Thanks, let's move on to the next commandment. Hurry. Hurry.
• Sure.

Commandment #6 - Join the Selenideium Element Inspector Bounty Hunting Reward Program and earn ☕s by contributing to this open-source project. 🚀

Join the Selenideium Element Inspector Bounty Hunting Reward Program and earn ☕s by contributing to this open-source project. 🚀 This is the perfect opportunity to make the first step into open-source contributing and if you would like to learn about JavaScript and Chrome extension development. 😊

You can expect an amicable, helpful community, and you can even earn ☕s.

I will even give a shoutout to you both on Selenideium and my personal Twitter account in case you contribute.

What are you waiting for?

Check out Breaking News! Selenideium Element Inspector Bounty Hunting Reward Program Is Here ☕ for more details! 😊

• And we are ready.
• Ok, but why did you put this last one to the end? It belongs to the Selenideium Element Inspector Chrome Extension.
• That is true, but as it contains a huge image, it would hide the other call to action and anyway, closing your article with a funny picture leaves your readers with a good feeling in them.
• What great advice Miki. Thanks. Next time, I will try it too. 😊
• WTF?
• Never mind, just mumbling in myself.

• Ok.

• Mikiii. You have written 7536 words, and it is high time to speak about Hashnode Widgets.

• Ok, there is no point to withstand you. You are so pushy, Miki.

Hashnode Widgets to the rescue

• How did your relationship with Hashnode Widgets start?
• I have recently read an article from my pal Jorge Romero.

In this article, he mentioned Hashnode widgets. As he is usually telling intelligent things, I had a look at it, and I immediately realised how awesome Hashnode Widgets are.

• What caught you in Hashnode Widgets?
• Her eyes, of course, and her face too.
• Come on, Miki. Tell me the truth.
• Ok. I immediately saw the infinite potential in it.
• Can you elaborate on this?
• Sure. During the last 1,5 months, I have posted many many articles. During this time, my call to action list and text changed continuously as I read, learnt, thought about it, and also because I started to incorporate in new things like blogging on other platforms too.

So, cause of this, I always had to go back and edit all my previous articles.

This was easy in the beginning.

• What happened then? I started to post daily, so I have published 40 articles(including this one).
• By the way, can you tell our readers, how old are you?
• I am closer to 30 than to 25.
• Really? I did not think you were such young. How old are you exactly?
• 40.
• What a coincidence, that is exactly how many articles you have written. It cannot be by accident.
• Stop right here. I do not believe in numerology.

• That is very stupidwise.

• So , what the problem with your daily posts was?

• As I continuously changed my call to action list, I always edited all my previous articles. Can you calculate what does it mean?
• No. I am not good at math.
• Well, that means exponential growing which means complexity.
• Sorry, but I do not get this mumbo jumbo.
• It means that I have to spend a hell of a lot of time updating my article!
• Ok. I got it. You do not have to be rude.
• You are right, sorry, but I cannot bear slow-minded people.
• Really? I thought you enjoy helping others and explaining everything in a digestible way.

• That's true. It looks like I am a better person than I thought.

• Let's continue. Was there a disturbance in this short period of your relationship?

• Sure. Right at the beginning.
• Wow. What happened?
• I have created a perfect call to action list, and she messed up everything. In a minute, the whole list looked like an ugly dollop.
• Well, that is not nice. How did you deal with it?
• I kindly asked her to do that again.
• Did it help?

• I do not know; we are not talking since then.

• Are you planning to have children?

• Well I already have one from my previous relationship. His name is Selenideium Element Inspector, but we are working on the project.
• Have you already decided what they will be called?
• Yes, their name will be Hashnode Newsletter Generator.
• Wow. What a lovely name.

• Yes, I think so.

• Miki, we are running out of time, do you have any last message for our readers.

• Sure. Just to teach something in this helpful article:

The word mumble is called motyogás in Hungarian. 😊

• Miki, thanks for the interview. It was a pleasure to meet you.
• Thanks to you too.

Just one last question.

• Yes?
• When will the interview be published?
• In a few hours, right after our designers are ready with the cover image, and right after, our painters highlight the primary information in this article. We have to hurry to make it into the Hashnode Daily Top10.
• Well, the painting won't take too long.
• You are right, Miki. You are right.
• Is that all?
• Umm. Not really. I have to admit we have a slight bottleneck here.

We have just employed an expert to raise the quality of our writing to a new level.

• Phew. Is it someone I know? What is her name?
• Her name is Grammarly Premium.
• I know her, at least her son Grammarly. We are great friends. I have learnt a lot from him. So what is the expert's opinion about this article?
• Well, she gave the advice to correct all our spelling mistakes, so we already did that.
• What is the problem then? The primary purpose of Grammarly is to correct your spelling mistakes.
• You are correct if we talk about Grammarly Premium's son, the little Grammarly, but his mother is much pickier.
• How much more?
• Guess how many corrections she suggested!
• 10?
• Upper!
• 50?
• Nope, go further.
• 100???
• You are not even close!
• Don't play on my nerves. How many corrections did she suggest?
• 415!!!
• No way. 415? That is crazy.
• Indeed.
• Will you correct all of them blindly?
• Of course not, as we also have our original experts, and we value their opinion.

I also heard that Grammarly Premium sometimes could be too official, which is not exactly what we want.

• Ok. then I wish you good luck; I guess you already lost the hope to be in the Top10 today, but maybe tomorrow.
• We will see Miki. We will see. Thanks for the interview again. I am not used to such long discussions, but I enjoyed every minute.
• Thanks too, Miki, the pleasure is mine.

Thanks for reading James, Mary, 若汐, 沐宸 and everyone else. 😊

What is your call-to-action list? Share it in the comments section!

Please share this story on social media if you enjoyed reading it so that I can reach more people! 👍🤣

Please share this story on social media if you learned something useful, so more people could benefit from it!👍📚

Please share this story on social media if you suffered enough while reading it! Let the world suffer!👍😈

Please share this story on social media, no matter what!😊🧡

My credo: The Mystery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet Read my story, in case you would like to understand how I think and act as a developer and tester in the real world. You can get some insights about my humour, and I am also happy to tell you that, this is my article about which I am the proudest of now.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to, on Hackernoon and even on Instagram. 😊

Contribute to the open-source Selenideium Element Inspector Chrome Extension, with which test automation teams can save hours daily by automatically generating all the relevant selectors for Selenide, Selenium, Cypress, Playwright, Squish and TestCafe.

Follow the Selenideium Element Inspector Twitter channel to get updated on the latest happenings regarding Selenideium, to get help, to share your experience and also to talk about any (test automation) related topic! 😊

Join the Selenide User Group on LinkedIn to connect with more than a hundred test automation engineers and learn and get help regarding the coolest e2e test automation framework: Selenide.

Join the Selenideium Element Inspector Bounty Hunting Reward Program and earn ☕s by contributing to this open-source project. 🚀 This is the perfect opportunity to make the first step into open-source contributing, and also in case you would like to learn about JavaScript and Chrome extension development. 😊

You can expect a friendly, helpful community, and you can even earn ☕s.

I will even give a shoutout to you both on Selenideium and my personal Twitter accounts in case you contribute.

What are you waiting for?

Check out Breaking News! Selenideium Element Inspector Bounty Hunting Reward Program Is Here ☕ for more details! 😊

As you might already know Selenidium Element Inspector is an open-source Chrome extension with which test automation teams can save hours daily while they are automating tests via using Selenide, Selenium, Cypress, Playwright, Squish and TestCafe frameworks.

The Backstory

In the last few days, Selenideium had its first 2 contributions.

The first one was a bug report (yeah, bug reports are so important I also count them as contributions ) by TheDevilOfJesters from Pittsburgh 10 days ago. He noticed the Options page showing "Selenium Java" 3 times instead of showing Selenium Java, Selenium Javascript and Selenium C#.

Thanks again for the bug report Jester. 🧡😊

I have to admit however I reacted quite quickly I did not start working on the bug as I was busy writing

1. My First Month on Hashnode - A Retrospection About Blogging on Hashnode Developer Journaling Platform by Miki Szeles

2. Hashnode Weekly 004 by Miki Szeles

3. The Mistery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet

All of them are related to software development and blogging, so I highly recommend checking them in case you have not done it yet.

I did not consider the bug showstopper as you can figure out the real meaning of the options with a few clicks, so I left the source code untouched for a few days.

And that is the story, how the second open-source contribution has happened as Jorge Romero submitted a bugfix in the form of a merge request for it.

Thanks, Jorge. 🧡😊

As I am already using buymeacoffee.com which is a great solution to provide the option for my readers to support me, I decided to buy a Coffee for Jorge.

It is of course far from being paid as you would get paid for your daily job, but I remember how happy I was when Maddy bought a coffee for me a few days ago. Thanks, Maddy. 🧡😊

In addition, to show my gratitude for the bugfix I also wanted to show my gratitude to Jester for reporting the bug. So I told him I would like to buy a coffee for him, but I am still waiting for his Buy Me a Coffee link. 😊

And that was the point when the idea of the Selenideium Element Inspector Bounty Hunting Reward Program was born in my mind. 😊

The Selenideium Element Inspector Bounty Hunting Reward Program

The program is very simple. As soon as you do one of the following, I will buy you a coffee:

• Report a valid bug

• Submit an approved feature request

• Fix a reported bug

• Implement an approved feature request

• Write an article about your experiences with Selenideium Element Inspector. In this case, you can be sure I will share your article on Twitter and LinkedIn too.

QA

Q: Can I get a ☕ for multiple bug reports?
A: Sure, just make sure you submit them as separate issues.

Q: Can I get ☕ for fixing my own bug report/implement my own feature request?
A: Sure. And in case you do that, I will buy 1 extra coffee for you.

Q: Can I get a ☕ in case I write negative things about Selenideium Element Inspector?
A: Having one-two area of improvement mentioned is absolutely ok, but in case it is a completely negative article, then I won't pay a ☕ for it, but instead of that I offer you a 15 minutes long video call, so you can share your experience with me, based on which we can further improve Selenideium Element Inspector.

Q: What if I contribute a lot? Can I earn extra ☕?
A: Sure. I really admire returning contributors, so after every 5 contributions, I will buy an extra ☕ for you. 😊

Q: I love Selenidium Element Inspector as I can really save a lot of time daily. Can I buy you a ☕?
A: Sure. Just click on the link below!

![](https://img.buymeacoffee.com/button-api/?text=Buy me a coffee&emoji=&slug=theashishmaurya&button_colour=FFDD00&font_colour=000000&font_family=Cookie&outline_colour=000000&coffee_colour=ffffff align="left")

Follow these steps:

1. Download the Selenideium Element Inspector

2. Use Selenideium Element Inspector

3. Check the source code on Github

4. Report your bug/feature request

5. Submit fixes and feature implementations

6. Get a ☕

7. Go to 2.

In order to motivate you for sharing the news, I will select 5 people randomly from those who share this article on Twitter in the upcoming week. Just do not forget to tag @selenideium. 😊

Happy Bounty Hunting! Enjoy your ☕. 😊

Still, have questions? Ask it in the comment section! I will update the post with the answers.

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to and even on Instagram. 😊

![](https://img.buymeacoffee.com/button-api/?text=Buy me a coffee&emoji=&slug=theashishmaurya&button_colour=FFDD00&font_colour=000000&font_family=Cookie&outline_colour=000000&coffee_colour=ffffff align="left")

Weeks passed and I started to hear rumours. There was a case when a Túró Rudi disappeared from it, and there was another case when a full packet of ham and cheese disappeared without any clue. I even heard a story when there was a sticky note on the food with the name of Alan on it, but by the next day (no it was not the weekend cleaning) it was gone.

DISCLAIMER: In order to protect the safety of our hero's loved ones, I have changed his name to Alan.

But as you might already know in case you read my The Mistery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet writing, you already know I really love detective stories. I highly recommend reading it it is only 17 minutes long. I promise, you won't regret it, but if yes, just come back here and shout madly in the comment section. 😊

So I leave here a clue for you:

DISCLAIMER END

I was quite a sceptic in the beginning. It is such a nice refrigerator, it cannot be true it steals our food. I thought maybe Alan put his food in the other fridge, or he has blackouts during which he eats his food not remembering anything afterwards.

I remember we were talking with Alan while we were bringing in our daily confectionery portion into our bodies. I admit he made a mistake here. He only ate half of his Hungarian Sponge Cake, actually he could learn from me as I always eat every bit of my cake. Let's forgive this to him for now.

While we were talking he recalled a story when his food mysteriously disappeared from the refrigerator. In order to prevent it from happening again, he picked up his fork and mixed the cake till it became an ugly dollop.

He put it back in the refrigerator and we continued working till we went home.

We usually come early in the morning and have a coffee together where we talk about life work and everything else. But this occasion was different. I will never forget his face what I saw in the morning, it has been burnt into me for an eternity. I just hope nobody has to see that face again. A tragedy happened.

The Ugly Dollop Hungarian Sponge Cake Has Disappeared.

That was the moment when I started to believe in the urban legends of the refrigerator. One week came after the other and I heard more similar stories. People were trying to guess how it is possible so many things are disappearing from this small but cute refrigerator on the 3rd floor.

Then I suddenly enlightened. I found the only possible answer for the situation.

There Must Be A Black Hole In This Small But Cute Refrigerator.

There's no other potential explanation. I was sure, somewhere in the universe, there is a place which is full of half-eaten sandwiches, cakes and of course "Túró Rudi". It must be completely similar to the black hole which sucks every half pair of socks. "Billions of socks have been lost since the dawn of time – but only ever one, never a pair".

Actually, I found a workaround to the problem of the missing socks. I've ordered 50 pairs of black socks from Amazon, so I, not just don't have to worry about losing some, but I do not have to pair them at all.

But let's get back to our story. We were standing there, completely shocked. We had no idea what to do. Alan tried to convince me there might be other explanations for the situation than just the black hole, but I was adamant. Using Occam's Razor there can be no other explanation as my idea was the simplest one.

I am sad to tell you that this mystery is still unsolved up till now. So to be on the safe side we told Alan to put a huge amount of laxative liquid into his food next time. I can just hope he won't forget about it. That would be quite unpleasant recognition for him.

Next time, when you open our small but cute refrigerator on the 3rd floor, and you see some food with the name Alan on it, or with any name, or any food without a name, please feel some empathy towards me. I honestly never ever ever ever ever want to see that face again.

In case I still have not convinced you, then just simply remember our advice...😊

In case you enjoyed reading this post please show your support by sharing it on social media!❤😊👍

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to and even on Instagram. 😊

Hashnode Weekly Newsletter

Ok. You got me. I know I f..kd up again. It is Sunday. But I have a very good excuse for why I was late in both cases. 😊

Apologize

Last week I was working hard on writing My First Month on Hashnode - A Retrospection About Blogging on Hashnode Developer Journaling Platform by Miki Szeles which took me approximately a dozen hours. No matter whether you are blogging on Hashnode or not, I highly recommend reading it. 😊

This time I was writing The Mistery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet which took me around 10 hours, and as I also played a lot with my son I had no time starting writing Hashnode weekly, especially as I still had ~30 articles on my reading list. But to convince you to forgive me, I brought 67 amazing Hashnode articles this week. 😊

In case you would like to know how I see the world as a software developer and tester, and in case you would like to have an intro to my humour, I really recommend reading it.

As you might already notice I really enjoy reading and writing very long high-quality articles. The above mentioned 2 article has a reading time of 34 minutes and 15 minutes.

That is a lot and I know most people usually like to read much shorter posts. But in order to make my content digestible, I help my readers (you) in multiple ways:

1. I include a table of contents at the top of the article, so you can quickly understand what you can expect
2. I always highlight the most relevant information in bold, so you can run through the article quickly, decide if it is interesting to you or not.
3. I split up my articles into bite-sized chunks, each of the paragraphs talking about one topic and I also make sure you can understand what is the main thought in the first 1-2 sentences so you can quickly skip the paragraph in case you are not interested.
4. I include tons of links to related material so you can learn much more about the subject than you can get from my article.
5. I use a catchy but descriptive and relevant title, so you won't be disappointed after opening my post.

So as you can see it is completely up to you whether you would like to spend 1 minute, 34 minutes our hours by following the links in my articles.

That's enough for an intro, so let's back to Hashnode Weekly.

Hashnode Weekly

I have started Hashnode weekly 3 weeks ago in order to collect the hidden gems of Hashnode without which those articles wouldn't get too much attention as luckily there are a huge amount of great posts coming out daily.

I also dedicate a session to the new bloggers, so I can help them to connect with their audience, and they can also get some motivating nice words from the Hashnode community. Up till now, I have posted 4 Hashnode Weekly:

1. Hashnode Weekly 001 by Miki Szeles
2. Hashnode Weekly 002 by Miki Szeles
3. Hashnode Weekly 003 by Miki Szeles
4. Hashnode Weekly 004 by Miki Szeles (Be careful this one to make sure you do not get into an infinite loop, as this is a recursive reference 😊)

Here are the stats:

1. Hashnode Weekly 001 - 226 views, 8 comments and 27 interactions.
2. Hashnode Weekly 002 - 291 views, 13 comments and 45 interactions.
3. Hashnode Weekly 003 - 281 views, 15 comments and 72 interactions.
4. Hashnode Weekly 004 - This is up to you, so I kindly ask you to comment, interact, share so we can beat the record. 😊

I am pretty happy about this result which we achieved together in this short period of time.

Before we get to the other topics, let me tell you a few words about Medium Weekly.

Medium Weekly

As I am reading Medium also and reposting my Hashnode article there, I also started Medium Weekly from which I have two:

1. Medium.com Weekly 001 by Miki Szeles
2. Medium Weekly 002 by Miki Szeles

But I decided to stop writing Medium Weekly, as I prefer to focus my time on the Hashnode community which is much better according to my experience.

That's enough about the Weekly Newsletters, let's continue

Featured Topic - Women In Tech

As you might slowly get used to it I always highlight one article/topic in my newsletters.

🏆 International Women's Day was 5 days ago on the 8th of March. It is a special day for every woman but is even more special to the tech community as we are celebrating Women in Tech. 😊

I even wrote my own article to support the Women In Tech movement: Happy International Women's Day - Miki Szeles's words about Women in Tech 💝.

But something happened yesterday, which radically changed how I think about the topic of Women In tech.

This event was reading this tweet on Twitter. It is in Hungarian, but you will get the main points of it in case you keep on reading.

In my opinion, there are 2 main goals of the Women In Tech movement:

1. Inspire more women to join the tech world. The movement is highly efficient doing this and it really helps.
2. To achieve gender equality. Unfortunately, I think the current approach does more harm than good.

Let me explain why.

By talking about women in tech we split people into 2 separate groups women and non-women and with this, we draw more focus on whether somebody woman or not, which is exactly the opposite of what we would like to achieve.

So instead of promoting women in tech, we should promote:

• Great leadership
• Delivering great and valuable work
• Communicating real results
• Focusing on fulfilling the requirements of clients and customers
• Promote employing and adequately paying appropriate professionals
• Promote helping each other

In case you look at the list you can see there is one common thing in all of them:

It does not mention either women or men. Why?

Because it is irrelevant, that is not what we should focus on.

So this is how my view changed recently about the topic of Women in Technology.

As I am continuously learning about the world my worldview is constantly changing, so I kindly ask you to share your (opposing) thoughts in the comment section, so I can further form my views.

Before we move on to the other articles, let's provide the list of articles on the subject of Women in Tech from this week:

• Eleftheria Batsou Why We Need More Women In Tech
• Nic Women in Tech
• Swati Sarangi Women In Tech
• Devhouse Women In Tech: Interview with QA team lead Natalia Demianenko
• Susmita Dey My Journey of Being #WomenInTech
• Roshaan From not being able to format a USB to landing my first internship as a high school junior ; here is my story
• Abbey Perini We've Been Here Since the Beginning

Blogging, Writing, Journaling, SEO

🏆 My top pic is Sandro Volpicella's post in which he shared some cool tips regarding SEO for Technical Content Writers. I also added my thoughts:

For SEO I am using Scrapy at the moment which has a quite good price-value ratio.

In the past, I have used Semrush (which is still much cheaper than Ahrefs the tool mentioned by Sandro) but in terms of functionality, it is unbeatable. I am pretty sure I will use it in the future too.

At the moment I am focusing on writing lots of great quality content using the techniques I have learnt in the past, making sure to achieve as little bounce rate as possible.

Later whenever I will use Semrush again, I will tweak my articles to have an even better SEO result. 😊

There is another great article in this category:

• Karthikeyan developed a very interesting project for the Hashura Hackathon with which you can cross-post your articles to multiple platforms. Learn more about it here: Introducing Kross post - Cross posting made easy

Software Development, Testing, Technology

🏆 This week I am featuring Parvin Eyvazov's freakin cool project called JSON Translator.

With his solution, you can automatically translate your JSON language files with the aid of Google Translate.

What a great solution to add support for all the languages in the world in your product.

I have already sent the link to my teammates, I am pretty curious what will they say. I suppose they will be amazed just like me. 😊

Read more here: FREE! Translate your language JSON file to any languages.

Here are the other also great articles:

• Rajat Thakur introduces the different techniques of web scraping in his article: What Are The Different Types Of Web Scraping Approaches?.
• Maddy gives 4 tips to easily get coding experience
• Diseyi Philomena compiled a list of non-coder and coder career options in her writing Your First Introduction to Tech. I only disagreed with one point, in case you are interested in which one, just check the comments. 😊
• Vidhi Jain brought as Spring Boot Interview Questions and she even provided answers for them.
• Kusumita Ghose gave some advice on How to get started with Competitive Programming?. This is a great post for those who like competitive programming but I am not one of those and I have a quite firm opinion about the topic, let me share it with you.

Personally, I do not really value competitive programming too much. Learning complex algorithms and the overoptimization of them has very little value in real life. Only a few per cent of the jobs really need it. Of course, it can form your thinking but there are other ways for that too, like solving real-world problems, which won't get as repetitive as doing the 100th of HackerRank challenge.

Also, programming at a very fast pace can do more harm than good. It is much better in case you take the time to think through and design your solution, which will be much more profitable in the long run.

Believe me, I had to solve many of those challenges at university, but haven't seen them in my 15 years of software development career. In my opinion, those challenges are only good for one thing, to get into companies who think that you can measure a developer by how much he/she practised the coding challenges for interviews, instead of checking whether he/she can solve a real-world problem.

• Pacifer York shares the list of The Coding Skills You Need For A Career In IT/CSE which can be very useful for people just starting their career as a software developer.
• parveen yadav has a strong C++ background but as the world was looking for Java developers mostly he changed his mind. Read more in his post: A Second chance as Software Engineer
• Yoshi shared an excellent diagram about the Architecture of Chrome Extension. This post is highly relevant to me as you might already know I got addicted to developing Chrome extensions. I have already released Selenideium Element Inspector in the Chrome Web Store about you can read more in my writing Save dozens of minutes daily during writing Selenide and Selenium E2E automated tests using the Selenideium Element Inspector Chrome Extension! and at the moment I am developing Hashnode Newsletter Generator with which Hashnode bloggers can easily create their own unique newsletter. My motto is: "Show me your newsletter and I will tell you who you are". 😊
• Zaheer khan also wrote on the topic of Chrome extensions in which he leads us through step by step on how to create a Chrome extension in his post Chrome Extension Tutorial.
• Paloma gives her advice on How to Get out of Tutorial Hell. I can highly relate to this as my Udemy library looks like just my Steam library, full of never touched content which I bought whenever there was a sale. 😊
• Deepa Goyal introduced the evolution of APIs in her writing A Visual History of APIs with an excellent infographic.
• Rafael Câmara explained the SOLID principles about which every software developer should know. He also posted about REST API Maturity Levels and he happily shared his thoughts when I asked him whether implementing HATEOAS would be useful for us or not. 👍
• Aashish Panthi shared a list of Free Resources for Developers and Designers.
• Salman Shaikh developed a very interesting project with which women can alert their friends in case of emergency. Read more about it in his post: Women's Safety Device Using Arduino, GSM and GPS Module
• Ahmed Ramy wrote an article with the title Test-Driven Development: #6 Testing Alerts, Popups, and Messages and he even got featured here on Hashnode.
• Ifeoma Lydia Amaranjo wrote a cool post with the title My Understanding on UI and Ux Design
• Opemipo Disu is a 16 years old developer from Nigeria. His story about cyberbullying really touched my heart. He even created a very valuable project called Aurora to stand up against cyberbullying. I warmly recommend reading his post: Aurora: An application that helps fight cyberbullying.. 🧡😊
• mahmoud elaraby bought 80+ hours of tutorials for java from which he only finished 15+ hours and he has serious doubts whether he is on the right track or not. I gave my advice to him and I suggest you do the same.
• Marco Gancitano shared his thoughts regarding What makes a senior developer?. I also added 2 more points:
• According to my Team Manager a Senior Developer can deal with a multiweek long task, he/she can split it up, delegate, monitor and deliver on time.
• Being a senior developer is not just about technical knowledge. Soft skills are equally important. I highly recommend reading this post (especially to you Bence Hornyák😊).
• Lucy Karimi shared her experience of being a first-time contributor to open source..
• Dipanshu Torawane explained to us What is DevOps?🤔
• Wdzz created his own API called AnimaliAPI with which you can query for animal classification and their scientific names. Learn more about it in his post: My first API is available to over three million developers.

Productivity, Psychology, Self-improvement, Life, Creativity, Learning, Jobs, Leadership, Motivation (Sorry but I did not want to call this section Other topics😊)

🏆 My top pick from this category is Ayyash's article in which he shared 5 lessons he learnt during 20 years. I found the post very insightful with which I can highly relate, so I would also like to share my thoughts related to the article.

Ayyash mentioned Notepad as the one to go note-taking app. I almost completely agree with him as I have tried so many solutions for notetaking like Word, GoogleDocs and products like EverNote.

Recently I started to use Notepad++ and nothing is compared to it. It is blazingly fast. One downside is that I cannot use an image, but I usually have a belonging Google Doc where I save them.

The physical notebook was never an alternative for me as I am way too slow with it compared to Notepad++ and I need my notes to be easily arrangeable and quickly searchable. I back up my notes via GitHub, so I even have the whole history of my docs.

He also advised organizing your email inbox based on what you would like to do with the email. Regarding this topic, I highly advise checking David Allen's GTD method.

David suggests the term zero inboxes, which simply mean you should have no mail in your inbox. Well, I have to admit I am not good at it, I have 25960 emails in my Gmail inbox. 😊

He suggests the following structure:

• Delete: get rid of (or archive) emails that serve no further purpose.
• Delegate: if someone else can answer the email better, forward it to them.
• Respond: respond immediately to emails and not keep them open.
• Defer: move the messages that will take some time to respond to a separate category.
• Do: make sure you stay on top of emails that require a timely response. Ayyash describes a scoring system that you should use whenever you have to select from multiple options.

I also have my own scoring system. Despite being binary it works quite well. I compare the aspect of 2 things, and the one which is better gets 1 point. I used this system whenever I have chosen testing frameworks. Selecting a Load And Performance Testing Framework - Gatling vs. Grafana k6 Selecting an End to End Testing Framework - Selenium or Selenide?

Let's see the other great articles about these topics.

• Mridu Bhatnagar shares 22 questions that can help whether you should quit your job or not in her writing How to decide when to quit your day's job?.

I just recently read Seth Godin's The Dip book which also gives some great advice on quitting but not just quitting your job but quitting basically anything. I was amazed how Seth can write an almost 200 pages long book about a message which can be articulated in 3 sentences. Despite this, I still recommend reading it, even if you finish it in 15 minutes. 😊

• Jorge Romero is a very productive writer, at the moment he is posting every day, which might or might not change when he will start participating in his first Hackathon. He always amazes me as he is drawing his own cover images which I am pretty sure you will quickly recognize whenever you open the linked pages. In addition to this, he knows just about everything. 😊 Here are 5 articles from him: How to make a cover image, Networking for Success!, Developer Dialectics, Plans for my blog and I'm participating in a Hackathon!!!!. Enjoy 😊
• Carlos Balbuena shares 3 tips with which a programmer can boost its productivity in his article Productivity for Programmers.
• Jewel Keith compares different learning models in her writing Mastery-Based Learning vs. Factory-Based Education Model: A Review of Launch School’s Documentation. We had a great discussion in the comments section. Just read it if you are interested. 😊
• Frank Elda posted about a very interesting topic, the aspiration list (which is a list of values, attitudes, directions that you want to follow in your life) with the title I stole a secret from a $100M company CEO: the Aspiration List.
• Conor Bronsdon posted Kathryn Koehler's article with the title Creating a Culture of Engineering Productivity at Netflix. Kathryn is the lead of the Productivity Engineering team at Netflix. The purpose of the team's existence is to boost the productivity of other teams. Pure awesomeness.

In case you would like to know more about what she is doing, then register for the free Interact conference which will be held on 7th of April. 😊

• Shiju Nambiar brought a very important topic with his writing Fixing my Imposter Syndrome. I can highly relate to this topic as my last 5+ years was the worst period of my life both personally and professionally. I even wrote my story which includes impostor syndrome, burnout, years of depression and more, but I was not brave enough to share it with the community.
• Oni Ebunoluwa Mercy also shared his thoughts on [The Myths about Imposter Syndrome and Its symptoms].(https://ebuntoday.hashnode.dev/the-myths-about-imposter-syndrome-and-its-symptoms-cl0mn5ffv0150xlnv33jq8eo2).
• Mridu Bhatnagar wrote a book review about The Practice by Seth Godin (Book Gist). It is again a book from Seth Godin and based on the article it has a little bit longer message than The Dip book. 😊
• Antonio Dinkins shared his thoughts on why it is better to do things with others in his post Don't Struggle Alone.
• Srinivasan Rangarajan lists 5 Types of Bad Managers.

I recently moved to an international company from a very small one and in order to be prepared I watched The Office and the IT crowd. Luckily the situation is much better than I expected I haven't met with the above-mentioned managers (yet). 😊

• Shawn Axsom gives some time management tips in his article Survival, Time Management, and Mattering as a Director of Engineering.

One of them is to only start a newsletter in case you have a vision and concrete goals.

Luckily(intentionally) I do have a vision and goals for my Hashnode Weekly Newsletter. Here they are:

• Draw attention to the hidden gems of Hashnode
• Have a reference for myself
• Help people from the community to find the best writers in the topics they are interested in
• Broaden my audience
• Got featured on Hashnode, to let more people know that dozens of great articles are being born on Hashnode weekly.
• Joaquim Da Costa: The title says it all: Corporate VS Startup Jobs:
• Alagbala Damilola shared his thoughts about productivity in his writing 🦋 On the Subject of Creativity. He also provided a great list of resources on the subject. Check it out! 😊
• Mridu Bhatnagar gave some advice with the title Things to do when you join a new organization?.
• Kalima Quotes wrote about the Benefits of Reading Motivational Quotes.

Luckily, at the moment, I do not need any quote to get motivated as my motivation level is higher than ever before thanks to the constant positive feedback of the Hashnode community and my colleagues. But I won't be mad at you in case you leave some nice words in the comment section, to make sure I keep this level of motivation. 😊

In the past, I really got a huge motivation boost from watching motivational videos. My favourite motivational video creator is Mateus M. Let me share the video I like the most:

Data Analysis, Data Science, Big Data, Machine Learning, Deep Learning, Artificial Intelligence, Robots

🏆My top pick is Syed Jafer's article in which he wrote about ML pipelines in quite a detailed way: Machine Learning Pipeline and Feature Engineering.

• Amr Khaled shares many code examples about How to - Data Analysis With SQL. At the moment we are only using CSV and XLS files, but I saved it for reference for the future. 😊
• Adam recently went through a lot of interviews and he shares his tips on How to Prepare for a Technical Data Engineer Interview.
• The TomTom Developers brought a very interesting topic: Data Visualization in their writing: Visualizing TomTom Traffic Data with Data Science Tools.
• Kim Minori wrote a very interesting story with the title A quick story about robots, from Turing and Asimov dreams to modern robotics institute
• Adarsh Singh explained How does ML Model work?.

Cybersecurity

🏆My top pick (and not just because there are no more articles) is Precious Eyoh's post in which he explained 7 Cybersecurity Threats You Must Know as a Web Developer. I also gave the advice to use the free OWASP ZAP tool with which you can test for the 10 most "popular" security issues.

Blockchain, Crypto

In case you read my article The Mistery Of The Supposedly Red ❤ Emoji AKA The Story Of How I Became A Software Developer Detective To Debug The Internet then you already know at the moment I am interested in a lot of topics except blockchain and frontend development. In spite of this, there were 2 articles that raised my curiosity so I read them and I am sharing them now with you. 😊

🏆My top pick is Abhishek Tiwari's Is Physical Art Getting Obsolete? Understanding NFT Digital Art. post in which he introduces us to the world of NFTs.

Another great article from this category is the writing of xuanling11 in which he talks about a very interesting term in the crypto world: Crypto Comics - What is Aping. In case you would like to know what is aping, just read the post. 😊

Hashnode newbies

• Randy Knight is a former Sysadmin who is studying to be a Web Developer and he also has a cybersecurity background. In addition to this, he is a disabled military veteran and life member of the DAV. He introduced himself in his In the beginning... writing.
• AliciaBytes is a German pansexual polyamorous trans woman, software developer and giant dorky nerd. She had a blog before but deleted everything with her transition. Now she started blogging again here on Hashnode. Here is her first post: Hello, Web 👋 I'm Alicia and this is my new website.
• Designegy Creatives who is a data analyst wrote 2 posts in the first she introduced herself Introducing Myself and in the second she wrote a very exciting project related to Jupyter notebooks. I fell in love with Jupyter notebooks recently since we started to use them in the Data Analysis class at the university. With Jupyter notebook, you can write code and document it using markdown parallelly which makes it very easy to share your projects with other data scientists (and with any python developer).

Unfortunately at the moment, her website is not accessible, but hopefully, she will realize it after she got notified cause of the mention.

And that's it. I hope you found something which is interesting to you. If that is the case, please share your feedback in the comment section.

To close the Hashnode Weekly Newsletter I leave a question here:

What was your favourite article you read during the last week? Share it with us in the comment section to make sure great content gets more attention. 😊

Share this post on social media so we can make sure great content reaches their great audience. ❤😊👍

In case you missed the previous Hashnode Weekly Newsletters, you can find them here:

1. Hashnode Weekly 001 by Miki Szeles
2. Hashnode Weekly 002 by Miki Szeles
3. Hashnode Weekly 003 by Miki Szeles

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to and even on Instagram. 😊

In order to make sure you won't get into the same situation, I decided to share my story with you.

The Crime

I really love using emojis. Here is the ordered list of my favourite ones:

😊❤🤣😱👍

By the way, which is your favourite emoticon? Just post it in the comment section!

As you can see, the supposedly red ❤ emoji is my second favourite. So you can imagine how I freaked out when I saw this on an early morning:

And not just the Hashnode software developer blogging platform affected, but also platforms like Facebook, Medium, dev.to and even Gmail.

It immediately became clear, there is a worldwide conspiracy behind this including Hashnode, Facebook, Medium, dev.to, Gmail and who knows who else. 😱

Denial

At this point, I could not accept the theory of the worldwide conspiracy which includes Hashnode, Facebook, Medium, dev.to, Gmail and who knows who else.

So as I was in the complete dark regarding why this tragedy happened, as a first step, I did what every software developer would do: I have looked for a workaround. 😊

This is how I found the orange 🧡 emoticon.

Good, good but it is far not as good as the supposedly red ❤ emoji. I couldn't articulate why I like the supposedly red ❤ much better, so I did some research to find the answer.

Did you know colours have meaning? I always presumed but I never took the initiative to find it out. Up till this time. 😊

There is much more in the colours than you might think at first.

I found the answer on Designs.Ai. Let me quote from the site:

Red is a bold, warn color with a rich history. Utilization of this color can be traced back to antiquity, where it was viewed as a shade of vitality, festivity, evil and disaster. Red has also been widely used in art, from the days of the Renaissance to today's contemporary art. Additionally, the color Red was utilized in Byzantine dresses to showcase status.

Red is seen as a color of love, primarily used during two of the biggest holidays of each year, Valentine's Day and Christmas. Red also represents other extraordinary emotions, ranging from anger, victimization and danger to warmth, enthusiasm, and sexuality. Pair red with other primary colors, yellow and blue to create bold, vivid palettes, or pair red with browns to create a warn palette.

Red hex code: #FF0000

And here is the description of orange:

The color Orange has a similar name to the sweet citrus fruit, and it is made by mixing the primary colors, red and yellow. As it is a secondary color, many hues use this as a base shade. Orange also comes in varying brightness, intensity, and depth. Orange marries the fierceness of red and the cheerfulness of yellow, often being associated with youth, vitality, friendliness, casualness.

Orange works well with its opposite color, bright blue, creating an intense, electric color combination. Orange can also be combined with shades of pink to create a softer, feminine palette.

Orange hex code: #FFA500

Can you see how huge the difference is? 😊

Since I lost the supposedly red ❤ emoji my days became greyer(🤍). Luckily my favourite emoji 😊 was with me during this hard period. With 😊 I can easily express in the language of the internet how I feel during most of the day. 😊

Days passed, and I spent most of my nights sleeplessly continuously wondering about what has happened with the supposedly red ❤.

I came up with a second workaround with which I can substitute the supposedly red ❤ emoji:

Take it and use it, it is for free. Just add the following HTML code to your Hashnode article:

<img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1647001545310/47WUcJeSz.PNG" alt="Thanks For Reading I Hope You Enjoy It Share It If You Like It Red Heart Emoji Emoticon Replacement">

It might feel good in the beginning, but I am sure you will have the feeling of missing out on something.

This solution was very cumbersome and I couldn't really use it on other platforms like Medium, Facebook and Gmail, as most of the other platforms do not support embedding HTML.

First I was wondering maybe the supposedly red ❤ emoji is feeling blue(💙) due to climate change, wars, COVID-19 or because there is no optional subscription on Hashnode from which writes could get back a huge part to be rewarded for their efforts. I was even thinking about such depressing things as maybe a tragedy happened and someone died at the Unicode Consortium (who is responsible for the approval of emojis).

It quickly became clear:

In case I do not take the initiative to solve the problem, no one else will do that instead of me.

True story. In every aspect of our lives. 😊

Crime Scene Investigation

This was the point when I decided to become a software developer detective who debugs the internet to solve the mystery of the supposedly red ❤ emoji.

Clue #1

After a quick google search I found the first clue on indiatimes.com I found the first clue.

It suggests the following:

For some, the black heart emoji 🖤 is the perfect emoji for a day when you are sitting inside, feeling angst and misunderstanding. It can mean you are feeling emotional, having a dark day or morbid sense of humour or the sad stuff. However, the emoji has become increasingly used to express support for black people. Black Heart Emoji is the symbol that shows emptiness, lack of emotion as it looks like a lifeless heart.

This black heart emoji can be seen used by people for symbolizing cruel and heartless people. If one person has experienced a traumatic event and is now weakly susceptible to any emotions.

Black Heart Emoji is a part of the Unicode 9.0 standard in 2016. Currently, this is listed in the Smileys & Emoticon category. Using this symbol for any gender or skin tone variations. Black Heart is available on all social media platforms.

In the same manner that sending different coloured hearts have different meanings or they can convey certain messages too.

A black heart is completely black in shade. It may be used to express sorrow, dark humour and sadness depending on the person. A black heart emoji is approved by Unicode 9.0 in the year 2016 and has been added to the list of Emoji 3.0 in the same year.

I support the Black Lives Matter movement from all my heart, but this definitely cannot be the answer to my question as this article is talking about the supposedly black 🖤 and not about the small black supposedly red ❤.

By the way, did you know there are 9 different coloured full heart emojis?

Here they are: ❤💚🤎🧡💙🖤💛💙💜

I do not know what it looks like on your screen by this is what I can see:

Look at the poor small supposedly red ❤ heart, it is not just black but it is smaller than the others. I am pretty sure it is scary as f..k.

Clue #2

As I did not find the answer yet, I continued being a detective and decided to do something which most people would never do.

I opened the second page of the Google search results. 😱😊

Thanks to my audacity to click on the Next button of the google search results page a whole new world has opened to me. My eyes got stuck on a title Heart emoji shows up small & black on Macrumors. I was sure this is the place where I will find the answer for why the supposedly red ❤ icon appears in black.

Skimming through the comments I got to know that others are also clueless and struggling with this issue on their mac, but not on their iPhone.

However, I do not have an iPhone I do have an Android phone so I immediately wrote an email and sent it to myself. Whenever I typed the supposedly red ❤ it really appeared in red so I was optimistic about the result.

A second later the email arrived. And there was it. The supposedly red ❤ icon was really red on my phone. 😊

Look:

Of course, I checked it on my PC too:

Unbelievable. I got one step closer to solving the mystery of the supposedly red ❤ emoji. 😊

Clue #3

My mind couldn't stop. If it can depend on the device, maybe it also depends on the type of browser.

I quickly opened Firefox and Edge and started to write an article, to see whether it works or not.

This is Firefox: And this is Edge:

And they are there. Amazing detective work. Following the clues I found I was able to narrow down the problem to Chrome. I felt like I am getting closer and closer, but let's put a breakpoint here and pause for a moment to examine Chrome a little bit deeper. 😊

Clue #4

I very often have trouble with Chrome, some pages are not working correctly, I cannot log in to certain sites, etc.

The solution in those situations is to start Chrome in incognito mode. That is awesome, going into incognito mode is definitely a thing a detective should do in this situation.

And it works. Pure awesomeness. Sherlock Holmes is nowhere near me. 😊

The Suspects

I am almost sure it is a Chrome Extension that makes my supposedly red ❤ emoticons black so let's see what I am dealing with.

I have 20 suspects from which 2 are my own children. 😱

I already let the older one go to discover the world. You can find him in the Chrome Web Store. Leave him some encouraging words, so he will know he is on the right way. 👍

I am still educating the younger one, but I will let him go in a few days so he can become a valuable member of the Hashnode community. 😊

Can you guess which are my children? 😊

The Interrogation

Let's put all of the suspects in prison and interrogate each one by one till I do not find the sinner.

Stop right here!

I am a software developer. Why would I use an o(n) complexity solution in case I can do that in o(log n) time?

The solution is simple. I sketched a flowchart quickly so you can better understand the algorithm:

Ups. Wrong one. Sorry. 😊

Here is mine:

So let's follow the steps of the flowchart and put all the suspects into prison. As this one can be done in a constant time, it does not add to the complexity.

The theory is simple: In case no crime happens while the suspects are in prison, I can be sure the sinner is one of the suspects. Sounds logical, don't you think? 😊

So I put all the suspects into prison and Yaaaaay. The supposedly red ❤ is really red this time. No sabotage happened. Now it is sure the sinner is here, I just have to find it.

Let's split the suspects into two equally sized groups(partitions) and release(enable) the people of the first group.

No f...ing way. One of the crime scene investigators just sent me a photo: The supposedly red ❤ emoji is black again. Most probably somebody took an airbrush and sprayed my beautiful red ❤ with black(🖤) paint. I just only hope it was not one of my children. 😱😊

Let's split up the partition again, and send the second half of the suspects into prison again(disable).

And here I am: The supposedly red ❤ emoticon is red again. Awesome. 😊

Only 5 more suspects to interrogate and I will have the sinner. Let's separate the remaining 5 suspects into 2 groups. As 5 is an odd number in one group I have to put 3 suspects.

Before I do that, let's listen to their alibi.

• Hashnode Newsletter Generator: I am a youngster. I did not even exist when the crimes started to happen. I love people, especially the Hashnode developer blogging platform community. I will soon help them to create their own unique newsletters. I do not modify your content what you can easily verify by seeing I do not need any permission to operate. My motto is: Show me your newsletter and I will tell you who you are.
• Adobe Acrobat: I am the descendant of the famous Adobe Acrobat with which you can fulfil all your PDF dreams. With my help, you can view, fill in comments, sign, convert and comment documents. I need the following permissions in exchange for that: read your browsing history, manage your downloads, communicate with cooperating native applications.
• ColorPick Eyedropper: I celebrate diversity. Just have a look at my logo, you will immediately realize it. I am a zoomed eyedropper & colour chooser tool that allows you to select colour values from web pages and more. I need only one permission: read your browsing history.
• Facebook Pixel Helper: I am the one to go tool for checking your Facebook advertisements. With my help, you can validate your Facebook pixel implementation. I only need 2 permissions: read your browsing history, modify data that you copy and paste.
• Fonts Ninja: Being a Ninja obviously mean my favourite colour is black. But I also like green, just look at my shirt is totally not black, but green. I have painted it myself. I only need one permission: communicate with cooperating native applications.

Very interesting stories. I do not know how you are with it, but for me, the two most suspicious agents are Adobe Acrobat and Fonts Ninja.

Adobe Acrobat is a powerful tool but in order to do his best, he needs a lot of power. Who knows maybe he never heard Uncle Ben's most important sentence:

Fonts Ninja is definitely suspicious with his black colour fetishism. So what should I do then?

Solving The Mistery

I would not feel safe releasing people who might be the saboteurs, so let's imprison Adobe Acrobat and Fonts Ninja Chrome extension and release the other 3 who seems to be innocent.

Let's see the result: Exactly as I expected. No crime happened which can only mean one thing: either Adobe Acrobat or Fonts Ninja is the saboteur who paints my supposedly red ❤ emojis black.

Oh My God! I am soooo excited, even I do not know who is the contravener as I am doing what any journalist would do: writing my story in parallel to the actual happenings.

I have never been so excited. 😊

Hold on Miki. That is not true. I can list at least 3 examples whenever you were more excited:

1. When you got married to your wife Panni.
2. When your son Levi was born.
3. When you got to know a few days ago that you will get a Hashnode T-shirt from the Hashnode Team.

Ok ok. You are right Miki. Again. 😊

Do not waste the time anymore as I can only keep our suspects in the prison for 24 hours without having any real evidence. So let's solve the mystery of the supposedly red ❤ emoji.

What do you guess? Who is the guilty suspect? Write it down on paper, then share it in the comment section whenever you finish reading the article! 😊

There is no problem with loving the black colour. Even myself a big fan of it. Don't you believe me? Just look at this article. I have written all letters in black colour. 😊

Caue of this my guess is Adobe Acrobat.

So I disabled Adobe Acrobat and here is the result

I can be happy, as I have found the sinner. But I never let anything go without testing, so let's try one last thing:

Enable Adobe Acrobat again in parallel to Fonts Ninja:

What the f..k? The supposedly red ❤ emoji is still red.

I made a huge mistake: I did not use Test Driven Development (TDD).

I just moved forward, without ever seeing a failing test. No matter what I did I always saw that the supposedly red ❤ emoticon was red. What a huge mistake to state it again.

How to go on from here?

Either the plugin has been fixed while I was writing the article, or I made an error in the investigation process. Using Occam's razor I can quickly realize it is high time to debug the investigation process.

Debugging The Investigation

What does every developer do when they encounter an error?

They look at the stack trace of course. Here is mine:

java.com.mszeles.MysterySolvingException: invalid sinner detected
    at com.mszeles.supposedly_red_heart_emoji.MysterySolver.imprisonSuspects(MysterySolver.java:69)
    at com.mszeles.supposedly_red_heart_emoji.MysterySolver.partitionSuspects(MysterySolver.java:13)
    at com.mszeles.supposedly_red_heart_emoji.MysterySolver.imprisonSuspects(MysterySolver.java:69)
    at com.mszeles.supposedly_red_heart_emoji.MysterySolver.partitionSuspects(MysterySolver.java:13)
    at com.mszeles.supposedly_red_heart_emoji.MysterySolver.imprisonSuspects(MysterySolver.java:69)
    at com.mszeles.supposedly_red_heart_emoji.MysterySolver.partitionSuspects(MysterySolver.java:13)
    at com.mszeles.supposedly_red_heart_emoji.MysterySolver.releaseSuspects(MysterySolver.java:42)
    at com.mszeles.supposedly_red_heart_emoji.MysterySolver.partitionSuspects(MysterySolver.java:13)
    at com.mszeles.supposedly_red_heart_emoji.MysterySolver.interrogate(MysterySolver.java:10)
    at java.base/java.lang.Thread.run(Thread.java:833)

As you might have also noticed on the flowchart, I am using a recursive solution here which is perferct for this task.

So let's backtrack my steps till the point where I saw the supposedly red ❤ emoji appearing in black last time. I won't describe every step here as I am pretty sure I already lost 90% of my readers, so I would like to say a big thank you to all who is still reading. 🧡😊

Solving The Mystery #2

I have tracked back to the point where I made the mistake. I did not realize that the enabling of the first 5 extensions did not result in an error so I narrowed done the problem to another 5 extensions.

I went on with the above mentioned procedure and finally I found the sinner Chrome Extension. I was shocked. It was my favourite Chrome extension without which I would not be writing in English.

You might have already guessed it is

Grammarly

Grammarly you son of a b..h. We have spent so much time together, hand-in-hand, almost every day writing. I remember the times when you continuously reminded me that I should use coma after Unfortunately, By the way, However and Although. And I will also never forget there is no such thing as Despite of only Despite and In spite of. And you even tried to correct the previously written Despite of. You bastard.

But I will also never forget that you betrayed me every time whenever I wrote a long article as you completely messed up the marking of errors. I got so angry I almost told you I hate you, but both of us know it is not true, I love you more than any of my Chrome extensions, I even love you more than my own plugins.

The Verdict

I was thinking a lot about what should I do with you Grammarly. Brake up is not an option, it never was. It looks like the only solution is to accept that the supposedly red ❤ emoji will be black forever, but I still have one more clue which would like to follow as I do believe in second chance.

Grammarly is smart. Very smart. It is possible, it sometimes automagically corrects things. So my last hope is to check its config, who knows maybe I find something useful there.

I clicked on the Grammarly Extension icon, and I immediately found what I was looking for:

Autocorrection

I turned it off, checked the result, but it is still the same. But I found another clue:

Can you spot it?

As soon as I refreshed the page the supposedly red ❤ emoticon appeared in red and then suddenly became black. I still have 2 more options that I can do, so let's quickly check the first one.

As there is no such Grammarly Chrome extension setting that could solve the problem, I open the webpage of Grammarly, maybe I can find something there.

I was wrong again. No option could help me.

Regarding the second option: If you read my story My First Month on Hashnode - A Retrospection About Blogging on Hashnode Developer Journaling Platform by Miki Szeles, then you already know I am not the type of person who gives up when facing a bigger obstacle, so as soon as I publish the article I will create a bug report for Grammarly and link my article, who knows maybe my story will touch their supposedly red ❤ and they will bring back to life the supposedly red ❤ emoji. 😊

That is the story of How I Became a Software Developer Detective To Debug The Internet.

Thanks for staying with me up till this point. I can only think of 2 reasons why you are still here. Either you enjoyed reading or because you like suffering. No matter which is the case, I kindly ask you to share my story on social media, either to cheer others up or to make them suffer. It depends on you. Thanks. ❤😊🧡🖤

UPDATE: I have submitted a bug report to Grammarly and they suggested using the desktop application which works perfectly, so finally my supposedly red ❤ emoji is really red. ❤😊

In case you enjoyed this article, I highly recommend reading The Mystery Of The Small But Cute Refrigerator On The 3rd Floor - My First 3 Months At DMG MORI HEITEC Digital Kft. too. 😊

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to and even on Instagram. 😊

But as usual, I do not leave you alone on your journey so I brought you a video that can jumpstart your Hungarian learning adventure.

Here it is:

Let's celebrate the Hungarian language together by sharing this video!😊

In case you do not want to miss my posts, just follow me here on Hashnode, on LinkedIn, on Twitter on Medium.com, on dev.to and even on Instagram. 😊