Golang Warsaw #57 (Winter) [EN]

We are in a new location, Connectis_ (Varso Place) will host us. Looking forward to meeting you!

As usual, please register or remove yourself from the participants lists if you cannot come. We order food and drink for every meetup according to the number of attendees.

As always, looking for speakers is a challenge, so please help us finding them. Submit a talk, ask your colleague or a coworker! 3 formats: 15, 30, 45. How to submit talk? Contact @Wojciech B, @jakubdal, or @lukasz on the gophers.slack.com

TALKS

▪ 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.

▪ 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.

SPEAKERS

▪ Miłosz Smółka (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. Principal Backend Engineer at GetHarley.

▪ Robert Laszczak (SlashID) — During the day, 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.

SPONSORS

We have stickers, beer, non-alcohol refreshments, and food thanks to our sponsors Spacelift.io and GoGoApps.

Kudos to GoBridge for the support.

Thank you Connectis_ for hosting us!

SUBMIT YOUR TALK

Contact us on gopher slack, channel #poland or #poland-warsaw:

@lukasz, @jakubdal, or @Wojciech

JOIN US

The slack is the best place to get in touch with the community:

▪ Slack: #poland-warsaw and #poland on https://invite.slack.golangbridge.org/

PREVIOUS TALKS

▪ Recordings:

https://www.youtube.com/channel/UCGttUF2KmcTU2fwH8wJ5srA/videos

▪ Previous talks:

https://github.com/golangpoland/meetup_golang_warsaw