I spent a lot of time thinking about when Java-based configuration may come in handy. Annotations are comfortable – you annotate a class, and that is all. You do not have to remember about writing an additional method in some strange configuration class.
Creating the CQ-Shop application was a great adventure. I used a bunch of new tools – event-driven architecture, Event Storming, Kafka, and many more. In this post, I summarize all the things that I learned and achieved.
From the very beginning, the CQ-Shop project was meant to be a big mix of buzzwords – microservices, event-driven, AI, and many many more. Even though the final application is a bit different than the planned one, it is still pretty impressive. In this post, I describe the architecture, development environment, and tools that I used.
CQ-Shop is an application written in event-driven architecture. In this post, I describe what the communication between microservices looks like. Before digging into that concept, I introduce the publish/subscription messaging. Once you get this idea, the whole concept of architecture should be clear. Moreover, I describe how I used events as a data for anomaly detection.
Hackathon Rzeszów is a 24-hour programming marathon. This year it took place in Aeropolis Park (Jasionka) on the 29-30th of March. It was our second start in this event. We participated in the first one in 2017. We liked the atmosphere and organization, so we decided to return and enjoy some time spent on brainstorming and coding.
Event Storming is a term that receives more attention every day. In this post, I’m describing what Event Storming is, how I tried it and how you can benefit from using this technique. Although it is not a new thing (introduced it in 2013), I haven’t met it in the corporate world.
When ten years ago someone asked me “what do you want to do when you grow up?” I answered, “I wanna be an IT guy”. Then the person asked another question: “do you know that you will have to learn and understand Math?”. I answered yes and kept this in my mind for the next ten years.
You’ve probably been using books since the first years at the school. You got used to learning from them. It doesn’t matter what you want to learn – physics, cooking, sports, photography – you always take a book. It’s the same with learning how to write code. You can find many programming books in your favorite bookstore and you probably spend tens of hours on selecting the right one.
The other day, I decided to read one paper about neural networks a day. I chose publications available at Arxiv and I added the site to my RSS reader. And just two days later I was shocked by the number of papers submitted to Arxiv every day! There were so many new ideas in the field of neural networks that it was impossible to follow them all. I gave up this habit after a week, but I realized one important thing: the majority of these papers were related to tuning or modifying already existing types of neural networks.
I’m about to start my final year at university, which will involve many activities related to obtaining my master degree. One of them is writing my master’s thesis, which is one of the biggest and the most time-consuming challenges. It’s a process that consists of writing the thesis and developing a project. I’m going to write a series of posts that will show you how the project is evolving.