InfoQ Homepage Software Engineering Content on InfoQ
-
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.
-
Level up on the Software Practices, Patterns and Skills Most In-Demand at QCon Plus
QCon Plus Online Software Development Conference (May 10-20) is brought to you by InfoQ to accelerate the learning path of senior software developers, software architects, software engineers and team leaders. Learn actionable insights from practising software leaders who are creating software, scaling architectures and fine-tuning their technical leadership to help you make the right decisions.
-
Qovery: a Heroku for Almost Any Cloud Provider?
Qovery started on a journey to build a developer’s productivity tool which would allow scaling companies to keep up the rapid pace of delivery, without sacrificing quality or stability. One way is by combining the simplicity and “magic” of a PaaS, like Heroku, with IaaS’ flexibility. In a conversation with InfoQ, the CEO and founder, Romaric Philogene, provided more insights into their journey.
-
MLOps: Continuous Delivery of Machine Learning Systems
Developing, deploying, and keeping machine learning models productive is a complex and iterative process with many challenges. MLOps means combining the development of ML models and especially ML systems with the operation of those systems. To make MLOps work, we need to balance iterative and exploratory components from data science with more linear software engineering components.
-
How to Embrace “You Build It, You Run It” with Paul Hammant at QCon London
Paul Hammant talked at QCon London about having developers responsible for the first line of support in production, as the saying goes, “if you build it, you run it.” Hammant recommends following this practice only if there are proper support levels and escalation policies defined. As a result, companies could reduce the chances of burnout or staff quitting.
-
Live Recorder: Debugging C++, Rust, and Go with Capture and Replay of Nondeterministic Data
Early in the year the Undo team released Live Recorder 5, a “software flight recorder technology” for C, C++ and Go applications that enables the capture of all non-deterministic data within an application’s execution for debugging purposes. The resulting recording supports the replay of events in time, backwards and forwards, when looking for and fixing bugs.
-
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.