Culture Trends 2024

The Culture & Methods Trends in 2024 cover the value of staff plus engineers, DevEx metrics, ways to make remote teams effective, challenges with diversity and software development impact on climate. This TensorBlue analysis is based on reporting and source material from InfoQ (https://www.infoq.com/articles/culture-trends-2024/).

What Happened

InfoQ Homepage Articles InfoQ Culture & Methods Trends Report - April 2024

InfoQ Culture & Methods Trends Report - April 2024

Whilst remote working presents challenges to innovation and collaboration, there are effective techniques to address them

Staff-Plus engineers bring value through far more than their technical skills

Developer Experience can be measured and there are metrics that can be used to find small improvements that make a huge difference

It is possible and practical to include climate impact as a quality attribute of a software product

The use of AI tools, such as large language models, can enhance the work of good programmers but do not replace the need for human expertise and creativity

This report summarizes how the InfoQ Culture and Methods editorial team sees the ongoing and emergent trends in the culture and methods space. We discuss evolving roles within teams, particularly the way staff plus roles can add value, the use, and misuse of DevEx metrics, how remote and asynchronous work continues to evolve, the fact that a lack of diversity is still a challenge in information technology, the slow pace of adoption of modern leadership approaches in many organizations and the need to move from climate change awareness to climate-conscious software engineering. Of course, we could not explore trends today without looking at the impact of AI and LLMs, but w

Implications for Product and Engineering Teams

For TensorBlue readers, the useful question is not just what happened, but how this changes product architecture, engineering priorities, AI delivery, observability, team workflows, or executive decision-making.

• Review whether this changes your AI roadmap, platform architecture, or engineering operating model.
• Identify the specific workflow, reliability, governance, or developer-productivity lesson that applies to your organization.
• Convert the lesson into a small production experiment with measurable quality, latency, cost, adoption, or risk metrics.
• Document source assumptions clearly so teams do not overgeneralize from incomplete public information.

TensorBlue Takeaway

The practical opportunity is to turn this signal into a concrete implementation decision: better AI systems, stronger product instrumentation, more reliable automation, and clearer technical governance. Teams that connect public technology shifts to their own delivery systems will move faster without adding unnecessary complexity.