Looks at the Defining Restorative paper from Ted Wachtel, founder of the International Institute for Restorative Practices (IIRP).
The explores the historical evolution of restorative justice from ancient roots to modern applications and outlines a supporting framework and how it can be used in the context of software teams.
It builds trust, fosters buy in, and reinforces that social capital.
The State of GitOps Report is the first in-depth investigation into the adoption, practices, and benefits of GitOps, drawing on data from 660 survey responses and expert interviews. Its goal is to understand what constitutes successful GitOps implementation.
The report finds that GitOps adoption is increasing, with 93% of organizations planning to continue or increase their use. It explores adoption not just by prevalence (breadth across systems) but also by the number of key practices implemented (depth or maturity). The report identifies a model of 6 core practices considered necessary for successful adoption.
The data showed a clear correlation: Applying more GitOps practices across more use cases, and over more of your productions systems leads to better results. Depth and breadth matter.
Lets look at the paper Evaluating the impact of Test-Driven Development on Software Quality Enhancement, published in I. J. Mathematical Sciences and Computing.
Find out the hurdles and outcomes of a TDD approach. Hurdles include lack of experience, time constraints, difficulty creating comprehensive tests cases, and integration issues. Benefits are things like user satisfaction, product quality, defect reduction, and code maintainability.
It’s not magic. TDD takes effort.
Source: Md. Sydur Rahman, Aditya Kumar Saha, Uma Chakraborty, Humaira Tabassum Sujana, S. M. Abdullah Shafi, “Evaluating the impact of Test-Driven Development on Software Quality Enhancement”, International Journal of Mathematical Sciences and Computing(IJMSC), Vol.10, No.3, pp. 51-76, 2024. DOI: 10.5815/ijmsc.2024.03.05
The landmark paper by Fred Brooks, No Silver Bullets, is stuffed full of smart thinking that applies today just as much as it did in the 1980s.
Find out about accidental and essential complexity and the factors in software that make it hard to share a mental model about the systems we create. Crucially, find out why the promised “silver bullets” of the 80s are not unlike those being hyped today.
No language of technique removes the essential complexity of the software we create.
Find out what transformational leadership looks like and how it benefits work performance and employee wellbeing and satisfaction.
Based on DORA’s research program, this episode looks at one of the most impactful capabilities you can bring to your software team, which is based on 5 qualities:
This paper on Psychological Affordances and their influence on DevEx improvement interventions from Catherine M. Hicks is a goldmine for understanding how to make a lasting difference to development teams.
Find out what a “psychological affordance” is, how definitions of developer experience differ, and how to create the right conditions for success.
For that code cleanup up tool to actually get used effectively, it’s not enough to just provide the tool. Leadership needs to actively signal that this work is valued, is visible, is important.
A tour of the 10 principles that guide safe, responsible, and effective use of AI in government from the Artificial Intelligence Playbook for the UK Government.
Looking back at the history of software delivery is like discovering the kind of diamond mine you see in cartoons. Lights reflect from perfectly cut gemstones that simply need to be plucked from the walls.
Well, way back in 1968, there was a NATO software engineering conference. Surely, there’s nothing to learn about software engineering from such an ancient conference? Well, maybe there is.
People chasing shiny new things, struggling to measure software delivery without driving the wrong behavior, and estimation are all topics that continue to be relevant even today.
That sounds remarkably like agile thinking doesn’t it; iterative development and adjusting based on feedback.
Dives into the new DORA report, titled Impact of Generative AI in Software Development, which looks at the outcomes of using AI for code, docs, and other software delivery tasks.
The report looks at benefits and problems at the individual and team levels, uncovering some surprises along the way like the vacuum hypothesis and the five key perspectives on AI.
Here’s another one of those head-scratching moments. Despite all these positive indicators in code and in process the researching surprisingly links AI adoption to negative impacts on overall software delivery performance.
This white paper from Octopus Deploy provides a comprehensive guide to mapping and improving deployment pipelines for achieving Continuous Delivery. It explains Continuous Delivery’s core principles and benefits, emphasizing its role in increasing deployment frequency and reducing risk.
Establish a basic deployment pipeline with stages like commit, build, acceptance, and production while highlighting the importance of automation and monitoring. Discover the cultural factors influencing DevOps’ success and find strategies for identifying and overcoming constraints to optimize the software delivery process.
Research has shown that these external approvals actually slow down deployments, increase lead times, and don’t even improve quality or reduce failure rates. In fact, they often have the opposite effect.
