Michał Dubel
Programming for a living since 2011, and for pure enjoyment since 1997. I have dabbled in various technologies—primarily working in the JVM world (mostly the tech stack related to Java - basically if it's Java, I've probably seen it, debugged it, and perhaps even dreamt about it once or twice), exploring the lightning-fast-changing world of frontend, and now bonding with Gopher and discovering the highs and lows of the Go world.
Besides my love for building tools and products, I find immense joy in creating effective and healthy engineering teams. Hence, you'll see in my CV periods where I was not only focused on tech leadership but also on team leadership (not to mention ensuring business success in the role of a delivery manager). Building great products is fun, but building great teams is an art form I relish.
I enthusiastically share my knowledge (often at the expense of a good night's sleep ;)), frequently delivering lectures at technical universities and conferences. I’ve become quite the night owl, perfecting the art of turning caffeine into code and coherent presentations.
P.S. I've made a personal commitment to complete reading 'Learn You a Haskell for Great Good' one day.
P.P.S You will probably find enough ways to contact me at dubel.dev - see ya!
From Java to Go(Lang)
Some might call it a midlife crisis, others an unrelenting thirst for adventure—whatever brought me to leave Java behind and embark on a journey with Golang, I invite you to join me on this exploration through the lens of a seasoned developer from the JVM world.
I'll discuss why it's worth learning new programming languages, how to approach Golang (especially if you come from a Java background), and what’s good, bad, and downright ugly about it.
Is Golang a safe haven where every Java developer can find peace and harmony? Is it worth becoming a polyglot? Is Java dying? Will Golang take over the world? We'll answer these and other questions during this talk. (Heads-up for the audience: expect a heavy dose of Golang code—consider yourselves warned!)
Programming for a living since 2011, and for pure enjoyment since 1997. I have dabbled in various technologies—primarily working in the JVM world (mostly the tech stack related to Java - basically if it's Java, I've probably seen it, debugged it, and perhaps even dreamt about it once or twice), exploring the lightning-fast-changing world of frontend, and now bonding with Gopher and discovering the highs and lows of the Go world.
Besides my love for building tools and products, I find immense joy in creating effective and healthy engineering teams. Hence, you'll see in my CV periods where I was not only focused on tech leadership but also on team leadership (not to mention ensuring business success in the role of a delivery manager). Building great products is fun, but building great teams is an art form I relish.
I enthusiastically share my knowledge (often at the expense of a good night's sleep ;)), frequently delivering lectures at technical universities and conferences. I’ve become quite the night owl, perfecting the art of turning caffeine into code and coherent presentations.
P.S. I've made a personal commitment to complete reading 'Learn You a Haskell for Great Good' one day.
P.P.S You will probably find enough ways to contact me at dubel.dev - see ya!
From Java to Go(Lang)
Some might call it a midlife crisis, others an unrelenting thirst for adventure—whatever brought me to leave Java behind and embark on a journey with Golang, I invite you to join me on this exploration through the lens of a seasoned developer from the JVM world.
I'll discuss why it's worth learning new programming languages, how to approach Golang (especially if you come from a Java background), and what’s good, bad, and downright ugly about it.
Is Golang a safe haven where every Java developer can find peace and harmony? Is it worth becoming a polyglot? Is Java dying? Will Golang take over the world? We'll answer these and other questions during this talk. (Heads-up for the audience: expect a heavy dose of Golang code—consider yourselves warned!)