Posts Tagged ‘Innovation’
[DevoxxFR2013] Keynote “Ouverture”: Welcoming Devoxx France 2013
Lecturer
Nicolas Martignole is an independent consultant and founder of Innoteria, with over a decade of experience in Java. He specializes in architecture, team coaching, and project management, having implemented Scrum at a major French bank since 2008 and previously at Thomson-Reuters as a senior developer and project manager. He authors the blog “Le Touilleur Express.”
Antonio Goncalves is a senior architect consulting and training on Java technologies. Formerly a Weblogic consultant at BEA Systems, he has focused on software architecture since 1998. Author of “Java EE 5” (Eyrolles) and “Beginning Java EE 6 Platform With GlassFish 3” (Apress), he contributes to JCP on Java EE 6, JPA 2.0, and EJB 3.1. He teaches at the Conservatoire National des Arts et Métiers and co-founded the Paris Java User Group.
Zouheir Cadi is an independent consultant specializing in Java/JEE technologies. After years in development, he serves as a production architect, bridging development and operations. Currently at France’s top e-commerce site, he is a Paris JUG board member and Devoxx France co-founder.
José Paumard, passionate about programming for over 20 years, transitioned from assembler and C to Java. An assistant professor at Paris University for 15 years with a PhD in applied mathematics and computer science, he blogs at “Java le soir,” a key French resource on Java. A Paris JUG member, he co-organizes Devoxx France and speaks at conferences like Devoxx and JavaOne.
Abstract
This article examines the opening keynote of Devoxx France 2013, delivered by Nicolas Martignole, Antonio Goncalves, Zouheir Cadi, and José Paumard. It contextualizes the event’s growth, organizational challenges, and community focus, analyzing session selection, special events, and thematic keynotes on past, present, and future of the industry. The discussion highlights transparency in call-for-papers, sponsor contributions, and efforts to engage diverse audiences, underscoring Devoxx’s role in fostering Java and broader tech ecosystems.
Event Overview and Growth Trajectory
The keynote commences with warm welcomes, acknowledging the team’s efforts in hosting Devoxx France 2013, a three-day event with 180 speakers, 75% French-language content. Martignole notes the expansion from 1,250 attendees in the inaugural edition to 1,400, a 220-person increase, signaling strong community interest. This growth mirrors the Devoxx family’s international success: 3,500 in Belgium and 500 for the UK’s debut, organized in just four months.
A satisfaction survey from the previous year, with 301 responses, informs improvements. Despite its length (81% found it too long, 18% much too long), it guides refinements, with Goncalves promising quality control for future iterations. The emphasis on constructive feedback, especially negatives, reflects a commitment to attendee-driven evolution.
Practical details include a free “Meet and Greet” evening with wine and cheese, sponsored by SonarSource, Atlassian, and CloudBees, running until 22:00. Six rooms host sessions, with overflow managed by red-vested volunteers for safety. All talks are recorded on Parleys.com, alleviating concerns about missing content. Community integration is highlighted, welcoming groups like Paris JS and Scala User Group.
Organizational Transparency and Session Selection
Transparency in the call-for-papers process is a focal point. Opened November 20 and closed January 31, it garnered 572 submissions, accepting only 162 due to venue constraints. Conferences (50-minute slots) saw 320 proposals, with 74 accepted; 14 allocated to premium sponsors, leaving 60 for general selection – an 82% rejection rate.
A 10-person team, including volunteers, rigorously evaluated submissions, using notes (0-5 scale), discussions, pizzas, and color-coded Post-its. Goncalves humorously notes resorting to a cat for ties, underscoring the process’s seriousness despite challenges. Rejected speakers are encouraged to reapply or present at local JUGs, emphasizing inclusivity.
The keynote theme – past, present, future – features speakers like Clarisse Herrenschmidt on writing history, Martin Odersky on objects and functionals, Alexis Moussine-Pouchkine on Java’s trajectory, and Habib Guergachi on web architectures. Odersky’s evening BoF is noted for Scala enthusiasts.
Special Initiatives and Community Engagement
Unique events differentiate Devoxx: “Devoxx for Kids,” led by Audrey Neveux, introduced 70 children to programming via robots the previous day, aiming to demystify parents’ professions. Though not repeatable annually due to school changes, it inspires future iterations alongside Belgium’s multilingual versions.
“Open Source Hacking” with Brice Dutheil and Mathieu Ancelin offers hands-on contribution. The “Afternoon for Decision-Makers,” from 14:00-18:15, mixes genres with CIOs discussing cloud, prepared by Arnaud Héritier. Reserved seats accommodate hard-to-book executives, but it’s open to all.
“Code Story,” by David Gageot and Jean-Laurent de Morlhon, features full-day live coding in a basement room. “Mercenaries of DevOps,” with Pierre-Antoine Grisoni, Henry Gomez, and others, explores native packaging and Kanban boards the next day.
Sponsors receive gratitude: premium partners enable affordable tickets; Oxiane handles training for over half attendees, managing complex dossiers. Medium and base sponsors filled slots quickly, with full exhibition halls praised for embodying Devoxx spirit.
In summation, the keynote reinforces Devoxx as a collaborative hub, blending education, networking, and innovation to advance the Java community and beyond.
Relevant Links and Hashtags
Links:
[DevoxxFR2013] Web Oriented Architecture: A Transmutation of Practices in Building Information Systems
Lecturer
Habib Guergachi is a Centrale graduate and the CEO and co-founder of Zenexity, established in 2003. As an expert in urbanization, he is among the French architects who introduced key concepts such as the “integrability coefficient” of applications. His professional background includes over seven years at the Central IT Department of AXA, more than three years at the IT Strategy Department of Société Générale, and five years on the executive committee and Technical Direction of a major IT services company. Currently, he leads large-scale urbanization projects and transformations of information systems toward web-oriented models. He also conducts seminars at the prestigious Capgemini Institute.
Abstract
This article explores Habib Guergachi’s lecture on Web Oriented Architecture (WOA), which critiques traditional enterprise practices and advocates for a shift to distributed, hyper-scalable systems. Drawing from historical analogies and real-world examples like LinkedIn, Guergachi argues for abandoning monolithic architectures in favor of independent, reactive applications that leverage modern web protocols. The discussion analyzes the implications for software development, emphasizing innovation, scalability, and the rejection of outdated paradigms to ensure future competitiveness in the French and global IT landscape.
Contextualizing the Shift from Hyper-Integrated to Hyper-Distributed Systems
Guergachi begins by drawing a parallel between the decline of traditional industries, such as steel mills like Gandrange and Florange, and the potential obsolescence of current software engineering practices. He posits that modern IT specialists, akin to specialized workers in software factories, risk irrelevance if they fail to innovate. The core dilemma is the overemphasis on hyper-integrated systems, where enterprises purchase off-the-shelf software that imposes architectures dictated by vendors. This leads to rigid, costly structures that stifle adaptability.
In contrast, Guergachi introduces the concept of hyper-distributed architectures, inspired by web-oriented principles. He illustrates this with a cultural anecdote: a hypothetical Chinese viewer searching for a French film clip on ina.fr fails due to rigid, integrated search mechanisms, while Google succeeds through flexible, distributed intelligence. This highlights how integrated systems, often built around enterprise architecture, application servers, and service buses, create “bousins” – complex, unmaintainable assemblages of tools like CMS for content, transactional plugins, and adapters for legacy JSF applications.
The lecturer critiques the inefficiency of such systems, where decision-making processes involve dumping data into warehouses for analysis, rather than fostering real-time adaptability. He urges a generational shift: respecting past achievements that built foundational information systems but making way for younger developers to construct future-proof ones. Avoiding the trap of using ingenuity merely to bypass imposed integrations is crucial, as technological evolution accelerates.
Principles of Distributed Paradigms and Real-World Implementations
Central to Guergachi’s thesis is the advocacy for distributed paradigms over integrated ones. He references Play Framework, a French-origin technology (despite initial skepticism due to its nationality), as a tool for building independent applications. LinkedIn’s approach exemplifies this: constructing systems as separate components, each focused on core business logic, deployed autonomously. These might use various technologies but prioritize scalability, security, and reactivity.
In a distributed model, non-core functions like search are outsourced to specialized services, allowing internal applications to remain focused and resilient under load. Guergachi explains techniques such as eventual consistency for high-load scenarios and strict consistency only where necessary, like payment processing. Communication between applications relies on RESTful hypermedia over HTTP, rejecting heavy RPC protocols or plugins like Flash, which he derides as symptomatic of a “third-world syndrome” – adopting external technologies without deep understanding.
He envisions enterprises concentrating solely on core business, externalizing storage, CMS, back-office, and video management to superior providers. Performance concerns with HTTP are dismissed as psychological barriers; no in-house solution can compete with storage specialists. Applications will interconnect in a “spaghetti” manner, but one that ensures predictability and adaptability, mirroring the web’s organic structure.
Guergachi introduces entropy as a metaphor: solid (rigid, controlled architectures), liquid (flexible, scalable across servers), and gaseous (pervasive, occupying value chain interstices like Google). Enterprises must evolve toward gaseous states for survival, contrasting with legacy systems that “suck blood” through perpetual maintenance fees.
Implications for Innovation and the Role of French IT Genius
The lecturer delineates integrated paradigms – building overarching technical architectures without functional hypotheses, aiming for longevity – as flawed, akin to overpacking for unforeseen disasters. Distributed paradigms, conversely, tailor architectures per application, prioritizing functional solutions over technical absolutes. For instance, displaying cached content during network failures ensures usability, decided by business logic rather than rigid transactional rules.
A paradigm, per Guergachi, is a coherent worldview offering solutions to its own problems. He warns against half-measures, like deploying advanced frameworks on outdated servers, urging full commitment to distributed models despite risks like dismissal. Submitting to vendor-driven technologies prepares for shameful obsolescence, whereas bold shifts enable glory through innovation.
Critiquing entities like INPI’s outdated systems, he highlights France’s image issues, comparable to 1980s Korean cars. French IT genius, exemplified by talents like Guillaume Bort and Sadek Drobi, must harness business acumen. Concepts like Scalaz originated in France (at Camel), underscoring untapped potential.
The economy of the web remains to be fully realized; Silicon Valley leads but hasn’t won. French informatics must act through innovation serving functionality, user experience, and distributed architectures with increasing entropy. Mastering interconnection complexity yields value, constructing planetary software masterpieces to safeguard jobs and elevate France.
In conclusion, Guergachi’s call to action – rebooting mindsets Monday morning – emphasizes radical change for continuity. By embracing WOA, developers transcend traditional constraints, fostering systems that are open, secure, adaptable, and cost-effective, aligning with business evolutions.
Relevant Links and Hashtags
Links:
[DevoxxBE2012] 7 Things: How to Make Good Teams Great
Sven Peters, an Atlassian ambassador with over a decade in Java EE development and team leadership, shared strategies for elevating competent teams to exceptional levels. Sven, passionate about clean code and developer motivation, drew from Atlassian’s experiences to outline seven practices fostering innovation and productivity while sustaining focus on quality products.
He opened by challenging assumptions about agile methodologies, observing that some self-proclaimed agile teams underperform, while certain traditional ones excel. Sven emphasized that true greatness transcends labels, requiring deliberate actions to boost morale and efficiency.
Atlassian, known for tools like Jira and Confluence, exemplifies these principles through an open culture that values feedback and experimentation. Sven warned that while inspiring, these methods must adapt to individual contexts, with readiness to iterate based on outcomes.
Enhancing Focus and Flow
Sven advocated protecting developers’ concentration, introducing “do not disturb” periods where interruptions halt, allowing deep work. At Atlassian, engineers signal availability with signs, reducing context switches that hinder productivity.
He stressed feeding intellectual curiosity via learning opportunities, such as internal talks or external conferences. These sessions, often during lunch, cover diverse topics, sparking ideas and cross-team collaboration.
Appreciating efforts, even minor ones, builds positivity. Sven described Atlassian’s kudos system, where peers publicly recognize contributions, reinforcing a supportive environment.
Automating Insights and User Empathy
To streamline oversight, Sven recommended automated reports aggregating metrics like code commits and bug fixes. These dashboards provide quick overviews without manual effort, freeing time for creative tasks.
“Dogfooding”—using one’s own products internally—bridges gaps between creators and users. At Atlassian, this uncovers issues early, fostering empathy and better designs. Sven shared how it led to improvements in their tools.
Sparking Innovation Through Dedicated Time
Special days, like “ShipIt” events, tackle backlog items in focused bursts. Atlassian’s 24-hour hackathons encourage wild ideas, with voting and implementation for winners, injecting fun and progress.
Experimentation time, such as 20% personal projects, drives breakthroughs. Sven recounted how this birthed features like Jira’s rapid boards, enhancing products while empowering staff.
He rated these practices’ feasibility and impact, urging measured trials to gauge effectiveness.
Adapting and Measuring Success
Sven concluded by encouraging experimentation, acknowledging failures as learning opportunities. Atlassian’s disbanded innovation team taught that distributed creativity works better.
He advised time-boxing initiatives, tracking results, and customizing approaches. Being distinctive in practices attracts and retains talent in a competitive field.
Sven’s insights, rooted in real-world application, offer a blueprint for transforming solid teams into outstanding ones through intentional, adaptive strategies.