InfoQ Homepage Agile Conferences Content on InfoQ
-
Optimizing Software Workflow: Exploring Fundamental Impacts in Technology
Software only has value when shipped; faster release cadence matters. Development, deployment, and operations require different thinking, metrics, and investments. There are four impacts in tech: product success, compute capacity, engineering capacity, and strategic innovation. The biggest expense is people. AI shifts engineers toward deeper problem understanding, not fewer engineers.
-
Building a Collaborative Platform Culture in a Bank
A platform is a collaboration system, not infrastructure. Culture follows structure: platform teams can build open support sessions, create super user awards for contributing developers, and establish shared open standards to grow an engineering mindset. Developers and product teams depend on a platform team, which in turn depends on application teams; to go forward, they need shared standards.
-
Beyond Autonomous Teams in Software Product Development
Autonomous teams are an article of faith in modern software development. The shape of our value determines what we can do; it determines our trade-offs between agency and coherence. We all have a purpose, and we all have agency to do something, hence the suggestion is moving from product focus to value center thinking.
-
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.
-
What Testers Can Do to Ensure Software Security
A secure software development life cycle means baking security into plan, design, build, test, and maintenance, rather than sprinkling it on at the end, Sara Martinez said in her talk Ensuring Software Security. Testers aren’t bug finders but early defenders, building security and quality in from the first sprint. Culture first, automation second, continuous testing and monitoring all the way.
-
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.
-
Lessons Learned from Migrating a Legacy Test Suite to Gauge with Kotlin
Liran Yushinsky shared how his team replaced brittle bash and kubectl tests with a unified Kotlin + Gauge framework. Using Fabric8, Terraform, and Ansible, they automated their test environments. Feedback loops dropped from hours to minutes, developers joined testing efforts, and shared ownership boosted quality and release speed.
-
Developing and Deploying Software in a Sustainable Way
Sustainable APIs benefit most from minimalism, Jochen Joswig said at OOP Conference . Deployment should consider energy, usage, carbon intensity, hardware acquisition. Remote work, long device lifespans, and green office practices can lower emissions. Efficient CI, selective builds, smaller artefacts, and optimized assets can further reduce energy use.
-
How to Do Sociotechnical Design Using Domain-Driven Design and Change Smuggling
Domain-Driven Design (DDD) can upskill sociotechnical design to navigate organizational dynamics and decision complexity in human systems. Change smuggling offers a practical way to launch small, safe-to-fail probes, nudging sociotechnical changes to emerge organically and conversationally.
-
How AI with Prompt Engineering Supports Software Testing
AI is becoming a key QA tool, aiding in faster scenario generation, risk detection, and test planning. Arbaz Surti showed how effective prompting using roles, context, and output format helps to get clear, relevant, and actionable test scenarios. AI can boost testers, but human judgment is needed to ensure relevance and quality.
-
Changing a Career from Developing Software to Test Automation
A developer who became a test automation engineer faced a challenging learning curve due to limited testing experience. He learned the importance of test levels, when not to automate, and how QA is vital to quality. Motivated by impact, growth, and teamwork, he values communication and continuous learning.
-
Why Software Engineering Governance Matters: Reducing Risk without Slowing down
Software engineering governance helps teams make decisions, Sarah Wells said at Goto Copenhagen. She argued it should support value delivery, not hinder it. Poor governance slows progress and can increase costs. A technical strategy with a radar can help teams to make better decisions, and aligning with DORA capabilities can boost their performance.
-
DevGreenOps: How to Design Sustainable Digital Services
DevGreenOps, also known as DevSusOps, is an extension of the DevOps approach, in which environmental sustainability considerations are integrated into every step of the DevOps cycle, Jochen Joswig said in his talk at OOP Conference. Applying transparency, minimalism, efficiency, and awareness helps us to design sustainable digital services.
-
Producing a Better Software Architecture with Residuality Theory
Software architecture is tough because it blends coding, math, and business systems. Due to surprises, architectures tend to become irrelevant over time, Barry O'Reilly said. He presented residuality theory, where he suggested stressing naive architectures to reveal hidden “attractors” in complex business systems. This allows designs to better survive change and uncertainty.