InfoQ Homepage Quality Content on InfoQ
-
Investigating Near Misses to Prevent Disasters: QCon London Q&A
Investigating near misses by gathering data from the field and exploring anything that looks wrong or is a bit odd can help to prevent disasters, said Ed Holland, software development manager at Metaswitch Networks. At QCon London 2019 he gave a talk about avoiding being in the news by investigating near misses.
-
Building High-Quality Products with Distributed Teams
To ensure the quality of the products and services, Intermedia uses a common test & pre-production environment for all distributed teams. Lilia Gorbachik, product manager at Intermedia, mentioned at European Women in Tech that having a mature testing process, working with risks, and making daily decisions from a high-quality product perspective are key aspects to build high-quality products.
-
The Manual Regression Testing Manifesto
Automating regression tests isn’t always the best solution, argued Brendan Connolly at the 2018 fall Online Testing Conference. He presented the “manual regression testing manifesto” and showed how it can be used to differentiate feature testing from regression testing and to decide when to automate or not automate tests.
-
Underplayed Premises of TDD: Q&A with GeePaw Hill
TDD is more than a technique; it’s a whole style of programming, an integrated system of related behaviors and ideas. The five premises of TDD provide a ring in which we operate, they are the air that a TDD’er breathes.
-
Code Reviews in Practice
Code reviews are a great way to find bugs, get input from other team members, and share knowledge and ownership. For maximum benefit, integrate code reviews into your development process to ensure that no code reaches production without being reviewed. Reviews tend to uncover unresolved issues in the development process which you may need to address.
-
Readable Code - Why, How and When You Should Write It
Most people would say they want readable code, and may even prefer readability over functionality. But when it comes down to asking people to define readability, opinions will start to diverge. At Explore DDD 2018 , Laura Savino covered why we want readable code, what it really means to be readable, and when readability absolutely must take priority over other considerations.
-
Getting More Work Done in Fewer Working Hours
When Jason Lengstorf’s body was actively falling apart due of the way he was working, he decided to limit his computer usage and create pockets of high-focus effort. Working fewer hours prevents you from becoming overtired or unfocused. We need to treat downtime with the same level of care as we treat our uptime, using breaks to make creative connections, recharge, and to remember why we work.
-
Sustainable Software with Agile
Sustainable software enables you to deliver changes to the customer more quickly with a lower likelihood of bugs, decrease of the total cost of ownership of applications, and increase business agility. It’s possible to verify the sustainability of software using a combination of automated analysis of source code, expert review of technical artifacts, and comparison with benchmark data.
-
Software Engineering for Creativity, Collaboration, and Inventiveness
A software engineering discipline must be iterative, based on feedback, incremental, experimental, and empirical. Craftsmanship is not sufficient; engineering is an amplifier, it enhances creativity, collaboration, and inventiveness. Continuous delivery is grounded in engineering principles.
-
Oath for Programmers
Our society demands a commitment to professional behavior; we need an oath for programmers as lives and fortunes depend upon the proper construction and execution of software, argues Robert Martin. According to him, this will have to be enforced by membership in an professional association.
-
Tackling Technical Debt at Meetup
Continuous product health can be realized by regularly prioritizing the highest impact technical debt items and knocking those off systemically. You need to continuously iterate how you're tackling technical debt to drive more and more impactful results. Going for maximum impact items first and communicating the impact of paying down technical debt is what Yvette Pasqua, CTO of Meetup, recommends.
-
Adopting Agile and DevOps at Wyndham Vacation Rentals UK
Embedding agile and DevOps had a positive impact on the role of QA at Wyndham; focusing effort in the earlier lifecycle stages has led to smoother releases with fewer bugs and post-production issues. Business colleagues and customers are more involved throughout the delivery cycle, making testing a shared responsibility .
-
Managing Crowdsourced Testing
Crowdsourced testing is a unique way of involving the crowd- meaning the real users/testers- into software testing under real world conditions. It helped Swisscom to find defects very early in the development process and increase the quality of products.
-
Putting Quality Back in Agile with Lean
The agile manifesto and lean practices are very complementary; lean can be a useful addition to a very strong agile process to increase quality. Interviewing real clients or client proxies to deeply understand their pain points and visualizing the process by diving into the handovers between departments helps to uncover problems faster and fix those problems more efficiently for a lower price.
-
Refocusing e-Commerce with Lean
Auchan:Direct, the online grocery delivery service of Auchan France, decided to apply lean to develop a new e-Commerce website. Their CEO was the first customer and they used continuous and fast feedback from their clients on the new experience to improve website quality using continuous delivery.