BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Software Engineering Content on InfoQ

  • Google Software Engineering Culture

    Several Google engineering practices have been largely adopted across the company until today and still contribute to the company's success. In 2017, a staff software engineer published some of these practices, not limited to software development. Today, Google fosters a team culture of creativity, autonomy, and innovation.

  • Google Releases New Java Logging Framework

    Google announced the release of a new open-source Java logging framework called Flogger that improves upon existing logging frameworks by reducing the cost of disabled log statements, increasing overall readability, and allowing extensibility.

  • Q&A with Katrina Clokie on Testing in DevOps for Engineers

    Wellington's DevOpsDays NZ recently closed with a keynote by Katrina Clokie on the Testing Skills and Superpower which engineers can utilise in a DevOps setting. The author of A Practical Guide to Testing in DevOps spoke with InfoQ to discuss the changes she's seen in the testing landscape and how this is further impacted by the move to embrace DevOps principles.

  • Software Engineering for Creativity, Collaboration, and Inventiveness

    A software engineering discipline must be iterative, based on feedback, incremental, experimental, and empirical. Craftsmanship is not sufficient; engineering is an amplifier, it enhances creativity, collaboration, and inventiveness. Continuous delivery is grounded in engineering principles.

  • Leaders Discuss How to Build Great Engineering Cultures

    QConLondon’s Building Great Engineering Cultures track brought together a panel of leaders to take questions from an audience. Leaders from Google, Sky Betting and Gaming, ITV, Deliveroo and GlobalSign shared how they support and build great cultures for engineers, accounting for individual growth, organisation need, a social conscience and a balanced life.

  • Great Engineering Cultures and Organizations - Afternoon Sessions from QCon London

    The Building Great Engineering Cultures and Organizations track at QCon London 2018 contained talks from practitioners representing digital leaders of the consumer internet as well as transformational corporates from “traditional” sectors. Previously InfoQ published a summary of the morning sessions; this is the summary of the afternoon sessions of this track.

  • Great Engineering Cultures and Organizations - Morning Sessions from QCon London

    The building great engineering cultures and organizations track at QCon London 2018 included talks from practitioners representing digital leaders of the consumer internet as well as transformational corporates from “traditional” sectors. The speakers presented how they established and scaled engineering cultures that keep their organisations ahead of the rest. A summary of the morning sessions.

  • Ethics, Values and Practices for Software Professionals

    Christiaan Verwijs has recently written about the need for a Hippocratic oath for software practitioners. Robert C. Martin and other commentators have made similar calls in recent months. We examine news in this space and the principles which support a professional practice of software development.

  • Book Review Understanding Software by Max Kanat-Alexander

    The book "Understanding Software" by Max Kanat-Alexander is an interesting read for project managers and software architects. It provides insights into how to keep your software simple, and how you can avoid complex unmaintainable software. The book is most useful for project managers and architects.

  • IEEE Helps You Make Sense out of Programming Language Rankings

    Unlike other programming language surveys, the IEEE Programming Language Survey gives you the ability to interactively alter the weights on the ranking criteria. Applying 12 metrics to 10 data sources, they rank 48 languages. They also explain their design, methods, and data sources.

  • 10 Weeks to QCon New York: Keynotes Announced and Early Peek into the Speaker Lineup

    QCon New York (the 6th annual software conference) is just 10 weeks away. June 26-28 QCon returns to its new location at Times Square’s Marriott Marquis, but with the same great lineup of speakers. 2017 features speakers from Stitch Fix, Google, Netflix, Lyft, Pivotal, Redis Labs, among others.

  • CA Technologies CEO Says "Built To Change is the New Paradigm"

    CA Technologies CEO Mike Gregoire opened the recent CA World conference predicting that successful companies of the future will be “Built To Change” by putting software at the center of everything they do, and that they need to be "built to change" from the ground up with software as the primary enabler of competitive advantage. He gave examples of the impact of this disruption.

  • Technologies for the Future of Software Engineering

    The Cloud, infrastructure as code, federated architectures with APIs, and anti-fragile systems: these are technologies for developing software systems that are rapidly coming into focus, claimed Mary Poppendieck. Systems are moving towards the cloud, and APIs are replacing central shared databases and enable the internet of things. We need to develop anti-fragile systems which embrace failure.

  • How Agile and Architecture Parted and Finally Became Friends

    People stopped seeing the need to define the architecture or do software design due to incorrect interpretation of the agile manifesto, argued Simon Brown. Many software developers don’t seem to have a sufficient toolbox of practices and the software industry lacks a common vocabulary for architecture. A good architecture enables agility with just enough up front design to create firm foundations.

  • Deliver Shippable Products with Good Engineering Practices

    Good engineering practices are the tools that help agile teams to deliver shippable products. Although many engineering practices have proved to be effective, they are not as widely used as they should be. Agile anti-patterns like the software testing ice-cream cone, accumulating technical debt and functional silos prevent teams from delivering a potentially releasable product.

BT