Welcome to my first article

The story begins with the idea to write a website about myself just as a portfolio landing page. After playing with React from scratch, implementing and finishing it after 6 days, I saw good results for such a short period (compared with Data Engineering routines). So I decided to continue my frontend development journey, and my next idea was to implement a website programming blog.

Background

When I just started my career, I worked as a backend developer. I implemented different backend services and, of course, used databases as well. So, while thinking about the future architecture of my website, I had a lot of ideas and design decisions about how the future frontend would work with the backend via Axios, and what databases I should use for my future programming blog website.

This would probably take several months, and the result would be a website programming blog that would be deployed on the internet among a million other website programming blogs...

Initially, I wanted to implement website sequentially aka using the waterfall approach:

1. Create a database schema
2. Connect to the backend
3. Write a frontend

However, if I had selected this path, I would probably lose motivation after some time and won't finish it. I decided to get the first web blog website up and running—not perfect, but as soon as possible. It's not even 2 weeks since I started developing, and this site is already published, and you can already read it! 🎉

Goals and Motivation

Another reason that came with my enthusiasm simultaneously is that I used to use the Microsoft OneNote application to write notes when I wanted to learn a new stack, go through all pages, or prepare for a technical interview. Via the website, I can:

• New knowledge: Revising old topics and exploring new ones to share with the audience helps me improve my own understanding.
• Structuring: Organise knowledge in a clear markdown format that ensures everything is presented in an orderly way.
• Clarity: Reduce the chance of making mistakes or skipping over confusing topics by maintaining a well-structured articles.
• Easy access: Share easily with my friends and anyone who wants to read information about some specific topic.
• High standards: Making it public forces me to maintain a high level of quality in providing and writing information.
• English skills: Improve my knowledge and express myself better in English!
• Full control: Implementing my website gives me full control over how I store my information.

So these are my motivations to continue writing about programming. In the next chapter, I will write more about the process of how to create a website on a pure frontend stack, learning along the way, and realizing and accepting annoying ideas and tasks that are really important.