# hybrid Published articles for hybrid. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Tailscale simplifies site-to-site VPN connections DevFeed: [How Tailscale simplifies site-to-site VPN connections]() Original publisher: [Read original article]() Published: 2025-09-23T17:57:09Z Content type: tutorial Language: en Sources: [Learn on Tailscale]() Topics: [Virtual Private Network](), [tailscale](), [networking](), [cloud-infrastructure](), [Security](), [Routing (disambiguation)]() Tags: [aws](), [azure](), [cloud-infrastructure](), [firewall](), [hybrid](), [networking](), [networks](), [tailscale](), [vpn]() ### AI overview This article explains how site-to-site VPNs securely connect separate offices, cloud environments, and on-premises networks. It compares traditional IPSec-based configurations with Tailscale's mesh networking and subnet routing approach. ### Source excerpt Learn how site-to-site VPNs connect offices and cloud networks securely. Compare traditional setups vs modern solutions that eliminate firewall configs and IP conflicts for good. ## Should you generate docs from your API schema? DevFeed: [Should you generate docs from your API schema?]() Original publisher: [Read original article]() Author: Emma Adler Published: 2025-05-16T00:00:00Z Content type: tutorial Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [OpenAPI Specification](), [API](), [Structured-data](), [Swagger](), [JSON](), [YAML]() Tags: [ai-trends](), [api](), [api-documentation](), [automate](), [automation](), [best-practices](), [hybrid](), [json](), [openapi](), [schemas](), [swagger]() ### AI overview This guide examines the benefits and limitations of generating API documentation from OpenAPI schemas. It explains how schema-based tools such as Swagger UI automatically create documentation from structured endpoint, method, data model, and response definitions, while noting that automation can leave gaps in user guidance and conceptual explanations. It recommends combining automation with customization. ### Source excerpt When your API constantly changes, how do you ensure your documentation keeps up? ## TLS 1.3 Hybrid Key Exchange using X25519Kyber768 / ML-KEM DevFeed: [TLS 1.3 Hybrid Key Exchange using X25519Kyber768 / ML-KEM]() Original publisher: [Read original article]() Published: 2024-11-01T00:30:36Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [TLS (Transport Layer Security)]() Tags: [hybrid](), [tls]() ### AI overview A brief practical description of TLS 1.3 hybrid key exchange using X25519Kyber768 and ML-KEM. ### Source excerpt A quick description of what a TLS 1.3 Hybrid Key Exchange using X25519Kyber768 / ML-KEM looks like in practice. ## Making the case for the WebView DevFeed: [Making the case for the WebView]() Original publisher: [Read original article]() Author: Campbell Graham Published: 2024-01-25T05:29:47Z Content type: opinion Language: en Sources: [Kogan.com]() Topics: [WebView](), [mobile-app-development](), [Mobile](), [User Experience]() Tags: [hybrid](), [mobile](), [mobile-app-development](), [user-experience](), [webview]() ### AI overview This opinion article argues that nested WebViews can be appropriate in hybrid mobile apps when teams must balance feature work, platform changes, maintenance, and parity with an accompanying website. It suggests evaluating criticality, interactivity, change frequency, content size, loading overhead, and native-development complexity, while keeping transitions seamless and preserving navigation and user state. ### Source excerpt Learning to embrace a hybrid approach for mobile app development: Native apps are best! Like the rest of the native mobile app development community, I typically agree with the notion that "native is best" when it comes to mobile apps. After all, these are the technologies we spend tens of hours every week utilising, and there is a passion for user experience that I feel is required in order to happily dive into the deep-end-specialisation of Google or Apple's tooling. An example of what is possible with Google's Material Design for Android: https://developer.android.com/design/ui?_gl=1*1g30ii5*_ga*MjA3NjQzNjE2NS4xNzAyOTQ0Nzc2*_ga_QPQ2NRV856*MTcwNjA2MTg0My44LjEuMTcwNjA2MTk2Ni4wLjAuMA.. However... As one of these oft-opinionated app developers who tends to view non-native tooling like React Native as a sub-par user experience, I have a potentially unpopular idea to share. Sometimes, a nested WebView does have its place. The pitch It might not be popular with the purists, but please hear me out. The nested WebView does sometimes have an important role to play (emphasis on nested!). When facing the challenge of balancing new features, requested enhancements, required platform changes and general maintenance, maintaining the required degree of parity between your mobile app and its accompanying website can be difficult. In my experience, here are some key factors to consider when deciding whether to implement a flow natively within your app or whether to utilise a nested WebView: Is it a critical piece of functionality that users will frequently use? To what degree is the content static or interactive? Will it be subject to frequent changes? How much content is there to display? Will the overhead of loading a WebView (including any relevant JavaScript) be fast enough for the use case? Do you feel any technical hurdles of developing it natively will result in a better user experience? There is no definitive flow chart that can help make this decision for you. However, wh ## How to create exceptional communication with mobile engineering teams DevFeed: [How to create exceptional communication with mobile engineering teams]() Original publisher: [Read original article]() Author: Sarah Gruneisen Published: 2023-08-21T09:19:33Z Content type: tutorial Language: en Sources: [Novoda]() Topics: [Mobile](), [mobile devops](), [Development](), [Architecture & Design]() Tags: [apps](), [communication](), [devops](), [distributed](), [how-to](), [hybrid](), [microservices](), [mobile-devops](), [mobile-engineering](), [monolith](), [native]() ### AI overview This article examines why mobile engineering teams become siloed, including organizational structures, remote and hybrid work, and the monolithic nature of mobile apps. It explains how Mobile DevOps can help bridge operational gaps and outlines principles for improving communication within mobile teams and across an organization. ### Source excerpt We explore the reasons why mobile teams get siloed, how Mobile DevOps aims to bridge the operational gap between teams, and the key principles of exceptional communication within mobile teams and organisations as a whole. The post How to create exceptional communication with mobile engineering teams appeared first on Novoda. ## How Skyscanner's all-day video call supports collaboration and knowledge sharing DevFeed: [How Skyscanner's all-day video call supports collaboration and knowledge sharing]() Original publisher: [Read original article]() Author: Skyscanner Engineering Published: 2023-08-09T12:34:59Z Content type: opinion Language: en Sources: [Stories by Skyscanner Engineering on Medium]() Topics: [Development](), [pair\_programming](), [Programming](), [meetings]() Tags: [collaboration](), [development](), [hybrid](), [knowledge-sharing](), [meetings](), [pair-programming](), [tech](), [virtual-office]() ### AI overview An employee describes how Skyscanner's hybrid team uses an all-day video call as a virtual office. The call helps colleagues across UK cities collaborate, share knowledge, support training, and participate in mob or pair programming. ### Source excerpt by Anthony Byledbal In the virtual office -- iStock Note: At Skyscanner, our teams work using a hybrid model. When not in the office, we want optimise our experience and keep close connection with our team members Video calls are usually meetings. An invitation is sent to participants and, on the scheduled day and time, all join for a limited period of time. However, in my team at Skyscanner, we as a team have decided to take a step further by introducing an all-day-long video call. The operating instructions are short: the first person to start its day, starts the call; the last person to finish, closes the call. This online tool has proven very successful with regards to employee collaboration, training enhancement, boosting morale and overall sense of engagement and positive team spirit. I was not used to working this way, but very quickly I have noticed the positive impact it had on me and my development. Before changing career from archaeology and moving to IT, I was unfamiliar with different kinds of online tools used in a working environment. I naively interpreted them as a poor management: I thought it was a way to track what me and my colleagues were doing. However, my experience in joining this call proved me wrong. Members of my squad created this online headquarter to connect their colleagues located across different cities around the United Kingdom in hope of improving communication, morale and collaboration within the team. A Shared Working Environment The call brings colleagues together. It is our virtual office where we feel less apart from each other. More importantly, this online space facilitates our daily work and knowledge sharing. It is good to see more experienced colleagues coding. Sharing screens is something our team does all day long, it immerses everyone into the code. From new joiners to senior engineers, everyone values this precious time because it allows us to ask questions and rise concerns. Most of the time, this provides us with an ## trivago Tech Week 2021 in Review DevFeed: [trivago Tech Week 2021 in Review]() Original publisher: [Read original article]() Author: Andreea Conciu-Ruse People person; Cat Lady; Project Manager @ trivago Linkedin profile Published: 2021-10-27T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Streaming](), [Twitch](), [zoom]() Tags: [community](), [engineering-culture](), [events](), [gaming](), [hybrid](), [music](), [streaming](), [talks](), [tech](), [twitch](), [virtual-event](), [zoom]() ### AI overview A review of trivago Tech Week 2021, a hybrid event featuring technical talks, exchange forums, guest speakers, gaming, and live music. The article describes how presentations and social activities were made available to both remote and on-campus participants. ### Source excerpt In the middle of summer 2021, we hosted one of our favourite annual events of the year - trivago Tech Week! This year's tech week had a new, hybrid format, featuring a wide variety of talks and ... ## Post-Mortem: Outbreak Database DevFeed: [Post-Mortem: Outbreak Database]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-03-03T05:00:00Z Content type: article Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [migration](), [Content Management System](), [PHP](), [Front end](), [Vue.js](), [GraphQL](), [axios](), [Website](), [Back end](), [API]() Tags: [aging](), [axios](), [cms](), [content](), [craft](), [custom](), [frontend](), [graphql](), [hybrid](), [management](), [migration](), [modernizing](), [php](), [post-mortem](), [post-mortems](), [twig-vue-js](), [vue](), [vuex](), [website]() ### AI overview A post-mortem on modernizing the aging custom PHP Outbreak Database website by migrating it to Craft CMS and planning a hybrid Twig/Vue.js frontend using Vuex, Axios, and GraphQL. The project aimed to improve content maintenance, researcher and journalist usability, and long-term technical foundations. ### Source excerpt Modernizing an aging custom PHP website with Craft CMS for content management, and a hybrid Twig/Vue.js + Vuex + Axios + GraphQL on the frontend ## Monstera: An Experiment in Using C++ and Object-Oriented Design for ReactOS's Memory Manager DevFeed: [Monstera: An Experiment in Using C++ and Object-Oriented Design for ReactOS's Memory Manager]() Original publisher: [Read original article]() Published: 2014-01-05T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [Kernel](), [C++](), [coding patterns](), [Development]() Tags: [c-plus-plus](), [coding-patterns](), [experiment](), [free](), [hybrid](), [kernel](), [object-oriented](), [open-source](), [os](), [procedural](), [react](), [reactos](), [win32](), [winapi]() ### AI overview Monstera is an experiment to assess whether C++ and selected object-oriented design principles can simplify development of ReactOS's predominantly procedural, C-centric memory manager. The post notes that kernel-code constraints limit which C++ features can be used, and that the experiment's success remains uncertain. ### Source excerpt This post really should have been made months ago, but finding the time to write a full blown newsletter has been getting more and more scarce. That being said, I've decided for the short term to split things that would normally act as a single newsletter section into separate blog posts so I don't need to wait and gather things. There was a lot of speculation as to what Monstera was when Aleksey made his commit with some suggesting it is a repeat of his ARWINSS effort but targetted at the memory manager.