InfoQ interviewed Boris Modylevsky about the importance of measuring code quality and how measurements can be used to improve quality, integrating static code analysis in continuous integration, testing coverage and test automation, and the benefits that continuous integration with integrated code analysis and test coverage can bring.
At the Agile Testing Days 2015 Jose Lima from Redgate software shared his experiences with microservices. InfoQ interviewed him about advantages and disadvantages of developing products with microservices, how applying microservices has improved the quality of products, testing microservices and the skills that testers need, and his learnings from developing and testing microservices.
Russ Olsen did the opening keynote titled "To the Moon" at the GOTO Berlin 2015 conference. InfoQ interviewed him about drawbacks of doing all the things at the same time to meet the deadline, learning from things that went wrong and from things that went right, how little things can kill you in software development, and how to focus and deal with details when doing complex work.
Uncle Bob proposes an oath to software programmers as other professions have, considering the importance of this craftsmanship.
Bryan Beecham gave a keynote about Human Refactoring at the Agile Testing Days 2015. InfoQ interviewed him about how Human Refactoring can help us to improve our lives, how it relates to refactoring code, why he considers eating healthy food to be important, how agile teams can benefit from human refactoring, and where people can find more information about self improvement and individual growth.
Karen Greaves and Sam Laing will give a keynote titled "testers are dying" at the Agile Testing Days 2015; InfoQ will cover this conference. InfoQ interviewed them about how agile impacts the role of testers, what testers can do to shorten the lead time of testing, collaboration between testers and other team members in agile teams, and the value that testers can contribute in agile teams.
In this interview Ralph Jocham talks about how to deliver value with agile teams, the most important skills that Scrum masters and product owners need to have, how you can know that the quality of the software that you are delivering is right and what teams can do if they want to deliver more value.
InnerSource is the name given to a development approach that applies open source software practices to the way organizations' develop software internally. Cedric Williams, technology leader at PayPal, explained how PayPal is experimenting with InnerSource to break down silos, grow collaboration and increase productivity.
Where many organizations use agile to develop IT products, agile principles and practices can also be applied for maintaining landscapes of commercial products. Gert Florijn and Eelco Rommes will talk about directing complex IT-landscapes in public sectors such as healthcare and local and national government organizations at the Agile and Software Architecture Symposium 2015.
Software architecture is a process; a sequence of strategic design decisions mapping specification and business goals to architecture design, and a thing; a set of views produced by the process that address different stakeholders, Michael Stal states describing how to define a software architecture.
This article contains advice written for web developers by two engineers, one recommending useful tools and techniques while the other providing suggestions on addressing some of the challenges faced writing for the browser.
Olaf Lewitz gave a keynote about Integral Quality at the Agile Testing Day Netherlands 2015. InfoQ asked Lewitz about quality attributes, what causes poor quality software, the relationship between the structure and culture of the organization and software quality and about clarifying intent and increasing trust.
For an organization to be data-driven, it's not enough to just dump mountains of data. That data needs to be accurate and meaningful. Julianna Göbölös-Szabó, data engineer at Prezi shared how they improved the quality of its log data. Their solution involved moving from unstructured to structured data with a lightweight, contract-based approach to nudge all teams in the right direction.
Hans van Wezep, software architect at Philips Healthcare, talked about model-based migration at the Bits&Chips Software Engineering conference. InfoQ did an interview with van Wezep about the challenges in maintaining legacy software, why manual refactoring is error prone, using models to refactor and migrate a codebase, and the benefits of using models when maintaining legacy software.
Computer-checked models can be used to prove that core communications and state management in a software program are 100% logically correct. Such models can also be used to generate 100% correct source code. The usage of formal methods can reduce costs and time to market and help to deliver highly reliable software products.