BT

A Crystal Ball to Prioritise Technical Debt in Monoliths or Microservices: Adam Tornhill's Thoughts

by Daniel Bryant on  Apr 02, 2017

At QCon London, Adam Tornhill presented “A Crystal Ball to Prioritise Technical Debt”, and claimed that although the technical debt metaphor has taken the software world with storm, most organizations find it hard to prioritise and repay their technical debt. Key takeaways from the talk included methods to identify ‘hotspots’ of code complexity and churn.

Dead Code Must Be Removed

by Ben Linders on  Feb 09, 2017 4

Dead code needs to be found and removed; leaving dead code in is an obstacle to programmer understanding and action, and there's the risk that the code is awakened which can cause significant problems. Deleting dead code is not a technical problem; it is a problem of mindset and culture.

The Future of QA at Atlassian

by Rui Miguel Ferreira on  Nov 06, 2016

Mark Hrynczak, Cloud QA Manager for Atlassian, gave a talk on this year’s company summit in which he shared his vision of how a high valuable QA team should perform. High value for a QA team is defined as being, in the first place, totally aligned with the company strategic goals ,thus contributing to solve the most important problems that an organization might face at a specific moment.

Increase Learning with 10% Autonomy Time

by Ben Linders on  Oct 20, 2016

Giving teams autonomy to spend 10% of their time for learning reduces delivery time, increases quality, and increases motivation. The 10% rule gives teams full autonomy to work on things they consider important. It results in freeing up people's creativity and letting teams grow their potential.

Refactoring and Code Smells – A Journey Toward Cleaner Code

by Ben Linders on  Sep 21, 2016

Refactoring helps to move towards cleaner code that is easier to understand and maintain. It takes practice and experience to recognise code smells: symptoms of bad design which indicate deeper problems in the code. Tools can be helpful to refactor in small steps and prevent breaking the code.

Benefits of Agile Transformation at Barclays

by Ben Linders on  Sep 08, 2016

Increased throughput, reduced code complexity, less production incidents, shorter deployment cycles and higher happiness in teams; these are some of the benefits that the agile transformation at Barclays has delivered. Within the first year of the transformation, which is based on Disciplined Agile, more than 800 teams adopted agile making this one of the largest agile implementations.

Continuous Deployment at Coolblue

by Ben Linders on  Sep 01, 2016

Continuous deployment results in a higher sense of responsibility and better quality of deployments, argues Paul de Raaij, technical pathfinder at Coolblue. Coding standards prevent your code base from becoming a mess, automated inspections are great for tedious and boring checks, and manual checks are great for checking if the logic or use of code actually makes sense.

Using Models in Developing Software for Self-Driving Cars

by Ben Linders on  Jul 28, 2016

Models play an important role in developing software for autonomous systems like self-driving cars; they are used to simulate and verify behavior, document the system, and generate code. Jonathan Sprinkle explains how to model software used in autonomous systems, the benefits of modeling, using test data to validate the software that drives a car and techniques for writing reliable code.

Applying Supply Chain Management to Deliver Faster with Higher Quality

by Ben Linders on  Jun 30, 2016 1

Supply chain management can raise the bar with continuous development, argues Joshua Corman, Director of the Cyber Statecraft Initiative and co-founder of Rugged Software. Our dependence on IT and software is growing faster than our ability to secure it, and applying supply chain approaches to software development helps to address complexity which reduces risks and increases quality.

Checked C - A Safer C/C++ from Microsoft

by Abel Avram on  Jun 16, 2016

Microsoft has open sourced Checked C, a research project meant to add bounds checking to C and C++.

How to Effectively Debug Software

by Ben Linders on  Jun 09, 2016 1

InfoQ interviewed Diomidis Spinellis, author of the books Code Reading and Code Quality, about finding and fixing errors in software, principles for debugging software and how to improve the effectiveness of debugging, how to write code that requires less debugging, and what managers can do to support error prevention and handling.

What Programmers Can Do to Write Better Code

by Ben Linders on  Jun 02, 2016

To write better code, programmers have to apply design fundamentals and read existing code, says Martin Thompson, a Java Champion and high-performance-computing specialist. InfoQ interviewed him after his Engineering You talk at QCon London 2016 about the challenges that the software industry is facing and what programmers can do to deal with those challenges and become better software engineers.

Understanding Large Codebases with Software Evolution

by Ben Linders on  May 12, 2016

InfoQ interviewed Adam Tornhill, author of Your Code as a Crime Scene, about software evolution and mining social information from code and how to use this to increase the understanding of large codebases, how to create a geographical profile of code, and the benefits that can be gained from techniques like mining social information and geographical profiling.

Crafting Quality Software

by Ben Linders on  Feb 14, 2016

Tarcio Saraiva and Adam Crough talked about crafting quality software at the 1st Conference in Melbourne, Australia. InfoQ asked them to share their views on what software quality is, and to explain the business benefits and how it can be managed. InfoQ also asked them about the role for testing, how continuous integration supports quality, and advice for delivering high quality software products.

Technical Debt and Team Morale when Maintaining a Large System

by Ben Linders on  Jan 26, 2016

Thomas Bradford talked about his experience with maintaining a monolith Java based system with zero test coverage and large technical debt at the Agile Testing Days 2015. InfoQ interviewed him about the problems that they had maintaining the system and the technical debt that had been build up, why they decided to take a different approach and how they improved team morale.

BT