
Sign up to save your podcasts
Or


We invited Michel Zitman on to talk about Cloud Financial Management.
Some of the topics we cover this episode, in order:
My favourite quotes from Michel this episode:
Enjoy!
Hassan Habib shares the guidelines he's put into practise when it comes to improving the engineering experience. The main goal: Make engineers enjoy what they're doing :)
☑️ Increasing the joy of creating software
My favourite quotes from Hassan Habib this episode:
Enjoy!
Some of the topics we cover this episode, in order:
☑️ The power of the right environment
Enjoy!
Some of the topics we cover this episode, in order:
☑️ Solving practical problems for engineers
Enjoy!
Some of the topics we cover this episode, in order:
- The what and why of Psychological Safety
Some of the topics we cover this episode, in this order:
- Tips when just starting out
Some of the topics we cover in this episode:
- What Modular Software Development is
After seeing the title, you might wonder: "What is MLOps?". That's also what I was thinking... But no worries, Roman and Julian explain exactly what it is! On top of that, we go over how to bring your machine learning model to production, the right way, and some of the challenges you might face along the way.
This episode was recorded live in collaboration with GoDataFest: Festival of Data Technology, and Club Cloud: Global Cloud Festival!
Because it was recorded live, the intro is slightly different than what you're used to :)
Enjoy!
You might've heard of this new-ish kid on the block: Kotlin!
And like all programming languages, it's a tool to get the job done. There is no "right" pick, just pros and cons, and Kotlin is no exception. However, the pros of Kotlin certainly make it sound appealing. One of the main benefits that stood out to me from this conversation is very simple: code clarity.
If the use of Kotlin as a language creates clarity for the engineers and teams that use it, it's a very powerful tool that contributes to their productivity.
Enjoy!
Pull requests (PRs), the standard way to collaborate in codebases to ensure quality (among other things).. It turns out that they're actually slowing down software development. But how?
Dragan explains how the problem lies in the way it's structured: it's asynchronous. There's a lot of time that passes before the code is merged, and the value is delivered. Large PRs are hard to review and course correct, and small PRs can introduce lots of context switches.
However there are ways around this, to have both speed and quality. These ways lie in co-creation: Pair and Mob programming
From the publisher's feed