---
title: "Discussion on \"Why You Always Have To Close Your Article With A Call To Action AKA A Brief Introduction To Hashnode Widgets By Miki Szeles\" | Hashnode"
description: "Discussion on \"Why You Always Have To Close Your Article With A Call To Action AKA A Brief Introduction To Hashnode Widgets By Miki Szeles\". Hello dear Reader!\nLet me outline a short story for you.\nMumbling on the street with a bucket on your head\nYou get up, early in the morning. To boot your day, you drink a coffeeand maybe also smoke a cigarette (at least I do that).\nA quick shower, dr..."
url: "https://hashnode.com/posts/why-you-always-have-to-close-your-article-with-a-call-to-action-aka-a-brief-introduction-to-hashnode-widgets-by-miki-szeles/6234b9edbef4c71aa6f0ea06"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why You Always Have To Close Your Article With A Call To Action AKA A Brief Introduction To Hashnode Widgets By Miki Szeles](https://mszeles.com/why-you-always-have-to-close-your-article-with-a-call-to-action-aka-a-brief-introduction-to-hashnode-widgets-by-miki-szeles?utm_source=hashnode&utm_medium=feed)

Hello dear Reader! 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, dr...

Mar 18, 2022 · 42 min read · mszeles.com  
Read the article

-   [#hashnode](https://hashnode.com/tag/hashnode)
-   [#2articles1week](https://hashnode.com/tag/2articles1week)
-   [#writing](https://hashnode.com/tag/writing)
-   [#blogging](https://hashnode.com/tag/blogging)
-   [#analytics](https://hashnode.com/tag/analytics)

## Written by

[Miki Szeles](https://hashnode.com/@mszeles)

@mszeles · Hungary

  
[View profile](https://hashnode.com/@mszeles)

Everything related to test automation

I am an enthusiastic developer since my childhood. I have started with Plus 4 and C 16 machines programming in Basic. I still remember when we were jumping on the bed with my brother, and accidentally saw the Commodore 64 computer on the top of the wardrobe, which was planned to be a Christmas gift for us. I don't have to tell you that we couldn't wait till then. :) I will never forget this memory. Of course in the beginning we only played on the computer, but later I became interested in how can I make my own programs. I have to tell when I first faced the binary number system I did not understand it, but I was still able to draw some sprites on the screen. :) I continued learning software development during grammar school. I got my Masters degree at the Budapest University of Economics and Technology where I learnt many languages and also learnt a lot about general software development theory and practice. I have started my professional career as a C++/C# developer, but I switched to Java after a few years. I've visited many meetups and Code Retreats during this time and I've learnt and introduced Agile methodologies in our company. During the years I lead the development team in close cooperation with the product management and testing department. In 2020 I felt I need something new and I turned towards test automation both API and UI. I did not regret my decision. Since then I tried many frameworks like RestArrured, Selenium, Protractor, Appium, Selenide and Karate. At the moment I am working as a Senior Software Developer in Test using Selenium and Selenide for UI testing and Karate for API testing. I believe knowledge sharing is very important, so apart from helping my colleagues work I started my technical blog recently: https://mszeles.com Sharing your knowledge provides many ways for your own development. Whenever I write an article many questions come into my mind which might be interesting for the readers, so I try to answer all of them in my posts. Doing this I learn a lot about the subject. In additionally sharing your knowledge gives a good opportunity for feedback based on which you can further improve.

## Responses 2

Markdown supported · ⌘↵ to post

[Mohit Yadav](https://hashnode.com/@just-moh-it)

[Mar 19, 2022](https://hashnode.com/posts/why-you-always-have-to-close-your-article-with-a-call-to-action-aka-a-brief-introduction-to-hashnode-widgets-by-miki-szeles/6234b9edbef4c71aa6f0ea06/comment/62354b6bbef4c71aa6f0f536)

Amazing article Miki! I'm so flattered you're able to get so much together in just one single blog post. Even while commenting, you seem to write a lot, while I still struggle to write a comment within a minute 😄

Seems like you're the "Just some guy with a moustache" of Hashnode lol. Anyway, awesome research and summary. I hope the algorithm gets the attention that it deserves... 👋

[Miki Szeles](https://hashnode.com/@mszeles)

[Mar 19, 2022](https://hashnode.com/posts/why-you-always-have-to-close-your-article-with-a-call-to-action-aka-a-brief-introduction-to-hashnode-widgets-by-miki-szeles/6234b9edbef4c71aa6f0ea06/comment/62354b6bbef4c71aa6f0f536#reply-623555826647c71acb642f15)

Thank you very much for your kind words Mohit.

I am so happy you enjoyed my article. 😊

Wow. Thanks for teaching me something new, I have never heard the term "Just some guy with a moustache" before. But is is very funny. 🤣🤣🤣

Thanks again for presenting me with your precisous time, you not just read my article, bug you also took the time to write a comment.

I really appreciate that. 🧡😊

[Jorge Romero](https://hashnode.com/@JorgeRL)

[Mar 18, 2022](https://hashnode.com/posts/why-you-always-have-to-close-your-article-with-a-call-to-action-aka-a-brief-introduction-to-hashnode-widgets-by-miki-szeles/6234b9edbef4c71aa6f0ea06/comment/6234eb1b6647c71acb642a2f)

Ann Handley, in the book "Everybody writes" introduces this concept of the "Ugly first draft". That I think matches closely what you propose here!

I will have to learn some of the data-analysis-based methods you use for getting insights on performance. As I currently don't do anything about that.

I really appreciate the insight of using data analysis. Thanks [Miki Szeles](https://hashnode.com/@mszeles)

May I offer some feedback? I find it way easier to read shorter paragraphs, and I have seen that improvement in your writing! However there are three things that make it a little hard for me to read (because I have ADHD).

1.  Having single-line paragraphs one after the other.
2.  Using bold letters too often.
3.  I can't follow who is talking in the conversation sections.

I think a good example of using bold letters effectively is when you retold the "mumbling on the street" story. As you only highlight the new changes, where you want the attention of the reader to go.

The single line paragraphs "blend" (I'm thinking that I may be slightly dyslexic) for me. So I get easily distracted before finishing the idea. The same for the conversations. Both long paragraphs and consecutive single-line paragraphs end up being very hard to read for me.

I can only say that those are issues for me. Again, I have ADHD and have a very hard time reading anything in the first place XD.

Finally, I am really loving your new approach to cover illustrations!

[Miki Szeles](https://hashnode.com/@mszeles)

[Mar 18, 2022](https://hashnode.com/posts/why-you-always-have-to-close-your-article-with-a-call-to-action-aka-a-brief-introduction-to-hashnode-widgets-by-miki-szeles/6234b9edbef4c71aa6f0ea06/comment/6234eb1b6647c71acb642a2f#reply-6234f692bef4c71aa6f0f199)

Thank you very much for your detailed feedback [Jorge Romero](https://hashnode.com/@JorgeRL). I appreciate it. 😊

I also read Ann Hadley's book. I am mentioning the "Ugly first draft" in one of my upcoming articles.

Ann's ugly first draft is quite different from this concept. She is only talking about writing and iterating inside one article, as far as I know.

The RWRR method is about iterating articles.

Thanks for sharing how you perceive my writing with ADHD. Up till now, I did not consider this factor.

Let me tell you how and why my writing is here at the moment.

In the beginning, I had very long paragraphs containing many thoughts. So I decided to highlight the critical information in it.

Thanks to the RWRR iterations during the weeks, this improved a lot.

I started to write shorter paragraphs containing only one thought.

Then I started to use Twitter, which highly affected my writing style as you have to condense the essence of your writing into 160 characters.

I used many filler words in the past, which I got rid of almost completely.

Now my writing is much denser, and as I use only a few filler words, the information density of my article becomes much higher.

I see two potential ways to further improve from here:

1.  Neglecting one part of my message and only highlighting the other minor part.
2.  Not highlighting anything at all.

I do not know which direction will I choose, but I may try both ways.

Regarding the conversation: Yeah, I am sure it is not easy to follow, especially as I am talking to myself, but I gave a clutch by using the - sign. Each new - character means the other me started to speak.

I also considered the option to add the names before each line, but in the end, I decided this solution would be adequate. But it looks like I was wrong, as at least it caused a headache to you. I am pretty curious what the others will say about it.

Thanks for taking the time not just to read it but also to give such a long and valuable feedback [Jorge Romero](https://hashnode.com/@JorgeRL). 😊👍
