InfoQ Homepage Culture & Methods Content on InfoQ
-
Jonathan Smart on Organizing for Outcomes - DOES 2022
Jonathan Smart shares patterns and anti-patterns to help organzations organize for business value and outcomes. He recommended focusing on “Better”, which is quality, “Value”, “Sooner”, which is time to learning and time to value, “Safer”, which is minimal viable compliance, and “Happier”, which is happier customers, colleagues, citizens, and climate.
-
Tapabrata Pal on DevOps at Fidelity: Investing in Inner Source and Engineering Excellence -DOES 2022
At the DevOps Enterprise Summit Vegas 2022, Tapabrata Pal presented the state of DevOps at Fidelity and their investment in DevOps and inner source. They were facing challenges with their tools sprawl, security, audit and compliance, and their metrics. They focused on a unified developer experience, their tools standardization, continuous compliance and contextual metrics.
-
Motivating Employees and Making Work More Fun
Progressive workplaces focus on purpose and value, having networks of teams supported by leaders with distributed decision-making. Employees get freedom and trust, and access to information through radical transparency that enables them to experiment and adapt the organization. In such workplaces, people can develop their talents and work on tasks they like to do, and have more fun.
-
State of Value Stream Management Report Shows Platform Adoption Increased 4X in a Year
The Value Stream Management Consortium has produced their 2022 report, which most notably shows a 4x increase in the number of respondents implementing a Value Stream Management platform. Organisations implementing VSM are using value streams to break down silos, and rather than setting a vision and goals up-front, many are just starting with a VSM mapping exercise treated as an experiment.
-
Performance Testing Should Focus on Trends
Performance testing starts by setting a baseline and defining the metrics to track together with the development team. Nikolay Avramov advises executing performance tests and comparing the results frequently during development to spot degrading performance as soon as possible.
-
Platform Engineering, DevOps, and Cognitive Load: a Summary of Community Discussions
Operations engineering is moving in the direction of platform engineering according to Charity Majors, CTO at Honeycomb. Majors sees platform teams tending to work higher up the stack than operations, DevOps, and SRE teams do. This shift in focus enables organizations to focus their limited development resources on their core product to drive maximum business value.
-
MIT Technology Review Insights Survey on Zero Trust in Cybersecurity
MIT Technology Review released their findings from the Zero trust closes the end-user gap in cybersecurity on Sep 19, 2022. This report focused on the approach to cybersecurity and mainly demonstrates how organizations go beyond passwords to embrace a new approach to defending against cyberattacks.
-
Reliable Continuous Testing Requires Automation
Automation makes it possible to build a reliable continuous testing process that covers the functional and non-functional requirements of the software. Preferably this automation should be done from the beginning of product development to enable quick release and delivery of software and early feedback from the users.
-
Google 2022 Accelerate State of DevOps Report Finds Strong Culture Predictive of Strong Performance
Google has released their findings from the 2022 Accelerate State of DevOps Report. This year's report focused on security with a specific emphasis on the software supply chain. The report found a broad adoption of the inspected practices with organizations that have a high-trust, low-blame culture leading the way in both security and operational practices.
-
Building an Effective Platform by Focusing on End-to-End Workflows
Platform engineering teams need to focus on building end-to-end workflows versus individual tools according to Naphat Sanguansin, CTO at Prodvana. A focus on workflows will help to abstract away the complexities of running services and allow for application engineers to focus on their product.
-
Technical Debt is Quantifiable as Financial Debt: an Impossible Thing for Developers
Technical debt can be quantified in various ways, but you cannot precisely quantify the associated financial debt. According to Kevlin Henney, we can quantify things like how many debt items we have, the estimated time to fix each debt item, a variety of metrics associated with our code, such as cyclomatic complexity, degree of duplication, number of lines of code, but not the financial debt.
-
Using Data to Predict Future Usage and Increase User Insights
By identifying usage trends, you can proactively adjust load, scaling, and routing to better handle the load on particular parts of the globe when you know it will peak there. Data about how users interact with your application can be used to design future features that better mimic these patterns and ensure that new features have a better chance of solving real user problems and getting adopted.
-
Establishing Autonomy and Responsibility with Networks of Teams
Working in outdated ways causes people to quit their work. Pim de Morree suggests structuring organizations into networks of autonomous teams and creating meaningful work through a clear purpose and direction. According to him, we can work better, be more successful, and have more fun at the same time.
-
How to Test Low Code Applications
For low code applications there are technical things you don’t have to test, like the integration with the database and the syntax of a screen. But you still have to test functionally, to check if you’re building the right thing. End-to-end testing and non-functional testing can be very important for low code applications.
-
A Distributed System is Knowable: an Impossible Thing for Developers
Failure in distributed systems is normal. Distributed systems can provide only two of the three guarantees in consistency, availability, and partition tolerance. According to Kevlin Henney, this limits how much you can know about how a distributed system will behave. He gave a keynote about Six Impossible Things at QCon London 2022 and at QCon Plus May 10-20, 2022.