Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Distributed Team Content on InfoQ

  • Application Security Optimised for Engineering Productivity

    Laura Bell Main presented a webinar on 2024 trends in application security. She called out a shift from siloed DevSecOps initiatives to building an understanding of dev friction, and presenting solutions which optimise engineering productivity. Nikki Robinson also recently spoke about the importance of taking a developer experience targeted approach to security platform engineering.

  • Adopting Agile by Increasing Psychological Safety in a Software Team

    To test the agile way of thinking, a software team worked on their psychological safety with kick-off exercises, sharing coffee breaks, celebrating wins, a stand-up question, and 1-on-1 talks. This helped them to increase psychological safety in their software team.

  • QCon London: The Art, Science and Psychology of Decision-Making

    At QCon London 2024, Hannes Ricklefs, head of architecture at the BBC, gave a well-received talk on decision making. Ricklefs summarised the key reasons behind applying art, science and psychology to the discipline of decision-making, focusing on appropriate methodologies to use and the effects of biases on our ability to make good decisions in both a personal and business context.

  • The Impact of Testing in Software Teams

    Communicating quality gaps, holding space for good testing, and writing automation are some of the ways that testers contribute to software teams. According to Maaret Pyhäjärvi, we need to think about testing, not testers. Collaboration and having conversations between team members can result in valuable impact that changes the product and the experiences of our users.

  • Fostering an Experimentation Culture in Software Development

    An experimental culture is a way of thinking; it is about trying new things and learning together, solving complex software problems, and creating value together. According to Terhi Aho, an experimental culture in software organizations requires strong management support and psychological safety.

  • How Continuous Discovery Helps Software Teams to Take Product Decisions

    Continuous discovery for product development is regular research that involves the entire software product team, and that can actively inform product decisions. Equating continuous discovery to weekly conversations with one or more customers can be misleading. Combining quantitative and qualitative research methods can help software teams gather data and understand what is behind the data.

  • What Software Developers Can Do to Prevent Forgetting or Overlooking Things

    According to Ilian Iliev, software developers tend to forget to do things they do not have to think about every day, which can cause delays or impact the functionality of the product during a software project. To prevent overlooking something, he suggested starting early with automating deployment, setting up error logging, and using lists and reminders of things that were forgotten previously.

  • Google Project IDX Integrates iOS and Android Emulator, Extends Templates Library, and More

    Six months after its launch, Google has extended its experimental AI-powered, Cloud-based, shared workspace Project IDX with the introduction of integrated iOS simulator and Android emulator, new project templates, better integration with the Nix package manager, and more.

  • Why Stable Software Teams Aren't Always Best: Self-Selection Reteaming at Redgate

    There are advantages to having the same group of people stay together, especially in achieving a time-bound software development project. However, in a world where we increasingly see product or stream-aligned teams who own long-living software from creation through to delivery, operation, and ongoing improvements, then optimising for very stable teams is not the best idea, Chris Smith argues.

  • The Challenges of Building Cyber-Physical Systems

    There are several challenges in building hardware-reliant cyber-physical systems, such as hardware lead times, organisational structure, common language, system decomposition, cross-team communication, alignment, and culture. A solution to such challenges is to apply agile at the systems level, and to architect both hardware and software into modular components.

  • Why Leading without Blame Matters to Leaders and Teams

    According to Diana Larsen, a culture of blame is a waste of human potential. People cannot achieve their best and most creative work when their energy goes into avoiding shame and blame. To lead without blame requires a shift toward learning and curiosity, she argues. It begins by building or restoring a relationship of trust and trustworthiness with the people.

  • How to Become a High-Performing Software Team

    The four major elements that enable high-performing software teams are purpose, decentralized decision-making, high trust with psychological safety, and embracing uncertainty. Teams can improve their performance by experimenting with their ways of working.

  • Things We Tend to Overlook Going from Architecture to Release

    People tend to overlook things when developing a new software product or service because they don’t have to think about them on a daily basis. Companies should create an environment where everyone can express their opinion and concerns and encourage bringing up questions to explore different angles and increase understanding.

  • Handling Conflicts by Dealing with Emotions

    Emotions are at the heart of conflicts, influencing their initiation, escalation and dynamics. Effectively managing your own emotions and understanding those of others can greatly impact the outcome of a conflict. Two steps to be taken are to label emotions, and take control and determine which emotion you want to focus on.

  • Embracing Complexity and Emergence in Organisations

    Focusing on the actual emerging organisation and the work people are doing can make a difference in embracing complexity and dealing with it a bit better. Psychological safety is critical for people giving feedback without fearing retribution or negative consequences. Fred Hebert spoke about embracing complexity at QCon New York 2023.