BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Articles

  • Maybe Agile Is the Problem

    “Agile” now means anything, everything, and nothing. Many organizations are Agile fatigued, and the “Agile Industrial Complex” is part of the problem. Agilists must go back to the basics and simplicity of the Manifesto and 12 Principles. The Heart of Agile and Modern Agile are examples of basic, simple frameworks. Agilists also have much to learn from social sciences.

  • How Do We Think about Transactions in (Cloud) Messaging Systems? An Interview with Udi Dahan.

    Do today's cloud-based messaging services have different transactional support than those that preceded it? If so, what are the implications? In this interview with distributed systems expert Udi Dahan, we explores the question.

  • Correctness vs Change: Which Matters More?

    In ongoing software development, our core work is changing code. Jessica Kerr argues that by building changeable software on top of existing, well-understood components, and by improving delivery automations, teams will get better at their core work of delivering value and "changing reality".

  • Q&A on the Book Mastering Collaboration

    The book Mastering Collaboration by Gretchen Anderson provides techniques and exercises that can be used to improve collaboration in teams and between teams and their environment. It explores topics like enlisting people, teamworking, trust, and respect, generating ideas collectively, decision making, and transparent communication.

  • How We Reduced Our React App’s Load Time by 60%

    React handles UI updates efficiently but it does not magically make your web app faster. As our application grew in size, we started noticing some drawbacks of our setup. Although we knew how React worked and how Redux manages state, our application had bloated in size. We started seeing application crashes and jank. It was time to drive down the technical debt and make performance improvements!

  • Why Should We Care about Technology Ethics? The Updated ACM Code of Ethics

    The 2018 rewrite of the ACM code of ethics and professional conduct has brought it up-to-date with new technologies and societal demands. This code supports the ethical conduct of computing professionals through a set of guidelines for positively working in the tech industry.

  • Q&A on the Book Evolvagility: Growing an Agile Leadership Culture from the inside out

    The book Evolvagility: Growing an Agile Leadership Culture from the Inside Out explains how focusing on inner-agility through sensemaking, communication, and relationship intelligence can increase the outer agility of organizations. It describes Sense-and-Respond leadership, an approach to catalyzing the creation of outcomes by sensing acutely, responding gracefully, and sensing deliberately.

  • Sustainable Operations in Complex Systems with Production Excellence

    Successful long-term approaches to production ownership and DevOps require cultural change in the form of production excellence. Teams are more sustainable if they have well-defined measurements of reliability, the capability to debug new problems, a culture that fosters spreading knowledge, and a proactive approach to mitigating risk.

  • WebAssembly and Blazor: A Decades Old Problem Solved

    A framework, named Blazor because it runs in the browser and leverages a templating system or "view engine" called Razor, enables the scenario .NET developers almost gave up on. It doesn't just allow developers to build client-side code with C#, but also allows developers to run existing .NET Standard DLLs in the browser without a plugin. Here's the story of WebAssembly and Blazor.

  • Author Q&A: Chief Joy Officer

    Richard Sheridan has released his next book: Chief Joy Officer: How Great Leaders Elevate Human Energy and Eliminate Fear. Building on the concepts from his first book, he provides practical advice for leaders who want to cultivate a culture of joy in their organization. He defines Joy as the satisfaction of a job well done, of building products that people love to use, with teamwork and trust.

  • Being an Ethical Software Engineer

    Our lives are improving because of technology. Software engineering is one of the more influencing practices we have today that is shaping society, but it doesn’t look like the industry is owning this social responsibility. At the end of the day, it’s not just about being better developers, but rather about being better people.

  • A Different Meaning of CI - Continuous Improvement, the Heartbeat of DevOps

    This personal experience report shows that political in-house games and bad corporate culture are not only annoying and a waste of time, but also harm a lot of initiatives for improvement. Whenever we become aware of the blame game, we should address it! DevOps wants to deliver high quality. The willingness to make things better - products, processes, collaboration, and more - is vital.

BT