InfoQ Homepage Agile Conferences Content on InfoQ
-
Transitioning to Modern Testing: How Testers Can Stop Being the Training Wheels for Teams
Traditional testing, where testers act as safety nets and testing is separated from implementation, can have a detrimental impact on quality. Testers can instead act as coaches, collaborate in teams, and foster change, to stop becoming the training wheels for teams. Culture is key, particularly in that the environment provides psychological safety.
-
Words Matter in Documentation to Build Better User Experience
The language that we use in our products or documentation can make people feel unwelcome or hurt people. We can choose words that are precise, not dependent on complex metaphors, and convey messages without negative connotations.
-
How Getting Feedback from Angry Users Helps to Develop Better Products
Every time you change something in your product, angry users can show up. These users are engaged and they care about your product. Listening to them can help you find golden nuggets of user insight to improve your product.
-
Trust-Driven Development: Building Cognitive and Emotional Pillars
Trust-driven development uses authenticity to build a safe environment for people to operate. To build trust we need to focus on two main pillars of trust – cognitive and emotional. We need to be brave, have courage, and give people access to our authentic selves.
-
Learnings from Discussing Developer Enablement at QCon London
Developer enablement can increase the potential of individuals in small and larger companies. Where individuals can have their own solutions, there will be things that are mandatory for all. Metrics can help to see what is being used or not. Be careful about supporting developer enablement for legacy systems; if it’s outdated and needs to be replaced then it might be better to not invest in it.
-
Every Question Has an Answer: an Impossible Thing for Developers
We tend to assume that every question has an answer, which for instance isn’t true when we want to find out what the current time is. Developers should increase awareness of unexpected failure modes, advertise the possibility of failure, and use time-outs to recover from waiting for an answer that will never come.
-
How Developer Enablement Brings Benefits to Software Organizations
Developer enablement is about tools and approaches that can greatly increase the potential we can have as individuals. It can have an impact on productivity and happiness, on profits and retention. Developer tools make it easier for engineers to deploy products, enabling them to focus on building a product.
-
How to Prepare an Agile Business Game
To make playing games "interesting" from the business owner's perspective, we need to ensure that they are aligned with the business needs. There are four steps in preparing a game: exploring the context, knowing your target group, defining the focus, and deciding how to facilitate it.
-
How Software Affects Climate Change, and What Software Engineers Can Do about It
There are huge amounts of software running everywhere on the planet - and this software consumes energy when it is running. Unfortunately most of the energy world-wide is still being produced by burning fossil fuels. Software engineers can improve the software so that it uses less energy to do its job, then less energy needs to be produced by burning fossil fuels, which is better for the climate.
-
Improving Software Quality with Gamification
Bingo Bongo sessions for bug hunting and playing risk storming games can improve quality. Gamification supports learning, can make everyday work interesting, and strengthen team spirit. Playing games should be part of the daily work at the office and seen as an effective work time. In gamification, a real value is created by the creative process.
-
Infinite Representations: an Impossible Thing for Developers
Developers can face impossible things in their daily work. It’s impossible to directly represent infinity or to hold infinite precision on a discrete physical computer. Storage and representations are bounded. Ignoring or being unaware of this impossibility can lead to bugs or systems behaving differently than expected. Kevlin Henney gave the keynote Six Impossible Things at QCon London 2022.
-
Creating Tight Cohesive Tech Teams for Women to Thrive
Women in tech need a dynamic, valuing team, stimulating work, push and support, local role models, nonjudgmental flexibility, and personal power. Tight cohesive teams can provide high-quality interactions, making people feel valued.
-
Measuring the Environmental Impact of Software and Cloud Services
Software has an influence on the limitation of the service life or the increased energy consumption. It’s possible to measure the environmental impacts that are caused by cloud services. The design of the software architecture determines how much hardware and electrical power is required. Software can be economical or wasteful with hardware resources.
-
Making On-Call Less Painful for Developers by Using High-Quality Alerts
On-call is an increasing reality for developers. Improving alerts to reduce noise, automation, and removing warnings can help to make on-call work more humane. A driving force behind automation is Infrastructure as Code. Over time you can abstract that code so that it fits other use cases, which helps propagate best practices.
-
How Security by Design Helped to Manage Risks in a Cloud Migration
When a company migrated to the cloud, security issues arose due to difficulties in getting stakeholders on board and involving security from the start. Embedding security assessments as part of the continuous cloud DevOps process and adopting an agile strategy for security risk management throughout the lifecycle of the project helped to increase the governance of security during the migration.