Hello world!

Welcome to the first post on my blog!

Here I want to present the following key points:


I have approached writing a blog several times before. The reasons why I let go were various and not once did I manage to make it to the final creation of the site. Let me describe and address the blockers that came along the way.

1. Lack of technical know-how
This goes back to my student days. The plan was to describe interesting academic projects, but at the time I was completely unsure how to approach it. Moreover: I had the opportunity to ask experienced colleagues how to do it, but I didn’t. All my research was based on creating a colossus, probably on a platform like WordPress, but each time something didn’t suit me, and I let go. Even when I had some basis that could already be published I lacked knowledge about hosting such constructs.

After some time, I visited the Java User Group in Görlitz, where static site generator solutions were presented. It gave me a new insight into how easy it is to create such a blog.

2. Lack of ideas for posts
In retrospect, I think it was more fear. At one time I had the impression that everything do is nothing new and will always be so. Well, nothing could be further from the truth. Even creating in a technology that is heavily explored, you can create a connection with another technology, and it will create business value. This value can also be beneficial to the community, so it’s worth sharing. This is definitely one of the most important points why I decided to write about my experiences.

3. Choice of the domain name
This may sound quite ridiculous, but by not knowing what domain name to choose I was slacking off with content creation. My conviction was that a particular domain name would influence the posts I would publish.It was no different in this case either. By a stroke of luck, I learned the technology that allowed me to publish this blog without first deciding on a particular domain. I have decided that I will initially use the custom name given by this service and will choose a particular domain name at a later time. This will probably happen when I have valuable content to share here.

4. Absence of why
Until now, I didn’t know why I wanted to start a blog. I told myself that if others were doing it then I should too.

Now I know what my goals are:

5. Language
It may sound trivial, but I couldn’t decide what language to choose for my posts, and as a result I held back on creating a blog. The decision was made for English. This will ensure that the texts will be understood by a larger group of people. Previously, I was afraid of the level of my skills in this language, but the moment I started working in a project where English was the main language I gained courage, because everyday communication did not cause me any problem. In addition, online translators help me create this content.

You may ask: What other languages could I write in?
My native language is Polish and my second language, in which I finished high school and college, is German.

Technical implementation

In this section I want to briefly describe what technology I chose to create this blog. This will be a general overview, as I plan to describe the process in detail in another post.

Since I do cloud development on the AWS cloud on a daily basis, I naturally decided that this would be the platform on which my blog would be deployed.
The question was which static site generator I would choose. I tested the following ones: Gatsby, Jekyll, Nuxt and Hugo. The choice fell on Hugo, because it was the most pleasant and fastest for me to work with. I liked the system of adding theme as git submodule. I decided on a minimalist theme with simple configuration, which completely meets my requirements. In case it becomes insufficient it is very easy to replace it.

The architecture at this point is very poor, as I was keen to start creating content as soon as possible. As time goes by, I plan to expand it. Let’s take a look at it:

Blog architecture



I build serverless solutions on a daily basis, and I did so in this case as well. AWS Amplify allows me to simply host my blog and in addition, when I make changes and add them to the repository it triggers a build and automatic content update. The only thing I have to “worry” about are interesting posts. The infrastructure is written in TypeScript using the CDK framework and is currently deployed manually from my local machine, as it is very simple. I plan to develop it in the future, also it will probably be plugged into AWS CodePipeline to also build automatically when changes are added to the repository.

The content itself is written in Markdown.

Future content expectations

What can you expect from future posts on this blog? My predictions are:

Thanks for reading and see You next time!