InfoQ Homepage Agile Conferences Content on InfoQ
-
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.
-
Fair Individual Compensation for Agile Teams with Team-Set Salaries
Team-set salaries can be used to set fair compensation for individuals in multiskilled, collaborative, autonomous teams. People don’t appraise themselves, only their colleagues. It gives everyone a direct say in salary settings.
-
How Measuring Defect Mass Helps to Test Critical Product Areas
Introducing a measurement called “defect mass” helped a project to find the most impacted areas by developments and decide how many tests should be run for each impacted area. Using this measurement together with other KPIs helped them focus their testing. They managed to decrease the number of customer incidents.
-
Increasing Collaboration at Ericsson: Hardware and Software Developers Learn Each Other's Language
You can integrate hardware and software development with a cross-border team setup, where it’s important that hardware and software developers speak each other’s languages. The suggestion is to focus on “us” instead of “we” and “them”, and on the technical competence that connects developers over agile or lean terminology.
-
Moldable Development: How Custom Tools Make Systems Explainable
Moldable Development is a way of programming through which we construct custom tools for every software development problem. Glamorous Toolkit is a moldable development environment that can be used to mold custom tools.
-
How AI Supports IT Operators to Resolve Issues Faster and Keep Systems Running
AIOps is all about equipping IT teams with algorithms that can help in quicker evaluation, remediation or actionable insights based on their historical data without the need to solicit feedback from users directly. AI can help IT operators to work smart, resolve issues faster and keep the systems up and running to deliver great end-user experience.
-
Implementing Remote Software Verification and Validation Using a Real Vehicle
Bosch is doing automated regression testing and user testing using a real car instead of a simulated one. Their aim is to test the software as quickly as possible, both from the test engineer's and user's perspectives. The car can be accessed remotely, and team members can work without being in the car.
-
Becoming a Better Tech Leader with Coaching
Coaching, both personal and professional, can help to understand your potential and discover ways to exercise that potential in your daily work. For Maryam Umar, coaching has proved to be highly useful in her tech work of leading testers and engineers.
-
Building Quality in for Blockchain Systems
Blockchain technology can be used to build solutions that can naturally deliver better software quality. Using blockchain we can shift to smaller systems that store everything in a contract. We have to understand our data needs and decide what is stored in the chain and what off-chain, and think about how requirements, defects and testing history can be built into the contract models.
-
Shifting to Asynchronous Communication in Software Teams
As some companies begin to go back to the office and embrace hybrid working, they are at risk of alienating those who wish to remain remote, which is looking to be a considerable number of workers in our industry. James Stanier suggests using more asynchronous means of communication and spending more time writing to each other rather than speaking in meetings.
-
The Challenges of Reading Code and How to Deal with Them
Reading code can be confusing in many ways; we are not explicitly taught how to read code, and we rarely practice code reading. Being aware of the cognitive processes that play a role can help to become better at reading code.
-
Leading a DevOps Transformation - a Collaborative Engineering Approach
When leading a DevOps transformation, transparency and visibility can help to get teams engaged in chance. Once involved, developers can act as knowledge multipliers and contribute to change initiatives. A mixture of solving frequently-occurring problems, addressing complex problems, and showing progress of the transformation can help to keep stakeholders involved.
-
How to Work Asynchronously as a Remote-First SRE
The core practices for remote work at Netlify are prioritising asynchronous communication, being intentional about our remote community building, and encouraging colleagues to protect their work-life balance. Sustainable remote work starts with sustainable working hours, which includes making yourself “almost” unreachable with clear boundaries and protocols for out of hours contact.
-
Adapting a Zero Bug Policy to Solve Bugs
Applying a zero bug policy made it easier to prioritize bugs and increased team visibility and responsiveness towards bugs. As it’s a radical change, you will need to adapt it to your context regarding decision-making and time to fix a bug.