Posts Tagged ‘Communication’
[DevoxxUK2026] Aspiring Speakers Session: Cloud, Code, and Curiosity
Lecturer
Omodolapo Babatunde (often referred to as Dolapo) serves as a Cloud Architect, Communications Manager, and founder of Unora Studio. His work focuses on building products and services for technical professionals, communities, and organizations, with emphasis on digital innovation, inclusive growth, and knowledge sharing.
Abstract
Omodolapo Babatunde explores the critical yet often overlooked phase between initial coding proficiency and mature systems thinking. Emphasizing intentional curiosity, creative experimentation, systems perspectives, and effective communication, the talk offers practical guidance for navigating career ambiguity and fostering sustainable professional development.
Cultivating Growth Through Intentional Curiosity
Omodolapo begins by prompting reflection: when did you last attempt something uncertain? This question frames his journey from uncertainty about industry directions—cloud computing, AI, quantum technologies—toward proactive engagement. Facing fears by weighing potential gains against losses, he advocates intentional curiosity as the catalyst for advancement.
This curiosity manifests through three pillars: creative experimentation, systems thinking, and communication. Experimentation represents the growth sweet spot where developers encounter roadblocks after basic implementation. Rather than stalling, experimentation drives iteration. Omodolapo documented his cloud learning via a blog titled “Cloud, Code, and Curiosity,” which facilitated knowledge sharing, community building, and unexpected opportunities.
Systems thinking emerges once coding fundamentals solidify. It involves evaluating trade-offs, socio-technical implications, and broader impacts on stakeholders. Solutions must consider not merely technical feasibility but organizational and human dimensions.
Communication completes the triad. Translating complex systems requires articulating ideas clearly, listening actively, questioning constructively, and aligning teams. Writing documentation tests true understanding, while presentation skills ensure ideas gain traction.
Omodolapo reinforces these concepts through Receipts, a career record intelligence application enabling professionals to capture, organize, and retrieve achievements efficiently. He encourages audience engagement with the tool.
Conclusion
The presentation culminates in a call to action: remain curious, execute pending experiments, connect with others, and document progress. Whether launching projects, sending messages, or presenting at conferences, proactive steps generate the most valuable career assets. By carrying people along and embracing uncertainty, technologists position themselves at the forefront of innovation.
Links:
[DevoxxFR2025] Alert, Everything’s Burning! Mastering Technical Incidents
In the fast-paced world of technology, technical incidents are an unavoidable reality. When systems fail, the ability to quickly detect, diagnose, and resolve issues is paramount to minimizing impact on users and the business. Alexis Chotard, Laurent Leca, and Luc Chmielowski from PayFit shared their invaluable experience and strategies for mastering technical incidents, even as a rapidly scaling “unicorn” company. Their presentation went beyond just technical troubleshooting, delving into the crucial aspects of defining and evaluating incidents, effective communication, product-focused response, building organizational resilience, managing on-call duties, and transforming crises into learning opportunities through structured post-mortems.
Defining and Responding to Incidents
The first step in mastering incidents is having a clear understanding of what constitutes an incident and its severity. Alexis, Laurent, and Luc discussed how PayFit defines and categorizes technical incidents based on their impact on users and business operations. This often involves established severity levels and clear criteria for escalation. Their approach emphasized a rapid and coordinated response involving not only technical teams but also product and communication stakeholders to ensure a holistic approach. They highlighted the importance of clear internal and external communication during an incident, keeping relevant parties informed about the status, impact, and expected resolution time. This transparency helps manage expectations and build trust during challenging situations.
Technical Resolution and Product Focus
While quick technical mitigation to restore service is the immediate priority during an incident, the PayFit team stressed the importance of a product-focused approach. This involves understanding the user impact of the incident and prioritizing resolution steps that minimize disruption for customers. They discussed strategies for effective troubleshooting, leveraging monitoring and logging tools to quickly identify the root cause. Beyond immediate fixes, they highlighted the need to address the underlying issues to prevent recurrence. This often involves implementing technical debt reduction measures or improving system resilience as a direct outcome of incident analysis. Their experience showed that a strong collaboration between engineering and product teams is essential for navigating incidents effectively and ensuring that the user experience remains a central focus.
Organizational Resilience and Learning
Mastering incidents at scale requires building both technical and organizational resilience. The presenters discussed how PayFit has evolved its on-call rotation models to ensure adequate coverage while maintaining a healthy work-life balance for engineers. They touched upon the importance of automation in detecting and mitigating incidents faster. A core tenet of their approach was the implementation of structured post-mortems (or retrospectives) after every significant incident. These post-mortems are blameless, focusing on identifying the technical and process-related factors that contributed to the incident and defining actionable steps for improvement. By transforming crises into learning opportunities, PayFit continuously strengthens its systems and processes, reducing the frequency and impact of future incidents. Their journey over 18 months demonstrated that investing in these practices is crucial for any growing organization aiming to build robust and reliable systems.
Links:
- Alexis Chotard: https://www.linkedin.com/in/alexis-chotard/
- Laurent Leca: https://www.linkedin.com/in/laurent-leca/
- Luc Chmielowski: https://www.linkedin.com/in/luc-chmielowski/
- PayFit: https://payfit.com/
- Devoxx France LinkedIn: https://www.linkedin.com/company/devoxx-france/
- Devoxx France Bluesky: https://bsky.app/profile/devoxx.fr
- Devoxx France Website: https://www.devoxx.fr/