GoWroc #53
17:45 Networking
Let's grab a beer and catch up beer!
18:00 Talks
Miłosz Smółka: Killing the legacy and other CQRS stories.
Do you know the feeling when your project gets stuck, and you can’t move forward? You see a few ways out, but all seem equally bad. You start wondering if the project is doomed or if you just miss some special knowledge. I felt this the most while trying to move out of legacy systems, but it’s common in many projects.
Over time, I learned that changing your mental model may reveal a solution you didn’t see before. Looking back at some of my projects, I realized one of the patterns that helped me think differently was CQRS.It doesn’t matter if you’ve used CQRS before, as I don’t plan to bore you with abstract definitions. A lot has been said about the theory of CQRS. Instead, I want to show how I used it in practice. I will share three real stories from different companies and projects where I managed to move forward and better grasp CQRS. One of them was the most challenging: killing the legacy codebase.
19:00 it's pizza time! And another chance to chat with your fellow gopher!
Robert Laszczak: Gopher Toolbox: Techniques and Tools Every Senior Go Developer Should Understand
A friend recommended you a technique that seems to be the perfect solution to the problem you’re struggling with. You convinced the rest of the team to adopt this idea, and after a heroic effort, you introduced the new technique into the project. However, six months later, you conclude that the original problem still exists. Moreover, now it’s not the only problem. One day, you notice someone well-known writes: “This technique doesn’t work.” Phew, so it’s not my fault. Sound familiar?
From my experience, most techniques and tools are not useless. The problem often lies in applying them to solve the wrong problem or in insufficient understanding of the given technique. Can you say that a pneumatic hammer is a bad tool just because you tried to hammer a nail with it and ended up punching a hole through the wall?
In my presentation, I will discuss the most important tools every aspiring senior Golang Developer should know. Moreover, I will share my experiences regarding situations when these tools proved to be effective and when they were the wrong choice.
20:00 Networking
Hello Gophers!
We are excited to meet you all again!
We will be meeting again in the lovely Wędrówki Pub. This time we will have two great talks with very interesting and modern topics.
And one more thing, there will be free beers and pizza! This is thanks to our kind sponsor BlueLabs!
Speakers
Robert - I am a Principal Software Engineer in SlashID, where I build IDP solutions at a global scale. During the night, I’m blogging at threedots.tech. Author of “Go With The Domain” and Watermill.io.
My programming journey spans 16 years, during which I’ve navigated diverse domains, including infrastructure, global financial platforms, and security. A couple of years ago, I finally found a language I loved: Go.
Miłosz - Principal Backend Engineer at GetHarley. I write about Go, modern business software, and related topics at https://threedots.tech. I enjoy sharing what I learned while working at startups and building products in different fields
Go Developers Network
We are a part of GDN, which is a collection of Go user groups working together with a shared mission to empower developer communities with the knowledge, experience, and wisdom to build the next generation of software in Go.
About Sponsor
BlueLabs
BlueLabs is a dynamic and fast-growing startup in the sports betting industry. We are committed to delivering innovative and cutting-edge solutions to our customers, providing an unparalleled betting experience.As we continue to expand to new markets and evolve our product, we are looking for a highly skilled and passionate software engineers to join our team. Check out our careers page!
.png)
