Beyond Coding

We invited Michel Zitman on to talk about Cloud Financial Management. Shorthand: FinOps.  Some of the topics we cover this episode, in order: ☑️ Cloud financial management - FinOps explained ☑️ How Cloud Cost inefficiency occurs in the first place ☑️ FinOps as a skill ☑️ Where most Cloud Costs occur, and how to reduce those costs ☑️ Big chunks of optimizations already, and much more when looking ahead My favourite quotes from Michel this episode: - "Awareness increases accountability, which in turn increases awareness." - "Turn off your cloud resources when you don't use them, just like how you would turn off the lights when you leave home." 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 :) Some of the topics we cover this episode, in order: ☑️ Increasing the joy of creating software ☑️ The 3 most important aspects to make engineers happy ☑️ Developers communicating with end users ☑️ Introducing standardisation ☑️ Speaking a language people understand My favourite quotes from Hassan Habib this episode: - "If your software engineers are hungry, your code is gonna be hungry, it's gonna be angry" - "If you're talking ideas and possibilities, you have to bring the engineers to the table. You have to have them see the customers and make the connection" Enjoy!

Some of the topics we cover this episode, in order: ☑️ The power of the right environment ☑️ Evolving software vs rebuilding it, and the not invented here syndrome ☑️ Trust is very complex ☑️ What does 100% unit test coverage mean? ☑️ The sweet spot of quality and speed My favourite quotes from Albert Brand this episode: - "Are you really going fast when it slows you down later?" - "Isn't speed just another quality?" Enjoy!

Some of the topics we cover this episode, in order: ☑️ Solving practical problems for engineers ☑️ Code reviews are becoming a big problem in our industry ☑️ Leveraging tools to better understand code ☑️ A startup with developers as target audience ☑️ Remote company culture Enjoy!

Some of the topics we cover this episode, in order: - The what and why of Psychological Safety - High performing teams - Awareness of how you act and communicate - Imposter Syndrome - The value of personal feedback

Some of the topics we cover this episode, in this order: - Tips when just starting out - Going outside of your comfort zone - The Full Stack term - The challenges of forming a great team - Stability versus Experimentation - The benefits of teaching

Some of the topics we cover in this episode:  - What Modular Software Development is - When to split your application, and how to split it - The role of Software Architect in a cross-functional team - When and how organisations adapt new tech - Hire for mindset, train for skill, and the joy of working in diverse groups

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