Archive for the ‘en-US’ Category
[KotlinConf2017] Cords & Gumballs
Lecturer
Mike Hearn is the lead platform engineer at R3, a consortium of leading financial institutions developing Corda, a blockchain-inspired distributed ledger platform implemented in Kotlin. With nearly eight years at Google as a senior software engineer and five years as a Bitcoin developer, Mike brings extensive experience in JVM-based development and distributed systems. His early adoption of Kotlin, 18 months before its 1.0 release, and his work on the open-source BitcoinJ library, used in products with millions of users, highlight his expertise in high-performance, scalable software solutions.
Abstract
Kotlin’s versatility enables both large-scale enterprise projects and lightweight command-line tools. This article analyzes Mike Hearn’s presentation at KotlinConf 2017, which explores two contrasting projects: Corda, a blockchain-inspired platform for financial institutions, and Gumballs, a tool for generating standalone native binaries from Kotlin/JVM code. The analysis examines the context of Kotlin’s adoption in enterprise and lightweight applications, the methodologies behind Corda and Gumballs, their technical innovations, and their implications for software development. Mike’s insights highlight Kotlin’s ability to address diverse use cases, from secure financial systems to efficient command-line utilities.
Context of Kotlin in Enterprise and Lightweight Applications
At KotlinConf 2017, Mike Hearn presented two distinct projects showcasing Kotlin’s flexibility. Corda, developed by R3, is a large-scale enterprise platform inspired by blockchain technology, designed to streamline financial transactions among banks. Implemented entirely in Kotlin, Corda leverages the language’s concise syntax and JVM compatibility to handle complex business logic securely. In contrast, Gumballs is a side project that compiles Kotlin/JVM code into standalone native binaries, competing with Go’s efficiency for command-line tools. This dual focus reflects Kotlin’s ability to cater to both enterprise-scale systems and lightweight, performance-critical applications.
The context of Corda’s development highlights Kotlin’s appeal for enterprise use. Mike, an early Kotlin adopter, chose the language for its compatibility with the JVM, which is well-suited for high-level business logic in financial systems. The decision to avoid web technologies like TornadoFX, due to security concerns, underscores Corda’s emphasis on robust, desktop-based applications. Gumballs, conversely, addresses the need for efficient, standalone tools, demonstrating Kotlin’s potential to rival Go in scenarios requiring minimal dependencies and fast execution.
Methodology of Corda and Gumballs
Corda’s methodology centers on leveraging Kotlin’s features to build a secure, scalable distributed ledger. Mike explained that Corda uses Kotlin’s type safety and concise syntax to implement complex financial workflows, such as peer-to-peer real-time gross settlement systems. The platform employs cryptographic identities for nodes, ensuring stronger security than traditional systems reliant on identifiers like social security numbers. Kotlin’s interoperability with the JVM allows Corda to integrate with existing financial infrastructure, while its open-source nature, with tutorials and sample apps, encourages developer adoption.
Gumballs, in contrast, focuses on generating ahead-of-time compiled native binaries from Kotlin/JVM code. Mike demonstrated how Gumballs produces lightweight executables, similar to Go’s output, by compiling Kotlin code into native binaries that run without a JVM. This approach minimizes dependencies, making it ideal for command-line utilities requiring fast startup and execution. The methodology leverages Kotlin’s compiler capabilities, showcasing its flexibility beyond traditional JVM applications and highlighting its potential for cross-platform, performance-critical tasks.
Technical Innovations and Challenges
Corda’s technical innovations include its use of Kotlin to manage complex state and transaction logic in a distributed environment. Mike highlighted how Kotlin’s concise syntax reduces boilerplate, enabling developers to focus on business logic rather than infrastructure. The platform’s participation in a competition with the Central Bank of Singapore to develop a settlement system demonstrated its ability to handle real-world financial challenges. However, challenges like ensuring security in distributed systems required banning less secure web technologies, favoring managed desktop apps for structural integrity.
Gumballs introduces a novel approach to Kotlin compilation, producing standalone binaries that compete with Go’s efficiency. This innovation addresses the need for lightweight tools in scenarios where JVM overhead is impractical. Challenges included optimizing the compilation process to minimize binary size and ensure compatibility across platforms. Mike’s presentation emphasized the experimental nature of Gumballs, inviting community feedback to refine its capabilities, reflecting the iterative approach to developing new Kotlin tools.
Implications for Software Development
Corda and Gumballs demonstrate Kotlin’s versatility across the spectrum of software development. Corda’s adoption by a consortium of banks underscores Kotlin’s suitability for enterprise applications requiring security, scalability, and interoperability. Its open-source model, supported by tutorials and sample apps, lowers the barrier to entry for developers building financial systems. Gumballs, meanwhile, expands Kotlin’s reach into lightweight, performance-critical applications, offering an alternative to languages like Go for command-line tools and utilities.
For developers, these projects highlight Kotlin’s ability to unify diverse development needs within a single language. Corda’s success in enterprise settings encourages adoption in industries requiring robust, secure systems, while Gumballs appeals to developers seeking efficient, standalone solutions. The broader implication is Kotlin’s potential to challenge established languages in both enterprise and niche domains, fostering a more cohesive development ecosystem. Mike’s call for community contributions via Corda’s open-source platform and Gumballs’ experimental development further amplifies Kotlin’s collaborative potential.
Conclusion
Mike Hearn’s presentation at KotlinConf 2017 showcased Kotlin’s remarkable adaptability through Corda and Gumballs. Corda’s enterprise-grade blockchain platform demonstrates Kotlin’s strength in handling complex, secure financial systems, while Gumballs highlights its potential for lightweight, high-performance tools. By leveraging Kotlin’s type safety, JVM compatibility, and concise syntax, both projects address distinct challenges, from distributed ledgers to native binaries. As Kotlin continues to evolve, Mike’s insights underscore its transformative role in software development, inspiring developers to explore its capabilities across diverse domains.
Links
[DotSecurity2017] The Digital Battle
In the digital domain’s relentless ruckus, where innovation’s influx intersects with iniquity’s ingenuity, safeguarding society’s sinews demands diligence beyond devices. Mikko Hypponen, F-Secure’s chief research officer, surveyed this skirmish at dotSecurity 2017, chronicling connectivity’s costs—from Nokia’s nadir to IoT’s insurgency. A Finnish fixture in antivirus annals since 1991, Mikko’s métier—malware’s myriad manifestations—manifests in missives that marry menace with mitigation, urging unity against ubiquitous threats.
Mikko’s meditation meandered through time: 2007’s iPhone ingress, internet’s ingress into pockets—privacy’s payment in profiles. Youth’s yen: videos’ vista via Google’s gaze, data’s donation. Privacy’s plight: perhaps perished, yet security’s skirmish salvageable—society’s stake superseding screens. Criminality’s calculus: crime’s commoditization, ransomware’s rise—CryptoWall’s coffers crammed $325M, victims’ vigil via NoMoreRansom’s nexus.
IoT’s incursion: Mirai’s maelstrom, 600,000 conscripts cascading DDoS—Dyn’s downfall, Krebs’ knockout. Mikko’s maxim: defaults’ delinquency, patches’ paucity—devices’ disposability dooms defense. Refrigerators’ reconnaissance, lamps’ liabilities—cloud’s collapse cascades chaos, AWS’s outage orphaning ovens.
Hope’s harbinger: IKEA’s integrity, investment’s imperative—security’s sanctity secures society.
Innovation’s Influx and Privacy’s Peril
Mikko mapped metamorphosis: Nokia’s nosedive, iPhone’s incursion—privacy’s price, data’s dues.
Malware’s Myriad and IoT’s Insurgency
Ransomware’s ransom, Mirai’s muster—Dyn’s deluge, defaults’ danger. Cloud’s crumble, chaos cascades.
Links:
[DevoxxFR 2017] Introduction to the Philosophy of Artificial Intelligence
The rapid advancements and increasing integration of artificial intelligence into various aspects of our lives raise fundamental questions that extend beyond the purely technical realm into the domain of philosophy. As machines become capable of performing tasks that were once considered uniquely human, such as understanding language, recognizing patterns, and making decisions, we are prompted to reconsider our definitions of intelligence, consciousness, and even what it means to be human. At DevoxxFR 2017, Eric Lefevre Ardant and Sonia Ouchtar offered a thought-provoking introduction to the philosophy of artificial intelligence, exploring key concepts and thought experiments that challenge our understanding of machine intelligence and its potential implications.
Eric and Sonia began by acknowledging the pervasive presence of “AI” in contemporary discourse, noting that the term is often used broadly to encompass everything from simple algorithms to hypothetical future superintelligence. They stressed the importance of developing a critical perspective on these discussions and acquiring the vocabulary necessary to engage with the deeper philosophical questions surrounding AI. Their talk aimed to move beyond the hype and delve into the core questions that philosophers have grappled with as the possibility of machine intelligence has become more concrete.
The Turing Test: A Criterion for Machine Intelligence?
A central focus of the presentation was the Turing Test, proposed by Alan Turing in 1950 as a way to determine if a machine can exhibit intelligent behavior equivalent to, or indistinguishable from, that of a human. Eric and Sonia explained the setup of the test, which involves a human interrogator interacting with both a human and a machine through text-based conversations. If the interrogator cannot reliably distinguish the machine from the human after a series of conversations, the machine is said to have passed the Turing Test.
They discussed the principles behind the test, highlighting that it focuses on observable behavior (linguistic communication) rather than the internal workings of the machine. The Turing Test has been influential but also widely debated. Eric and Sonia presented some of the key criticisms of the test, such as the argument that simulating intelligent conversation does not necessarily imply true understanding or consciousness.
The Chinese Room Argument: Challenging the Turing Test
To further explore the limitations of the Turing Test and the complexities of defining machine intelligence, Eric and Sonia introduced John Searle’s Chinese Room argument, a famous thought experiment proposed in 1980. They described the scenario: a person who does not understand Chinese is locked in a room with a large set of Chinese symbols, a rulebook in English for manipulating these symbols, and incoming batches of Chinese symbols (representing questions). By following the rules in the rulebook, the person can produce outgoing batches of Chinese symbols (representing answers) that are appropriate responses to the incoming questions, making it appear to an outside observer that the person understands Chinese.
Sonia and Eric explained that Searle’s argument is that even if the person in the room can pass the Turing Test for understanding Chinese (by producing seemingly intelligent responses), they do not actually understand Chinese. They are simply manipulating symbols according to rules, without any genuine semantic understanding. The Chinese Room argument is a direct challenge to the idea that passing the Turing Test is a sufficient criterion for claiming a machine possesses true intelligence or understanding. It raises profound questions about the nature of understanding, consciousness, and whether symbolic manipulation alone can give rise to genuine cognitive states.
The talk concluded by emphasizing that the philosophy of AI is a fertile and ongoing area of inquiry with deep connections to various other disciplines, including neuroscience, psychology, linguistics, and computer science. Eric and Sonia encouraged attendees to continue exploring these philosophical questions, recognizing that understanding the fundamental nature of intelligence, both human and artificial, is crucial as we continue to develop increasingly capable machines. The session provided a valuable framework for critically evaluating claims about AI and engaging with the ethical and philosophical implications of artificial intelligence.
Links:
- Video URL: https://www.youtube.com/watch?v=pDPFnywbWDo
Hashtags: #AI #ArtificialIntelligence #Philosophy #TuringTest #ChineseRoom #MachineIntelligence #Consciousness #EricLefevreArdant #SoniaOUCHTAR #PhilosophyOfAI
[ScalaDaysNewYork2016] Finagle Under the Hood: Unraveling Twitter’s RPC System
At Scala Days New York 2016, Vladimir Kostyukov, a member of Twitter’s Finagle team, provided an in-depth exploration of Finagle, a scalable and extensible RPC system written in Scala. Vladimir elucidated how Finagle simplifies the complexities of distributed systems, offering a functional programming model that enhances developer productivity while managing intricate backend operations like load balancing and circuit breaking.
The Essence of Finagle
Vladimir Kostyukov introduced Finagle as a robust RPC system used extensively at Twitter and other organizations. Unlike traditional application frameworks, Finagle focuses on facilitating communication between services, abstracting complexities such as connection pooling and load balancing. Vladimir highlighted its protocol-agnostic nature, supporting protocols like HTTP/2 and Twitter’s custom Mux, which enables efficient multiplexing. This flexibility allows developers to build services in Scala or Java, seamlessly integrating Finagle into diverse tech stacks.
Client-Server Dynamics
Delving into Finagle’s internals, Vladimir described its client-server model, where services are treated as composable functions. When a client sends a request, Finagle’s stack—comprising modules for connection pooling, load balancing, and failure handling—processes it efficiently. On the server side, incoming requests are routed through similar modules, ensuring resilience and scalability. Vladimir emphasized the “power of two choices” load balancing algorithm, which selects the least-loaded node from two randomly chosen servers, achieving near-optimal load distribution in constant time.
Advanced Features and Ecosystem
Vladimir showcased Finagle’s advanced capabilities, such as streaming support for large payloads and integration with tools like Zipkin for tracing and Twitter Server for monitoring. Libraries like Finatra and Featherbed further enhance Finagle’s utility, enabling developers to build RESTful APIs and type-safe HTTP clients. These features make Finagle a powerful choice for handling high-throughput systems, as demonstrated by its widespread adoption at Twitter for managing massive data flows.
Community and Future Prospects
Encouraging community engagement, Vladimir invited developers to contribute to Finagle’s open-source repository on GitHub. He discussed ongoing efforts to support HTTP/2 and improve performance, underscoring Finagle’s evolution toward a utopian RPC system. By offering a welcoming environment for pull requests and feedback, Vladimir emphasized the collaborative spirit driving Finagle’s development, ensuring it remains a cornerstone of scalable service architectures.
Links:
[DotSecurity2017] Verifiable Lotteries
In realms where randomness reigns—visas’ vagaries, audits’ allocations, tournaments’ tabulations—authorities’ assertions of equity often echo empty, bereft of corroboration. Joseph Bonneau, a cryptographer and researcher at Stanford’s Applied Crypto Group, demystified this domain at dotSecurity 2017, championing verifiable randomness as algorithmic accountability’s anchor. Formerly of Google and the Electronic Frontier Foundation, Joseph’s journey—Bitcoin’s blockchain to privacy’s precincts—culminates in constructs that compel proof from the capricious, from dice’s clatter to cryptographic commitments.
Joseph’s journey juxtaposed physical proofs’ pitfalls: lottery balls’ bias, dice’s deceit—transparency’s theater, yet tampering’s temptation. Cryptography’s counter: commitments’ covenant—hash’s hideaway, revealing randomness post-participation. Verifiable delay functions (VDFs) vex velocity: computations’ chronology, proofs’ promptness—adversaries’ acceleration averted. Joseph’s jewel: lottery’s ledger—participants’ pledges, commitments’ concatenation, hash’s harvest yielding winners’ wreath.
Applications amplify: H1B visas’ vagaries verified, elections’ audits authenticated—overbooked flights’ farewells fair. Joseph’s jibe: FIFA’s football fiascoes, fans’ fury—verifiability’s vindication. Blockchain’s boon: Bitcoin’s beacons, stock quotes’ surrogates—delay’s defense against traders’ tempo.
Challenges chime: VDFs’ verification velocity, parallelism’s peril—research’s realm ripe. Joseph’s rallying cry: demand documentation—dashlane’s draws, FIFA’s fixtures, governments’ gambits—cryptography’s capability calls.
Randomness’ Riddles and Physical Pitfalls
Joseph juxtaposed balls’ bias, dice’s deceit—commitments’ cure, delay’s deterrent.
Constructs’ Craft and Applications’ Ambit
Hash’s haven, VDFs’ vigil—lotteries’ ledger, visas’ verity. Blockchain’s bastion, stocks’ surrogate.
Links:
[DevoxxUS2017] Java EE 8: Adapting to Cloud and Microservices
At DevoxxUS2017, Linda De Michiel, a pivotal figure in the Java EE architecture team and Specification Lead for the Java EE Platform at Oracle, delivered a comprehensive overview of Java EE 8’s development. With her extensive experience since 1997, Linda highlighted the platform’s evolution to embrace cloud computing and microservices, aligning with modern industry trends. Her presentation detailed updates to existing Java Specification Requests (JSRs) and introduced new ones, while also previewing plans for Java EE 9. This post explores the key themes of Linda’s talk, emphasizing Java EE 8’s role in modern enterprise development.
Evolution from Java EE 7
Linda began by reflecting on Java EE 7, which focused on HTML5 support, modernized web-tier APIs, and simplified development through Context and Dependency Injection (CDI). Building on this foundation, Java EE 8 shifts toward cloud-native and microservices architectures. Linda noted that emerging trends, such as containerized deployments and distributed systems, influenced the platform’s direction. By enhancing CDI and introducing new APIs, Java EE 8 aims to streamline development for scalable, cloud-based applications, ensuring developers can build robust systems that meet contemporary demands.
Enhancements to Core JSRs
A significant portion of Linda’s talk focused on updates to existing JSRs, including CDI 2.0, JSON Binding (JSON-B), JSON Processing (JSON-P), and JAX-RS. She announced that CDI 2.0 had unanimously passed its public review ballot, a milestone for the expert group. JSON-B and JSON-P, crucial for data interchange in modern applications, have reached proposed final draft stages, while JAX-RS enhances RESTful services with reactive programming support. Linda highlighted the open-source nature of these implementations, such as GlassFish and Jersey, encouraging community contributions to refine these APIs for enterprise use.
New APIs for Modern Challenges
Java EE 8 introduces new JSRs to address cloud and microservices requirements, notably the Security API. Linda discussed its early draft review, which aims to standardize authentication and authorization across distributed systems. Servlet and JSF updates are also progressing, with JSF nearing final release. These APIs enable developers to build secure, scalable applications suited for microservices architectures. Linda emphasized the platform’s aggressive timeline for a summer release, underscoring the community’s commitment to delivering production-ready solutions that align with industry shifts toward cloud and container technologies.
Community Engagement and Future Directions
Linda stressed the importance of community feedback, directing developers to the Java EE specification project on java.net for JSR details and user groups. She highlighted the Adopt-a-JSR program, led by advocates like Heather VanCura, as a channel for aggregating feedback to expert groups. Looking ahead, Linda briefly outlined Java EE 9’s focus on further cloud integration and modularity. By inviting contributions through open-source platforms like GlassFish, Linda encouraged developers to shape the platform’s future, ensuring Java EE remains relevant in a rapidly evolving technological landscape.
Links:
[DevoxxUS2017] Eclipse OMR: A Modern, Open-Source Toolkit for Building Language Runtimes by Daryl Maier
At DevoxxUS2017, Daryl Maier, a Senior Software Developer at IBM, introduced Eclipse OMR, an open-source toolkit for building high-performance language runtimes. With two decades of experience in compiler development, Daryl shared how OMR repurposes components of IBM’s J9 Java Virtual Machine to support diverse dynamic languages without imposing Java semantics. His session highlighted OMR’s potential to democratize runtime technology, fostering innovation across language ecosystems. This post explores the core themes of Daryl’s presentation, emphasizing OMR’s role in advancing runtime development.
Unlocking JVM Technology with OMR
Daryl Maier opened by detailing the Eclipse OMR project, which extracts core components of the J9 JVM, such as its compiler and garbage collector, for broader use. Unlike building languages atop Java, OMR provides modular, high-performance tools for creating custom runtimes. Daryl’s examples showcased OMR’s flexibility in supporting languages beyond Java, drawing from his work at IBM’s Canada Lab to illustrate its potential for diverse applications.
Compiler and Runtime Innovations
Transitioning to technical specifics, Daryl explored OMR’s compiler technology, designed for just-in-time (JIT) compilation in dynamic environments. He contrasted OMR with LLVM, noting its lightweight footprint and optimization for runtime performance. Daryl highlighted OMR’s garbage collection and code generation capabilities, which enable efficient, scalable runtimes. His insights underscored OMR’s suitability for dynamic languages, offering developers robust tools without the overhead of traditional compilers.
Active Development and Use Cases
Daryl discussed active OMR projects, including integrations with existing runtimes to enhance debuggability and performance. He referenced a colleague’s upcoming demo on OMR’s tooling interfaces, illustrating practical applications. Drawing from IBM’s extensive runtime expertise, Daryl showcased how OMR supports innovative use cases, from scripting languages to domain-specific runtimes, encouraging developers to leverage its modular architecture.
Engaging the Developer Community
Concluding, Daryl invited developers to contribute to Eclipse OMR, emphasizing its open-source ethos. He highlighted collaboration opportunities, noting contact points with project co-leads Mark and Charlie. Daryl’s call to action, rooted in IBM’s commitment to open-source innovation, encouraged attendees to explore OMR’s GitHub repository and participate in shaping the future of language runtimes.
Links:
[KotlinConf2017] How to Build a React App in Kotlin
Lecturer
Dave Ford is an independent software developer and trainer with extensive experience in JVM-based languages and JavaScript. Having worked with both technologies since their inception, Dave brings a deep understanding of cross-platform development. His recent project of porting a React application to Kotlin showcases his expertise in leveraging Kotlin’s JavaScript interoperability and type-safe features. As a trainer, Dave is dedicated to sharing practical insights, helping developers navigate modern frameworks and tools to build robust web applications.
Abstract
The integration of Kotlin with React offers a powerful approach to web development, combining Kotlin’s type-safe, concise syntax with React’s component-based architecture. This article analyzes Dave Ford’s presentation at KotlinConf 2017, which explores building a React application using Kotlin/JS. It examines the context of Kotlin’s JavaScript interoperability, the methodology for creating type-safe React components, the use of Kotlin’s DSL capabilities, and the challenges encountered. The analysis highlights the implications of this approach for web developers, emphasizing productivity gains and the potential to streamline front-end development within the Kotlin ecosystem.
Context of Kotlin and React Integration
At KotlinConf 2017, Dave Ford addressed the growing interest in using Kotlin for web development, particularly through its JavaScript compilation capabilities. Kotlin/JS allows developers to write type-safe code that compiles to JavaScript, enabling integration with popular frameworks like React. Dave’s presentation, informed by his experience porting a React app to Kotlin, targeted an audience familiar with Kotlin but largely new to Kotlin/JS and React. The context of the presentation reflects the increasing demand for modern, type-safe alternatives to JavaScript, which often suffers from runtime errors and complex tooling.
React, a widely-used JavaScript library, excels in building dynamic, component-based web interfaces. However, its reliance on JavaScript’s dynamic typing can lead to errors that Kotlin’s static type system mitigates. Dave’s talk aimed to bridge these ecosystems, demonstrating how Kotlin’s interoperability with JavaScript and its IDE support, particularly through JetBrains’ tools, enhances developer productivity. The presentation’s live coding approach provided practical insights, making the integration accessible to developers seeking to leverage Kotlin’s strengths in front-end development.
Methodology for Type-Safe React Components
Dave’s methodology centered on using Kotlin’s JavaScript interop features to create type-safe React components. He demonstrated how Kotlin/JS interfaces with React’s APIs, allowing developers to define components with compile-time type checking. This approach reduces runtime errors common in JavaScript-based React development. By leveraging Kotlin’s type system, developers can ensure that props and state are correctly typed, improving code reliability and maintainability.
A key innovation was the use of Kotlin’s DSL capabilities to simplify React programming. Dave showcased how Kotlin’s type-safe builders create a declarative syntax for component hierarchies, making code more readable and concise compared to JavaScript’s verbose patterns. For example, he implemented a game application, passing event handlers (e.g., deal, hit, stay) through components to manage state changes. This approach, using lambda expressions and anonymous objects, allowed asynchronous state updates in a React-like manner, demonstrating Kotlin’s ability to streamline complex front-end logic.
Challenges and Lessons Learned
Porting a React app to Kotlin presented several challenges, which Dave candidly shared. One significant obstacle was managing state in a React application without direct access to game state from child components. To address this, Dave passed event handlers from parent to child components, a common React pattern, but implemented them using Kotlin’s type-safe constructs. This required defining interfaces for event handlers and overriding functions to update state asynchronously, highlighting the need for careful design to maintain React’s unidirectional data flow.
Another challenge was the learning curve for developers new to Kotlin/JS. Dave noted that while Kotlin’s IDE support simplifies development, familiarity with React’s ecosystem and JavaScript tooling (e.g., Create React App) is necessary. His live demo encountered minor issues, such as the need to refresh the application, underscoring the importance of robust tooling integration. These lessons emphasized the value of Kotlin’s type safety and IDE support in overcoming JavaScript’s limitations, while also highlighting areas for improvement in Kotlin/JS workflows.
Implications for Web Development
The integration of Kotlin and React, as demonstrated by Dave, has significant implications for web development. By combining Kotlin’s type safety with React’s component model, developers can create robust, maintainable web applications with fewer runtime errors. The use of DSLs enhances productivity, allowing developers to write concise, expressive code that aligns with React’s declarative paradigm. This approach is particularly valuable for teams transitioning from JVM-based Kotlin (e.g., Android or server-side) to web development, as it leverages familiar syntax and tools.
For the broader ecosystem, Kotlin/JS expands Kotlin’s reach beyond traditional JVM applications, challenging JavaScript’s dominance in front-end development. The ability to compile to JavaScript while maintaining type safety positions Kotlin as a compelling alternative for building modern web applications. Dave’s emphasis on community engagement, encouraging developers to explore Kotlin/JS, suggests a growing ecosystem that could influence web development practices, particularly for projects requiring high reliability and scalability.
Conclusion
Dave Ford’s presentation at KotlinConf 2017 illuminated the potential of Kotlin/JS to transform React-based web development. By leveraging type-safe components and DSL capabilities, Kotlin offers a productive, reliable alternative to JavaScript, addressing common pain points in front-end development. Despite challenges like state management and tooling integration, the approach demonstrates significant promise for developers seeking to unify their Kotlin expertise across platforms. As Kotlin/JS matures, its impact on web development is likely to grow, fostering a more robust and developer-friendly ecosystem.
Links
[DevoxxUS2017] Eclipse Che by Tyler Jewell
At DevoxxUS2017, Tyler Jewell, CEO of Codenvy and project lead for Eclipse Che, delivered a compelling session on the shift from localhost to cloud-based development. Highlighting Eclipse Che as a next-generation IDE and workspace server, Tyler discussed how it streamlines team collaboration and agile workflows. With contributions from industry leaders like Red Hat and Microsoft, Che has rapidly gained traction. This post explores the key themes of Tyler’s presentation, focusing on the future of cloud development.
The Rise of Cloud Development
Tyler Jewell began by outlining market forces driving the adoption of cloud development, such as the need for rapid onboarding and consistent environments. He contrasted traditional localhost setups with cloud-based workflows, emphasizing how Eclipse Che enables one-click environment creation. Tyler’s insights, drawn from his role at Codenvy, highlighted Che’s ability to reduce setup time, allowing teams to focus on coding rather than configuration.
Eclipse Che’s Workspace Innovation
Delving into technical details, Tyler showcased Che’s workspace server, which supports reproducible environments through containerized runtimes. Unlike Vagrant VMs, Che workspaces offer lightweight, scalable solutions, integrating seamlessly with Docker. He demonstrated how Che’s architecture supports distributed teams, enabling collaboration across geographies. Tyler’s live demo illustrated creating and managing workspaces, underscoring Che’s role in modernizing development pipelines.
Community Contributions and Roadmap
Tyler emphasized the vibrant Eclipse Che community, with nearly 100 contributors from companies like IBM and Samsung. He discussed ongoing efforts to enhance language server integration, citing the Language Server Protocol’s potential for dynamic tool installation. Tyler shared Che’s roadmap, focusing on distributed workspaces and team-centric features, inviting developers to contribute to its open-source ecosystem.
Balancing IT Control and Developer Freedom
Concluding, Tyler addressed the tension between IT control and developer autonomy, noting how Che balances root access with governance. He highlighted its integration with agile methodologies, enabling faster iterations and improved collaboration. Tyler’s vision for Che, rooted in his experience at Toba Capital, positioned it as a transformative platform for cloud-native development, encouraging attendees to explore its capabilities.
Links:
[DevoxxFR] How to be a Tech Lead in an XXL Pizza Team Without Drowning
The role of a Tech Lead is multifaceted, requiring a blend of technical expertise, mentorship, and facilitation skills. However, these responsibilities become significantly more challenging when leading a large team, humorously dubbed an “XXL pizza team,” potentially comprising fifteen or more individuals, with a substantial number of developers. Damien Beaufils shared his valuable one-year retrospective on navigating this complex role within such a large and diverse team, offering practical insights on how to effectively lead, continue contributing technically, and avoid being overwhelmed.
Damien’s experience was rooted in leading a team working on a public-facing website, notable for its heterogeneity. The team was mixed in terms of skill sets, gender, and composition (combining client and vendor personnel), adding layers of complexity to the leadership challenge.
Balancing Technical Contribution and Leadership
A key tension for many Tech Leads is balancing hands-on coding with leadership duties. Damien addressed this directly, emphasizing that while staying connected to the code is important for credibility and understanding, the primary focus must shift towards enabling the team. He detailed practices put in place to foster collective ownership of the codebase and enhance overall product quality. These included encouraging pair programming, implementing robust code review processes, and establishing clear coding standards.
The goal was to distribute technical knowledge and responsibility across the team rather than concentrating it solely with the Tech Lead. By empowering team members to take ownership and contribute to quality initiatives, Damien found that the team’s overall capability and autonomy increased, allowing him to focus more on strategic technical guidance and facilitation.
Fostering Learning, Progression, and Autonomy
Damien highlighted several successful strategies employed to promote learning, progression, and autonomy within the XXL team. These successes were not achieved by acting as a “super-hero” dictating solutions but through deliberate efforts to facilitate growth. Initiatives such as organizing internal workshops, encouraging knowledge sharing sessions, and providing opportunities for developers to explore new technologies contributed to a culture of continuous learning.
He stressed the importance of the Tech Lead acting as a coach, guiding individuals and the team towards self-improvement and problem-solving. By fostering an environment where team members felt empowered to make technical decisions and learn from both successes and failures, Damien helped build a more resilient and autonomous team. This shift from relying on a single point of technical expertise to distributing knowledge and capability was crucial for managing the scale and diversity of the team effectively.
Challenges and Lessons Learned
Damien was also candid about the problems encountered and the strategies that proved less effective. Leading a large, mixed team inevitably presents communication challenges, potential conflicts, and the difficulty of ensuring consistent application of standards. He discussed the importance of clear communication channels, active listening, and addressing issues proactively.
One crucial lesson learned was the need for clearly defined, measurable indicators to track progress in areas like code quality, team efficiency, and technical debt reduction. Without objective metrics, it’s challenging to assess the effectiveness of implemented practices and demonstrate improvement. Damien concluded that while there’s no magic formula for leading an XXL team, a pragmatic approach focused on empowering the team, fostering a culture of continuous improvement, and using data to inform decisions is essential for success without becoming overwhelmed.
Links:
- Damien Beaufils’s Twitter
- Damien Beaufils’s LinkedIn
- Video URL: https://www.youtube.com/watch?v=eEUfsjYj3rw
Hashtags: #TechLead #TeamManagement #SoftwareDevelopment #Leadership #DevOps #Agile #DamienBeaufils