Software Teams
Showing 6 out of 6 results
Inclusion in the Workplace
Jill Wetzler and Evan Suttter sat down with Jørn Larsen to explore what companies could and should do to enable inclusion in the workspace, including what the best tools to accomplish that are and how important it is to have support from different groups in the company. Last but not least, they focus on a list of things that each one of us should do to start moving the needle.
Leveraging Our “Brains” in Software Development
Our brains empower us to run complicated software development programs, but can also be the thing that prevents us from achieving the best possible results due to several psychological biases. Fahran Wallace, senior consultant at OpenCredo, and Benjamin Mitchell, director of engineering at Kevel, discuss those psychological biases at work, how we can tackle them and how we can wire the brain to overcome them.
Retrospectives Antipatterns with Aino Vonge Corry
Agile retrospectives are much more than just a quick overview and assessment of what has worked and what hasn’t worked. They enable teams to discover their internal mechanisms while sharing, appreciating and learning from what has happened. There are different ways and approaches to handling retrospectives, and in her book, Retrospectives’ Anti-patterns, Aino Vonge Cory highlights them by sharing from her own experience.
How to Avoid Failure in Your Agile Retrospective
Running retrospectives can be intimidating, especially if you’re just getting started. However, their importance in shaping teams cannot be contested. To ensure that you run successful retrospectives it is essential to understand what common pitfalls or antipatterns appear while running them. Moreover, in the second episode, based on the book “Retrospectives Antipatterns,” Aino Vonge Corry and John Le Drew highlight the role of the facilitator as a team psychologist and what future retrospectives can do for you.
Software Engineering at Google
What’s the difference between programming and software engineering? Join Titus Winters, co-curator of “Software Engineering at Google”, and Matt Kulukundis while they approach the lessons learned by software engineering teams at Google in establishing the right practices for writing sustainable code in a safe environment. Discover what Google is still trying to improve on and what software decisions are difficult to undo.
Software Architecture: The Hard Parts
There are no easy decisions in software architecture. Instead, there are many hard parts--difficult problems or issues with no best practices--that force you to choose among various compromises. With this book, you'll learn how to think critically about the trade-offs involved with distributed architectures.
