Beyond Coding

I invited Michael Feathers on to discuss what makes a great and effective team in tech. We cover lots of the social systems you’ll see, as well as the impact that remote working has had on those. More of the topics we cover this episode, in order 💬 ☑️ Remote working and team autonomy ☑️ Treating software like biology ☑️ Finding common grounds of communication ☑️ Genuine curiosity ☑️ Team goals vs. Individual goals More on Michael Feathers: https://michaelfeathers.silvrback.com https://twitter.com/mfeathers https://www.linkedin.com/in/michaelfeathers

I invited Hannes de Jager, Kevin van den broek and Goos van den Bekerom on to discuss the ins and outs when it comes to the Go programming language. All you need to know with regards to why and how Go would be embraced within a team, or within an organisation. Sounds interesting? Check it out! Some of the topics we cover this episode, in order 👇 ☑️ The pros and cons of Go ☑️ How does Go get adopted within organisations? ☑️ The way Generics was introduced in Go ☑️ Hire good engineers instead of “language” engineers More on Hannes: https://www.linkedin.com/in/hannesdejager https://github.com/hannesdejager More on Kevin: https://kevinvandenbroek.nl https://www.linkedin.com/in/kevin-van-den-broek https://github.com/Kevintjeb More on Goos: https://www.linkedin.com/in/goosvandenbekerom https://github.com/GoosvandenBekerom

Diana Montalion shares how we think of, and design, sources of information to accommodate for what we want as users, depending on the context we’re in. It requires a way of thinking we’re not used to: systems thinking, or non-linear thinking. But doing so and adapting the software we create, can open up opportunities that weren’t there before. Some of the topics we cover this episode, in order 👇 ☑️ Systems thinking vs. Linear thinking ☑️ Designing for sources of information ☑️ Do you know why your tasks matter? ☑️ Changing the skills we value when hiring ☑️ Learning from each other, and growing as a team More on Diana:   https://www.montalion.com https://twitter.com/dianamontalion https://www.linkedin.com/in/dianamontalion  #systemsthinking #software #podcast

Whether you know it or not, we’re all benefitting from open source software. The innovation and collaboration that has come from it is incredible. But it’s not without flaws… Very Interesting ones actually, so I invited Paulo Lopes and Maarten Mulders on to discuss the good, bad, and ugly when it comes to open source. Some of the topics we cover this episode, in order 👇 ☑️ Disputes and social problems that occur in open source projects ☑️ Contributing to open source, and how to make it easier ☑️ What would make open source better? ☑️ The not invented here syndrome in open source projects Enjoy! Check out Paulo Lopes: https://www.linkedin.com/in/pmlopes https://twitter.com/pml0p35 Check out Maarten Mulders: https://www.linkedin.com/in/mthmulders https://twitter.com/mthmulders https://maarten.mulders.it #podcast #tech #opensource

Maarten shares how the city of Amsterdam is creating and leveraging AI solutions to help society and improve the city. It was surprising to hear how there are lots of experiments being done involving more state of the art technologies when it comes to AI. And I really enjoyed learning what projects are being worked on right now. What projects are those? Listen in to find out! Some of the topics we cover this episode, in order 👇 ☑️ Using AI to make the city better, or to prevent it from becoming worse ☑️ The Algorithm Register ☑️ Amsterdam for all: increasing accessibility in the city ☑️ Current ways of working and the challenge of moving to the cloud ☑️ Using established methods, but also experimenting with state of the art tech More on Maarten: https://www.linkedin.com/in/maartensukel https://twitter.com/maartensukel Check out Amsterdam Intelligence: https://www.amsterdamintelligence.com

“Doing the right thing is not equal to doing things right”. This really stuck with me after discussing how to create effective data science solutions with Deena Gergis. It would be easy to create a solution ‘just’ from the technical side, but more often than not, your solution might not get used at all that way. Partnering with your stakeholders, and building this solution together is the right way to do it. And it starts by having an equal level conversation with each other. Some of the topics we cover this episode, in order 👇 ☑️ The differences between data science academically, and data science professionally ☑️ Doing things right vs doing the right things ☑️ Buy-in from your most important stakeholders and partners ☑️ The right balance of focus and flexibility in creating data science solutions ☑️ Hiring for emotional intelligence and leadership skills, as well as technical expertise More on Deena: https://linkedin.com/in/deena-gergis https://www.youtube.com/c/deenagergis

Cloud technology has made things a lot easier, but it has also introduced new challenges for developers. Together with friend and returning guest Léon Rodenburg we discuss what cloud native software development entails, and share how to be effective. Some of the topics we cover this episode, in order 👇 ☑️ What is cloud native software development? ☑️ Team responsibility in handling the cloud ☑️ The problem with cloud courses and trainings ☑️ Iterating on your cloud infrastructure ☑️ Start by understanding your current project in terms of cloud infrastructure More on Léon: https://linkedin.com/in/leon-rodenburg https://twitter.com/lrodenburg

Felienne shares her journey on how she created Hedy, the programming language that helps teach kids how to program. Creating your own programming language is a big accomplishment, but a language on its own can only go so far. With actual usage, user feedback, and continuous improvements, Hedy can truly improve the way teachers teach, and kids learn how to program. And it's definitely on its way to do so. Hedy is available in 18 different languages, and is being used globally. Truly remarkable!   Some of the topics we cover this episode, in order 👇   ☑️ Why Felienne created the Hedy programming language ☑️ Maintaining an open source programming language ☑️ Solving the initial problem, but creating new problems along the way ☑️ Dictatorship vs. Bureaucracy in adding features to programming languages ☑️ Closely listening to user feedback More on Hedy: https://www.hedycode.com https://github.com/Felienne/hedy  More on Felienne: https://www.felienne.com https://twitter.com/felienne https://www.linkedin.com/in/felienne  #tech #podcast #programming

There have been lots of worthwhile Agile implementations within organisations. However, there’s also a dark side to Agile... Laurens and I discuss how not every organisation actually “understands” it, which leads to forced implementations. Eventually, this lack of understanding can create lots of frustration towards something that’s meant to be helpful. Where does it go wrong, and how we you fix that? Some of the topics we cover this episode, in order 👇 ☑️ Focussing on the single most important thing ☑️ Scrum implementations gone wrong / The dark side of Agile ☑️ Truly acting as a team ☑️ What makes a great leader ☑️ Managers are humans Laurens is someone I truly could listen to for hours, enjoy! More on Laurens: https://www.linkedin.com/in/laurensbonnema https://twitter.com/laurensbonnema

Want to live and work next to the beach, but stay in the tech space? No problem! Working remote allows you to have the personal life that you want whilst your work life fit around that. That is one of the main drivers why Alvaro started his company in a fully remote setting. He shares how he’s been operating fully remote, some of the pitfalls he’s experienced, and much more! Some of the topics we cover this episode, in order 👇 ☑️ Managing and trusting remote teams ☑️ Clear expectations and long-term partners ☑️ Engineers want to work remote, so organisations offer it ☑️ The issues with working remote ☑️ Personal values, team values, and company values More on Alvaro: https://www.linkedin.com/in/alvarormoya https://lidr.co