InfoQ Homepage GOTO Conference Content on InfoQ
-
How Observability and Telemetry Can Enhance the Practice of Software Engineering
Observability must evolve with serverless, event-driven architectures. OpenTelemetry can decouple telemetry from vendors, letting developers emit consistent, high-quality data that explains real system behavior. Shared vocabularies and good telemetry make debugging faster and improve reliability, speed, and developer productivity.
-
Platform as a Product: Delivering Value While Balancing Competing Priorities
Software platforms must be treated as products. Success requires balancing engineering, design, usability, security, and value for internal customers and the organisation, Abby Bangser mentioned in her talk Platform as a Product. A product mindset, clear ownership, and continuous investment prevent bottlenecks, platform decay, and wasted effort, enabling scalable, sustainable value over time.
-
Decentralizing Architectural Decisions with the Architecture Advice Process
Our system architectures have changed as technology and development practices have evolved, but the way we practice architecture hasn’t kept up. According to Andrew Harmel-Law, architecture needs to be decentralized, similar to how we have decentralized our systems. The alternative to having an architect take and communicate decisions is to “let anyone make the decisions” using the advice process.
-
Taking the Technical Leadership Path
Technical leaders face challenges beyond individual contributor work: aligning with business on investments, managing systemic aspects, mentoring, and keeping up with a changing codebase. We need technical alignment—shared codestyle, implementation patterns, and standards—to avoid accidental complexity. Leadership grows through practicing skills, improving team issues, and acting as a role model.
-
Things Software Developers Think They Don’t Need to Care about, But Can Impact Their Job
Holly Cummins gave a keynote at Goto Copenhagen where she urged developers to care about overlooked issues that shape their work. She warned of unintended consequences of design decisions, promoted systems thinking and statistical literacy, stressed mastering concurrency as hardware evolves beyond Moore’s Law, and mentioned the impact of AI on the job market.
-
How Artificial Intelligence Can Help Us Connect with Customers
In software development, success means going beyond meeting requirements. We must create products that surprise and delight users and are innovative, create impactful solutions, Ken Hughes said in the keynote “Connection is Everything”. AI can help us connect with customers and create better user experiences.
-
Large Scale Experimentation at Spotify
When you want to scale the number of A/B tests to do many experiments at the same time, you need to adopt your processes and platform, and it might also impact your culture. Doing product research with controlled experiments helps to confront your ideas about how customers will use your product in reality, and check if those ideas actually impact user behaviour.
-
Open Source Development at the UK Government
New code developed for GOV.UK will be open by default. Coding in the open enables reuse and increases transparency. The UK government wants to provide digital services which are so good that people want to use them; services which are leading to better interaction between the government and citizen.
-
Getting the Data Needed for Data Science
Data science is about the data that you need; deciding which data to collect, create, or keep is fundamental argues Lukas Vermeer, an experienced Data Science professional and Product Owner for Experimentation at Booking.com. True innovation starts with asking big questions, then it becomes apparent which data is needed to find the answers you seek.
-
Using Models in Developing Software for Self-Driving Cars
Models play an important role in developing software for autonomous systems like self-driving cars; they are used to simulate and verify behavior, document the system, and generate code. Jonathan Sprinkle explains how to model software used in autonomous systems, the benefits of modeling, using test data to validate the software that drives a car and techniques for writing reliable code.
-
Becoming a Responsive Enterprise
Software-driven companies are taking over the world because they are responsive organizations, built on 'sense and respond' instead of 'plan and predict'. In the next decade every large scale organization will be digitized and will effectively become a software-driven enterprise. Vikram Kapoor, CEO at Prowareness, explored how organizations can increase their responsiveness.
-
Understanding Large Codebases with Software Evolution
InfoQ interviewed Adam Tornhill, author of Your Code as a Crime Scene, about software evolution and mining social information from code and how to use this to increase the understanding of large codebases, how to create a geographical profile of code, and the benefits that can be gained from techniques like mining social information and geographical profiling.
-
Second GOTO Berlin Conference Due Early November
The second GOTO conference in Berlin is due early November, with two days of conference on November 6-7, preceded by one day of training. The program is titled "for developers, by developers" with emphasis placed on presenting the latest developments as they become relevant and interesting for the software development community.
-
GOTO Berlin: Problems Using Your Own Public API
Using your own public API can be a challenge, Phil Calcado, Director of Engineering at Soundcloud, declared when sharing his experiences managing and rebuilding a large Rails application in a talk at the GOTO Berlin Conference.
-
GOTO Berlin: Microservices as an Alternative to Monoliths
James Lewis talked at the GOTO Berlin Conference about an alternative to the traditional way of building systems where all functionality is put into one big application with one big database, instead using a pattern where entirely separate business capabilities, together with their own data, are kept separate in microservices.