InfoQ Homepage QCon London 2020 Content on InfoQ
Articles
RSS Feed-
Increasing Developer Effectiveness by Optimizing Feedback Loops
We can think of engineering as a series of feedback loops: simple tasks that developers do and then validate to get feedback, which might be by a colleague, a system (i.e. an automation) or an end user. Using a framework of feedback loops we have a way of measuring and prioritizing the improvements we need to do to optimize developer effectiveness.
-
Scaling Distributed Teams by Drawing Parallels from Distributed Systems
An effective distributed team’s characteristics are accountability, good communication, clear goals and expectations, a defined decision-making process, and autonomy with explicit norms. Ranganathan Balashanmugam spoke about scaling distributed teams around the world at QCon London 2020. In his talk he showed how we can apply distributed systems patterns for scaling distributed teams.
-
Exploring Costs of Coordination During Outages - QCon London Q&A
Coordinating different skills, knowledge and experience is necessary for coping with complex, time-pressured events, but it incurs costs. Well-designed coordination is smooth and can be trained for. Learning how to take initiative, being observable to your counterparts and engaging in reciprocity are examples of strategies engineers can use to lower costs of coordination during outages.
-
Leading through Experimentation in a Distributed Agile Organization
Change is our work as agile coaches and leaders. When your teams and organizations are distributed, experimentation becomes the primary tool to aid our change navigation. As online collaboration technologies improve and we begin to understand how flexibility and choice become critical in distributed work, modeling and teaching experimentation are important for agile coaches and all leaders.
-
Key Takeaway Points and Lessons Learned from QCon London 2020
QCon returned to London this past March for its fourteenth year in the city, attracting over 1,600 senior developers, architects, data engineers, team leads, and CTOs. This article provides a summary of the key takeaways.