Day One of the 19th annual QCon London conference was held on April 7th, 2025, at the Queen Elizabeth II Conference Centre in London, England. Key takeaways included: developer joy increases developer productivity; platforms are “not an island,” but organizations adopting them do so within an ecosystem; collaborative software can be fragile; and local-first software is a design principle by which the data on a user’s device is the primary source of truth.
What follows is a summary of the keynote address and highlighted presentations.
Keynote Address: A Thirteen Billion Year Old Photograph
Table of Contents
- QCon London 2025 Day 1: Parsing Data from Space, Developer Joy, Local First Apps, Platforms
Dr. Kenneth Harris, Senior Project Manager at The Aerospace Corporation and Former Rocket Scientist and Integration Engineer at NASA, presented his keynote address entitled, A Thirteen Billion Year Old Photograph.
Harris started his presentation with a picture of the 30 billion-year-old Tarantula Nebula as the basis for describing some history and details of infrared radiation. He described how infrared is used in the James Webb telescope and how the numerous images from the instruments in the telescope are processed.
In 1800, while making measurements using a thermometer in the path of visible light, British astronomer Sir William Herschel stumbled upon a temperature change in the area that was just “beyond red.” Initially referred to as “invisible heat,” infrared radiation, or the wavelength range in the infrared spectrum, is used in many applications of the analytical sciences. Moving forward in time to 1929, Hungarian physicist Kálmán Tihanyi invented the first infrared camera.
Harris described many details of the James Webb telescope, starting with the lens that allows the light into the telescope to operate the instrumentation, such as spectrometers.
From there, Harris continued with additional details that included: 3D simulations of the various near- and mid-infrared instruments; the cosmic redshift; the temperature differences on each side of the sun shield (85℃ and -230℃); and what is inside the instrument module.
The data packets from the instrument are processed using several file formats: .fits, Flexible Image Transport System; .json, JavaScript Object Notation; .ecsv, Enhanced Comma Separated Value; and .asdf, Advanced Scientific Data Format.
Generating a final image involves layering the various images captured by the instrument. There are six steps: stack the images; assign blue images; assign green images; assign orange images; assign red images; and finally create the composite.
Harris concluded his presentation by demonstrating the Mikulski Archive for Space Telescopes (MAST) portal, managed by the Space Telescope Science Institute (STSci). Entering a value, say, NGC 3324, in the target field will provide all the images and corresponding details of the Carina Nebula.
Highlighted Presentations: Productivity is Messing Around and Having Fun | Local First – How To Build Software Which Still Works After the Acquihire | Your Platform is Not an Island: Embracing Evolution in Your Ecosystem
Productivity Is Messing Around and Having Fun was presented by Holly Cummins, Full-Stack Engineer, Building Quarkus at Red Hat, and Trisha Gee, Developer Champion and Author of “Head First Java” (3rd Edition), “97 Things Every Java Developer Should Know,” and “Getting to Know IntelliJ IDEA.”
Cummins and Gee kicked off their presentation by asking the question: “Developer Joy and Developer Productivity Engineering: are these opposites, or the same?” Cummins recalled a story in which her team was working harmoniously together, writing code for a project. The product manager approached her one day and asked, “Why are you smiling?” After stating that the team is happy, the product manager responded, “Work is not a place to be happy!“
Fred Brooks, an American computer scientist and author of “The Mythical Man-Month: Essays on Software Engineering,” described the joys of the craft as: the sheer joy of making things; the pleasure of making things that are useful to other people; the fascination of fashioning complex puzzle-like objects of interlocking moving parts and watching them work; the joy of always learning; and the delight of working in such a tractable medium.
Joy in the workplace has business value, but sometimes management doesn’t recognize that. Aristotle once said, “pleasure in the job puts perfection in the work.“
The research, which can be measured, shows that fun is good for business. Examples include: Effects of Workplace Fun on Employee Behaviors: Focused on Generation Y in the Hospitality Industry from UMass Amherst; Positive Intelligence from the Harvard Business Review; and Happiness and Productivity from The University of Warwick.
The 2014 State of DevOps Report concluded that job satisfaction is the number one predictor of organizational performance.
The SPACE Framework, introduced in 2021, is a formal approach to understanding and enhancing developer productivity. Cummins and Gee focused on the Activity and Efficiency & Flow dimensions of this framework.
For the Activity dimension, the use of incentives to produce more lines of code was explored.
For the Efficiency & Flow dimension, Cummins and Gee introduced the Default Mode Network, a “system of connected brain areas that show increased activity when a person is not focused on what is happening around them.” For example, according to a Business Insider news piece from 2016, 72% of people get their best ideas while showering. Cummins and Gee shared their own personal activities on how they are more productive.
In summary, Cummins and Gee offered these key takeaways: be careful how productivity is measured because that metric determines what you will get (do not use LOC!); automate drudgery that stops developers from being effective at their job; being happier makes developers better at their job; having down time (and showers, or knitting jumpers) makes developers better at their job
InfoQ will follow-up with a more detailed news story.
Local First – How To Build Software Which Still Works After the Acquihire was presented by Alex Good, Software Engineer at Ink & Switch and Core Contributor on the Automerge CRDT Library.
Good started his presentation with a description of his local workout tracker application that was simple until he was asked for it to be collaborative. This required tasks such as: design and implement a backend server API; synchronization related to updates; establish and maintain a server; and authentication and authorization. This creates a problem by which users now depend on servers they cannot control or understand. As once stated by Leslie Lamport, American computer scientist and mathematician:
A distributed system is one in which the failure of a computer you didn’t even know existed can render your computer unusable.
Local-first software is a “design principle in which the data on the user’s device is the primary source of truth; other copies on servers or other users’ devices are secondary.” Attributes include: no spinners; multi-device; using the network is optional; seamless collaboration; secure and private; and ownership and control.
An example of local-first is GitHub. However, there are synchronization issues that can be avoided using a finer-grained data model for each commit over the “snapshot of the filesystem” approach. This provides a default automatic resolution of conflicts to access conflicting values during synchronization. This is useful for more complex applications.
Collaboration as version control provides benefits, such as: a generic infrastructure; reduced complexity; and improved management of change.
Your Platform is Not an Island: Embracing Evolution in Your Ecosystem, was presented by Rachael Wonnacott, Associate Director for Container Platform Engineering at Fidelity International.
Wonnacott kicked off her presentation by stating an organization’s platform is not an island. The developer experience matters in platform engineering but shouldn’t be a major focus. She maintained that organizations are an ecosystem where teams and people interact as a living, breathing system. Organizations grow organically, but there are notable differences in the spectrum of startups and large corporations.
Historically, an on-premise infrastructure created an application, packaged it, and threw it over the wall, as it were, to the customer.
Conway’s Law, a principle created by American computer scientist Melvin Conway, is defined as: “any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.“
The reality within the enterprise, Wonnacott explained, is that on-premise dependencies are essentially technical debt in disguise. A Fidelity International container platform case study revealed that “on average, a cloud developer only spends 11% of their time actually writing code. Instead, about 3x as much time is spent working on boilerplate, plumbing, debugging pipelines, waiting, and writing “code about code” that has little to do with their business.“
Ideally, developers should only focus on applications and data in cloud development. Things such as runtime, virtualization and storage should be handled by others.
Cloud operations messaging has evolved using a new cloud operating model analogy, where developers now have a choice between the existing model, known as the “Public Cloud House,” or the “Kubernetes Hotel,” offering a fully managed platform that incorporates container hosting, platform compliance, data and integration services, all of which can be isolated and segregated from one another.
The application lifecycle could be a reference to a platform being an island, but platforms should do more than connect; they should amplify. There should be a dynamic configuration generation approach such that the developer entry point is simplified using dynamic configuration, and deployment mechanisms should be transparent to the end user.
Wonnacott described how platform engineering can be used to improve the application lifecycle that strikes a balance between developer experience and business outcomes.
In conclusion, Wonnacott stated that a platform can be a bridge, not an island.
date:2025-04-13 05:45:00
QCon London 2025 Day 1: Parsing Data from Space, Developer Joy, Local First Apps, Platforms
QCon London is renowned for bringing together software leaders and innovators to discuss the latest trends and challenges in the software development world. Day 1 of QCon London 2025 promised (and delivered) a fascinating mix of topics. From deciphering complex data streams originating from space to cultivating developer joy, exploring the potential of local first applications, and understanding the intricacies of modern platform engineering, the day was packed wiht insightful talks and discussions. Here’s a breakdown of the key themes and takeaways from each area.
Parsing Data from Space: Challenges and Solutions
The sheer volume and complexity of data generated by space missions present unique challenges for software engineers. Speakers at QCon London 2025 Day 1 shared their experiences in building systems to process and analyze this data, covering topics such as:
- data Acquisition and Preprocessing: Extracting relevant information from noisy and incomplete datasets. Addressing challenges related to data formats, transmission delays, and data loss.
- Real-time Processing: Developing systems to analyze data in real-time, enabling timely decision-making for mission control and scientific discovery.
- Scalability and reliability: Designing robust and scalable infrastructure to handle growing data volumes and ensure continuous operation.
- Anomaly Detection: Identifying unusual patterns and events in the data that may indicate spacecraft malfunctions or new scientific discoveries.
- Data Visualization: Techniques and technologies used to translate the raw data into insightfull information.
Case Study: Analyzing Martian Weather Data
One particularly compelling presentation detailed the challenges of analyzing weather data from the Martian surface. The presentation elaborated on:
- Dealing with infrequent and inconsistent data transmissions due to orbital mechanics and interaction limitations.
- Building custom algorithms to compensate for data gaps and noise.
- Leveraging machine learning to predict weather patterns and alert scientists to potential dust storms.
Practical Tips for Handling Space Data
Several speakers offered practical advice for engineers working with space data, including:
- Embrace data engineering best practices: Treat your data as a valuable asset and apply rigorous data management techniques.
- Automate data pipelines: Automate repetitive tasks like data ingestion, cleansing, and change to improve efficiency and reduce errors.
- Prioritize data quality: Robust data validation and error handling are crucial to ensure data integrity and prevent downstream problems.
- Utilize cloud-based solutions: Leverage the scalability and cost-effectiveness of cloud platforms for data storage, processing, and analysis.
- Collaborate with domain experts: Work closely with scientists and engineers to understand their data needs and translate them into technical solutions.
Developer Joy: Creating Environments Where Engineers Thrive
Developer joy, often overlooked, plays a crucial role in productivity, retention, and overall software quality. Several sessions at QCon london 2025 Day 1 focused on strategies for fostering a positive and fulfilling work environment for developers.
- Reducing cognitive Load: Simplifying development workflows, providing clear documentation, and minimizing distractions.
- Empowering Autonomy and Ownership: Providing developers with the freedom to choose their tools and approaches, and giving them ownership over their work.
- Fostering Collaboration and Community: Encouraging communication, knowledge sharing, and mentorship opportunities.
- Promoting Continuous Learning and Growth: Providing opportunities for developers to learn new skills,attend conferences,and engage in professional development.
- Providing Effective Feedback and Recognition: Giving developers regular feedback on their work and recognizing their contributions.
Benefits of Developer Joy
Speakers highlighted the various benefits of prioritizing developer joy,including:
- Increased Productivity: Happy and engaged developers are more productive and efficient.
- Reduced Turnover: A positive work environment reduces employee turnover and attracts top talent.
- Improved Software Quality: joyful developers are more likely to take pride in their work and produce high-quality code.
- Greater Innovation: A culture of experimentation and creativity fosters innovation and problem-solving.
| Positive Action | Outcome |
|---|---|
| Clear Documentation | Reduced Cognitive Load |
| Autonomy | Increased Engagement |
| Regular Feedback | Improved Performance |
Practical Tips for Cultivating Developer Joy
here are some practical tips for creating a more joyful work environment for developers:
- Invest in good tooling: Provide developers with the tools thay need to be productive and efficient.
- Automate repetitive tasks: Use automation to reduce mundane tasks and free up developers to focus on more challenging problems.
- Create a culture of learning: Encourage developers to learn new skills and technologies.
- Embrace flexible work arrangements: offer flexible work options to help developers balance their work and personal lives.
- Foster a sense of purpose: Help developers understand the impact of their work and connect them to the company’s mission.
- Celebrate successes: Acknowledge and celebrate milestones and achievements to boost morale and foster a sense of accomplishment..
Local First Apps: Rethinking data Ownership and User Experience
Local first apps, which prioritize storing data locally on the user’s device, are gaining popularity as developers seek to improve performance, enhance privacy, and provide a more seamless offline experience. QCon London 2025 Day 1 explored the benefits and challenges of this emerging paradigm.
- Advantages of Local First Architecture: Improved performance, enhanced privacy, offline functionality, and reduced reliance on external services.
- Challenges of Local First Architecture: Data synchronization, conflict resolution, security, and platform compatibility.
- Technologies for Building Local First Apps: CRDTs (Conflict-Free Replicated Data Types), local databases (e.g., SQLite), and peer-to-peer networking technologies.
- use Cases for Local First Apps: Collaboration tools, note-taking apps, personal finance managers, and offline-first mobile applications.
First-Hand Experience: Building a Collaborative Markdown Editor
One session provided a first-hand account of building a collaborative markdown editor using a local first architecture. The speaker shared insights into:
- Challenges of implementing CRDTs for real-time collaboration.
- Managing data synchronization and conflict resolution across multiple devices.
- Optimizing performance for offline use.
Benefits and Trade-offs of Local First Apps
| Benefit | Trade-off |
|---|---|
| Better Privacy | Synchronization Complexity |
| Offline Access | Storage Requirements |
| Faster Performance | Data Consistency Challenges |
Practical Tips for Designing Local First Apps
- Prioritize offline functionality: Design your app to be fully functional even without an internet connection.
- Use CRDTs for data synchronization: CRDTs can simplify conflict resolution and ensure data consistency.
- implement robust security measures: Protect user data stored locally on the device.
- Choose the right local database: Consider factors such as performance, storage capacity, and platform support.
- Focus on a seamless user experience: Make the app easy to use and intuitive, even when running offline.
Platforms: Building Internal Developer Platforms for Velocity and Governance
Platform engineering, the practise of building and managing internal developer platforms (IDPs), is gaining traction as organizations seek to improve developer productivity, streamline operations, and enhance governance. QCon London 2025 Day 1 featured several insightful talks on platform strategy and implementation.
- Defining the Scope of an IDP: identifying the core services and capabilities to include in the platform,such as infrastructure provisioning,deployment pipelines,monitoring,and security.
- Choosing the Right Technologies: Selecting the appropriate tools and technologies for building the platform, such as Kubernetes, containers, service meshes, and observability platforms.
- Building a Developer-Centric Experience: Designing the platform with the needs of developers in mind, providing self-service capabilities and intuitive interfaces.
- Measuring the Impact of the Platform: Tracking key metrics such as developer productivity, deployment frequency, and infrastructure costs.
- Platform Governance and Security: Establishing clear guidelines and policies for platform usage and ensuring that the platform is secure and compliant.
Platform Engineering Case studies
- Migration to a Self-service Infraestructure: How to build a self-service process,giving developers more control over their environments.
- Cost Reduction with Container Orchestration: Case study about reduced costs by using a container orchestration platform.
Key Considerations for Platform Engineering
Here are some key factors to consider when embarking on a platform engineering initiative:
- Start small and iterate: Begin with a limited set of services and gradually expand the platform based on user feedback and evolving needs.
- Focus on developer experience: Make the platform easy to use and provide excellent documentation.
- Automate everything: Automate as many tasks as possible to reduce manual effort and improve consistency.
- Embrace infrastructure as code: Use infrastructure as code (IaC) to manage infrastructure in a consistent and repeatable way.
- Treat the platform as a product: Apply product management principles to the platform, continuously gathering feedback and iterating on its design and functionality.
- Secure the platform at every level: Implement robust security controls to protect the platform and the applications running on it.
| Platform Aspects | Considerations |
|---|---|
| Developer Experience | Ease of Use, Documentation |
| Security | Access Control, Vulnerability Scanning |
| Automation | CI/CD Pipelines, Infrastructure Provisioning |
The Future of Platform Engineering
Several speakers discussed the future of platform engineering, noting the rise of:
- AI-powered platforms: Using AI to automate platform operations and provide intelligent insights.
- Serverless platforms: Abstracting away infrastructure management and allowing developers to focus on building applications.
- Edge platforms: Extending the platform to the edge to support distributed applications and low-latency scenarios.