# reuse Published articles for reuse. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Announcing the S3 API: Use any S3 client with Appwrite Storage DevFeed: [Announcing the S3 API: Use any S3 client with Appwrite Storage]() Original publisher: [Read original article]() Author: Torsten Dittmann Published: 2026-09-03T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Amazon S3](), [API](), [Amazon Web Services](), [SDKs](), [Command-line interface](), [migration]() Tags: [announcements](), [api](), [aws](), [backup](), [cli](), [code](), [commands](), [data](), [files](), [migration](), [reuse](), [s3](), [sdk](), [sdks](), [server](), [storage](), [tools]() ### AI overview Appwrite Storage now exposes an S3-compatible API that supports AWS CLI, AWS SDKs, rclone, s3cmd, and other S3 clients. Existing buckets and files remain available through both the native Storage API and the S3 API, with support for standard operations, multipart uploads, and presigned URLs. ### Source excerpt Appwrite Storage now exposes an S3-compatible API. Point the AWS CLI, the AWS SDKs, and tools like rclone at your Appwrite buckets, with no migration required. ## Ray tracing massive amounts of animated geometry using tetrahedral cages DevFeed: [Ray tracing massive amounts of animated geometry using tetrahedral cages]() Original publisher: [Read original article]() Author: Holger Gruen Published: 2026-07-22T01:00:00Z Content type: article Language: en Sources: [AMD GPUOpen]() Topics: [Ray Tracing](), [GPU](), [real-time]() Tags: [agility-sdk](), [animation](), [architecture](), [article-release](), [directx](), [game-development](), [gpu](), [graphics](), [graphics-apis](), [memory](), [microsoft-agility-sdk](), [microsoft-directx](), [optimization](), [performance](), [ray-tracing](), [raytracing](), [real-time](), [research](), [reuse](), [technical-article](), [technical-articles](), [white-paper]() ### AI overview The article explains a ray-tracing method for massive animated scenes that uses low-resolution tetrahedral cages to deform geometry while reusing static mini-meshes and mini-BLASes. This reduces per-frame update and memory costs, with the paper demonstrating roughly 585 million animated triangles at 60 frames per second on an AMD Radeon RX 9070 XT at 1080p. ### Source excerpt Animate compact tetrahedral cages and reuse static mini-BLASes to ray-trace hundreds of millions of triangles in real time, dramatically cutting per-frame update and memory costs for dense foliage, grass, and crowds. ## Nginx TLS tuning for HTTPS performance, TTFB, and latency DevFeed: [Nginx TLS tuning for HTTPS performance, TTFB, and latency]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-06-10T12:06:18Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [nginx](), [TLS (Transport Layer Security)](), [Latency](), [Handshake](), [HTTP](), [Back end]() Tags: [blog](), [encryption](), [http](), [http-3](), [latency](), [linux](), [nginx](), [performance](), [request](), [reuse](), [security](), [server](), [sysadmins](), [tls]() ### AI overview A practical guide to tuning Nginx TLS, HTTP/2, and HTTP/3 settings for HTTPS performance. It explains that tuning can reduce handshake overhead and improve connection reuse, while application execution often remains the main contributor to TTFB and latency. ### Source excerpt Nginx TLS tuning won't fix a slow application, but it does cut handshake overhead and improve connection reuse, which shaves milliseconds off every HTTPS request. Continue reading... ## Flutter's multiplatform value for agentic development DevFeed: [Flutter's multiplatform value for agentic development]() Original publisher: [Read original article]() Author: Michael Thomsen Published: 2026-05-18T18:42:10Z Content type: article Language: en Sources: [Flutter - Medium]() Topics: [Flutter](), [multiplatform](), [Artificial Intelligence](), [Dart](), [Development](), [Large Language Model]() Tags: [agentic](), [agentic-ai](), [agentic-development](), [ai](), [code](), [consistency](), [dart](), [flutter](), [flutter-app-development](), [llms](), [mobile-app-development](), [multiplatform](), [reuse]() ### AI overview The article explains how Flutter's single shared codebase can support multiplatform app development and agent-driven workflows. It argues that writing features once in Dart gives AI assistants unified context, reduces token usage and hallucination risk, and helps maintain consistency across platforms. It also describes reported benefits including code reuse, native compilation, and strongly typed Dart code. ### Source excerpt The fundamental value of multiplatform development with Flutter lies in building apps that support multiple platforms with just a single, shared source codebase, allowing developer teams to work in unison across all platforms. This is crucial in an AI-driven world where enhanced consistency, reduced token usage, and fast market reach become vital. By maintaining a single codebase, builders can focus their AI assistants on one unified context, drastically reduce token overhead, and minimize AI hallucinations. Instead of asking AI to translate features across fragmented, platform-specific languages, builders can leverage AI to write it once in Dart and instantly deploy it everywhere. Dash secretly hanging out in an alley doing agentive thingsThe existing value proposition Multiplatform development relies on enabling a single, shared source codebase. In our first-party Flutter apps, between 95% and 99% of the source code is shared. This massive code reuse unlocks several benefits: Faster time to market across multiple platforms because a team only needs to maintain one codebase. Guaranteed consistency across platforms, giving companies a single, consistent feature set to support across all their customers, regardless of their platform of choice. Native performance and stability because Flutter code is compiled to each platform's native machine code. Semantic guardrails increase security because the Dart language is strongly typed. The agentic value proposition While LLMs are good at translating requirements into code, using them to build separate native apps for each platform scales poorly. Replicating features across different languages using LLMs multiplies generation time and token usage, and can quickly lead to implementations drifting apart. Flutter's single-source solution eliminates these problems. But beyond just code sharing, Flutter's specific architecture makes it the ideal framework for agent-driven development. This emerging value proposition is driven by ## Transforming Capital One's Data Marketplace with Embedded Governance and a Product Mindset DevFeed: [Transforming Capital One's Data Marketplace with Embedded Governance and a Product Mindset]() Original publisher: [Read original article]() Author: Valeria Gomez Published: 2026-01-13T13:34:19Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Architecture & Design](), [Orchestration](), [Microservices](), [data]() Tags: [apis](), [apollo-federation](), [dashboards](), [data](), [ecosystems](), [events](), [governance](), [graphql](), [latency](), [low-latency](), [microservices](), [orchestration](), [performance](), [platform](), [product-mindset](), [reuse](), [router](), [scale]() ### AI overview A recap of GraphQL Summit 2025 describing how Capital One used GraphQL, Apollo Federation, and Apollo Router to build an enterprise data marketplace. The approach centralized orchestration across microservices, applied company standards, improved data discoverability and reuse, and was validated with a production-traffic rollout showing low latency, high throughput, and no disruption to live workloads. ### Source excerpt A recap from GraphQL Summit 2025 on how Capital One applied a product mindset to build an enterprise data marketplace powered by Apollo Large organizations with complex data ecosystems often face a familiar challenge. As systems evolve over time, data becomes harder to find, harder to trust, and harder to use. Teams build APIs independently, integrations multiply, and identifying the authoritative source of data can take significant effort. ## The Open Evaluation Standard: Benchmarking NVIDIA Nemotron 3 Nano with NeMo Evaluator DevFeed: [The Open Evaluation Standard: Benchmarking NVIDIA Nemotron 3 Nano with NeMo Evaluator]() Original publisher: [Read original article]() Author: Seph Mard; Isabel Hulseman; Besmira Nushi; Piotr Januszewski; Grzegorz Chlebus; VivienneZhang; Wojciech Prazuch; Pablo Ribalta; Nik Spirin; Ferenc Galko Published: 2025-12-17T13:22:18Z Content type: article Language: en Sources: [Hugging Face - Blog]() Topics: [LLM evaluation / benchmarking](), [Benchmark](), [NeMo](), [Nemotron](), [Artificial Intelligence](), [Nvidia](), [configuration](), [Library](), [Inference]() Tags: [ai](), [benchmark](), [benchmarking](), [benchmarks](), [build](), [configuration](), [evaluation](), [inference](), [library](), [model](), [models](), [nemo](), [nemotron](), [nvidia](), [open](), [pipeline](), [pipelines](), [reuse](), [validation](), [verify]() ### AI overview This article presents an open, reproducible evaluation recipe for NVIDIA Nemotron 3 Nano 30B A3B using the NeMo Evaluator library. It explains how complete configurations, prompts, runtime settings, harness versions, logs, and artifacts enable independent verification and consistent model comparisons across inference backends and infrastructure. ### Source excerpt NVIDIA released Nemotron 3 Nano 30B A3B with an explicitly open evaluation approach to make that distinction clear. Alongside the model card, we are publishing the complete evaluation recipe used to generate the results, built with the NVIDIA NeMo Evaluator library, so anyone can rerun the evaluation pipeline, inspect the artifacts, and analyze the outcomes independently. We believe that open innovation is the foundation of AI progress. ## Six Principles for Writing Clean, Maintainable Classes DevFeed: [Six Principles for Writing Clean, Maintainable Classes]() Original publisher: [Read original article]() Author: Daniel Moka Published: 2025-04-19T05:00:55Z Content type: tutorial Language: en Sources: [Craft Better Software]() Topics: [clean-code](), [Code](), [Development](), [implementation](), [Inheritance]() Tags: [classes](), [clean-code](), [code](), [implementation](), [inheritance](), [quality](), [reuse]() ### AI overview This tutorial presents six principles for writing clean classes: use noun-based names, avoid unnecessary getters and setters, hide internal state, expose a focused API, order methods by call flow, and favor composition over inheritance. It argues that small, focused, intention-revealing classes are easier to change, test, and understand. ### Source excerpt 7 essential tips to produce maintainable and intention-revealing classes ## Configuring IP Addresses Won't Make You an Expert DevFeed: [Configuring IP Addresses Won't Make You an Expert]() Original publisher: [Read original article]() Published: 2025-01-09T05:39:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Networks](), [Learning](), [networking](), [Routing (disambiguation)](), [Integration testing](), [Containers]() Tags: [art](), [container](), [containers](), [integration-testing](), [mistakes](), [netlab](), [ospf](), [production](), [reuse](), [routing](), [testing]() ### AI overview This opinion argues that repeatedly configuring routine networking details in labs does not by itself build expertise. The author describes using netlab to automate familiar setup, reuse lab designs, create new topologies quickly, and focus on unfamiliar networking concepts, while noting that adapting existing topologies can still be useful for engineers who work on running networks. ### Source excerpt A friend of mine recently wrote a nice post explaining how netlab helped him set up a large network topology in a reasonably short timeframe. As expected, his post attracted a wide variety of comments, from "netlab is a gamechanger" (thank you 😎) to "I prefer traditional labs." Instead of writing a bunch of replies into a walled-garden ecosystem, I decided to address some of those concerns in a public place. Let's start with: Read more ... ## How to create an ESP-IDF component DevFeed: [How to create an ESP-IDF component]() Original publisher: [Read original article]() Author: John Lee Published: 2024-12-02T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Embedded Software Dev](), [Embedded Systems](), [Development](), [ESP32](), [Hardware]() Tags: [architecture](), [blog](), [code](), [component](), [components](), [driver](), [embedded](), [embedded-systems](), [esp-idf](), [esp-idf-component](), [esp32-c3](), [hardware](), [how-to](), [i2c](), [library](), [maintenance](), [project](), [registry](), [reuse](), [sensor]() ### AI overview This tutorial explains how to create and add project components in ESP-IDF. It covers component structure, placement in an application or separate project, and an example sensor driver for an I2C device using an ESP32-C3 development board with an integrated SHTC3 sensor. ### Source excerpt Using a monolithic architecture to develop complex applications tightly integrated with all the business logic, peripheral drivers, protocols, cloud connectivity, and so on, might sound like a nightmare. Yet, this is common in embedded systems, because it helps keep the resource overhead to the minimum. Inevitably, such approach makes collaborative development, maintenance, and reuse of code challenging to say the least. ## What is the ESP Component Registry? DevFeed: [What is the ESP Component Registry?]() Original publisher: [Read original article]() Author: John Lee Published: 2024-11-08T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Development](), [Command-line interface](), [Code](), [CMake]() Tags: [architecture](), [article](), [blog](), [cli](), [cmake](), [component](), [components](), [dependencies](), [development](), [esp-idf](), [libraries](), [registry](), [reuse]() ### AI overview This article explains the ESP Component Registry and the concepts behind it: components, the component manager, and the registry. It describes how reusable components support ESP-IDF projects and how the component manager adds dependencies, creates component structures, and downloads dependencies during CMake builds. ### Source excerpt When starting a new project, we often reuse existing code, for example from libraries and drivers. This not only saves time but also makes your project easier to maintain. In this article, we will explore what the ESP Component Registry is and the key concepts of components, making it easy to understand not only how to use components but also how to contribute. Concept# The architecture of ESP-IDF is modular, making it easier to understand and maintain. ## Reusable Styles in Compose DevFeed: [Reusable Styles in Compose]() Original publisher: [Read original article]() Published: 2024-10-17T00:00:00Z Content type: tutorial Language: en Sources: [Donovan LaDuke - Developer]() Topics: [Jetpack Compose](), [ui](), [Code]() Tags: [code](), [compose](), [extension-function](), [function](), [layout](), [maintenance](), [reuse]() ### AI overview This article explains how to create reusable styles in Jetpack Compose by grouping shared modifier chains into reusable modifier functions. It discusses applying padding, borders, and card styling across layout components, while warning against excessive nesting and overuse of abstraction. ### Source excerpt Leverage Modifier chains to create reusable styles in Compose ## Scaling Mobile Development at Microsoft-- Mental Model DevFeed: [Scaling Mobile Development at Microsoft-- Mental Model]() Original publisher: [Read original article]() Author: Anand Nath Published: 2024-06-12T14:37:04Z Content type: article Language: en Sources: [Android@Microsoft - Medium]() Topics: [Mobile](), [Development](), [Microsoft](), [App](), [User Experience](), [Android]() Tags: [android](), [app](), [architecture](), [development](), [ios](), [microsoft](), [mobile](), [mobile-development](), [reuse](), [user-experience]() ### AI overview This first article in a series presents a high-level mental model for scaling development across Microsoft mobile applications. It describes separately maintained codebases and overlapping experiences, then discusses High Value Controls such as One Camera and One Player, including problems caused by siloed development such as inconsistency, limited interoperability, and redundant libraries. ### Source excerpt Scaling Mobile Development at Microsoft -- Mental Model In the Scaling Teams Mobile Development series we looked at scaling development in a single mobile code base. Since then, we were at work, looking at up-levelling this problem statement and look at how to scale across mobile applications. Here is a new series which tries to throw some light around this topic. This article is the first of a series, starting with understanding the problem statement and a high level solution. In the following articles we will dive deeper with an example and discuss practical aspects of how we got it done. Let's dive in! Photo by Hans-Peter Gauster on UnsplashShared experiences Microsoft has a suite of mobile applications. Each of these applications are developed in separate code base, has its own release cycles. There are a lot of overlapping experiences across these applications. These experiences are also implemented, tested and maintained independently in each application. Here are some examples: File picking experience across Microsoft mobile apps.Calendar experience across Microsoft mobile apps.File sharing experience across Microsoft mobile apps. In order to drive consistent user experience across these applications, Microsoft is invested in developing "High Value Controls" aka HVCs. For example, there is One Camera which provides camera functionality for most of the Microsoft apps, there is One Player which provides video playback in Microsoft apps and some more. Most of the HVCs are developed in silos without any common considerations or guidelines. Some HVCs are developed inside one of the Microsoft mobile apps and then lifted out to be positioned as reusable. These come with the remnants of the app specific concepts and logic, which does not sit well with other apps. This kind of HVC development lack consistency, coherence and interoperability. This also leads to a series of issues for both the Microsoft mobile apps and HVCs. Issues for Microsoft mobile apps Note: In this ## Managing State in Vue Applications: The Composable Provider Pattern DevFeed: [Managing State in Vue Applications: The Composable Provider Pattern]() Original publisher: [Read original article]() Author: Doximity Published: 2023-07-21T07:23:00Z Content type: article Language: en Sources: [Doximity]() Topics: [Vue.js](), [Front end](), [Scalability](), [Nuxt.js]() Tags: [code-modularity](), [components](), [maintainability](), [modularity](), [reusable-code](), [reuse](), [scalability](), [state-management](), [vue]() ### AI overview This article explains the Composable Provider pattern for state management in Vue applications. The approach combines the Vue Composition API with the Provide/Inject APIs to manage complex, feature-driven state, with benefits including scalability, maintainability, reusability, and reduced code duplication. ### Source excerpt State management is a fundamental concept of front-end application design, and a critical aspect in building robust Vue applications. As Vue applications grow in complexity, managing state becomes an increasingly challenging task, especially when working with a large organization of engineers spread across various product teams. Fortunately, the Vue and Nuxt ecosystem provides a variety of state management solutions, each with its own trade-offs. In this blog post we will explore the Composable Provider pattern, which handles state management by combining the Vue Composition and Provide/Inject APIs, and why its clean and simple implementation is a powerful approach to handling complex, feature-driven state in modern Vue applications. Note: This article was originally intended as a reference for our internal engineering team, but given its potential general use among Vue application developers we are publishing it here. We hope you'll find this pattern helpful when designing your Vue application's state as we have here at Doximity! Why Efficient State Management Matters Efficient state management plays a crucial role in the development of Vue applications. As applications grow in complexity, the ways in which we manage and handle changes to state become increasingly important. Here are a few key reasons why managing state efficiently matters: Scalability: As Vue applications and the teams building them grow in size, the complexity and size of their state grow also. Efficient state management allows for better scalability by providing a structured and organized approach to handling state. It becomes easier to add new features, maintain existing functionality, and reason about the flow of data within the application. Code Maintainability: Well-managed state reduces code complexity and promotes code maintainability. When state is not encapsulated properly, it becomes challenging to understand and modify the application's behavior. By implementing sound state management ## Ultimate Go: Advanced Engineering Episode 9 DevFeed: [Ultimate Go: Advanced Engineering Episode 9]() Original publisher: [Read original article]() Published: 2022-12-20T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Go Language](), [Bitcoin](), [Ethereum]() Tags: [bitcoin](), [blockchain](), [blockchain-asset](), [build](), [building](), [code](), [concepts](), [engineering](), [ethereum](), [genesis](), [genesis-json](), [genesis-record](), [go](), [go-blockchain](), [implement](), [introduction](), [project](), [project-layout](), [reuse](), [standard-library]() ### AI overview This video tutorial covers the initial layout of a blockchain project in Go, including creating a genesis record and explaining its role. It also introduces fundamental blockchain verifications. ### Source excerpt Introduction In episode 8, Bill wanted to build a blockchain in Go and began to lay the groundwork for the project. Go is a good choice because its standard library has the necessary network and cryptographical functionality required to build a blockchain. Unlike the previous segment, Bill plans to use this blockchain to manage accounts and balances with hypothetical assets. Bill will reuse concepts from ethereum, bitcoin and the previous segment of the series to implement this blockchain. ## Why the DRY Principle Is Often Misunderstood in Software Design DevFeed: [Why the DRY Principle Is Often Misunderstood in Software Design]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2022-04-30T13:13:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Software Engineering](), [Architecture & Design](), [abstraction](), [reuse](), [maintenance]() Tags: [abstraction](), [component](), [dependencies](), [maintenance](), [practices-software-development-software-craft](), [reuse](), [software-design]() ### AI overview The article argues that the DRY principle is frequently misapplied in software development. Reusing code can reduce duplication but may introduce dependencies, rigid contracts, and abstractions that are difficult to change, especially when systems evolve independently. ### Source excerpt DRY - DO repeat yourself When I started my career as a software developer and already during university, almost no principle was mentioned as often as the DRY principle: "Do not repeat yourself" ## Effective Kotlin Item 36: Prefer composition over inheritance DevFeed: [Effective Kotlin Item 36: Prefer composition over inheritance]() Original publisher: [Read original article]() Published: 2021-04-25T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [Inheritance](), [Object-oriented programming (OOP)](), [Kotlin](), [reuse](), [superclass]() Tags: [approach](), [behavior](), [hierarchy](), [inheritance](), [kotlin](), [object](), [oop](), [reuse](), [superclass](), [workshop-learning-programming]() ### AI overview The article argues that inheritance should primarily model a clear "is a" relationship and can be problematic when used mainly for code extraction or reuse. It presents class composition as a safer and more explicit alternative, while acknowledging that composition requires additional code. ### Source excerpt Years of OOP made us overuse inheritance. Instead, we should more often use a composition that is safer and more explicit. More often, but not always... ## Threat Modeling Building Blocks DevFeed: [Threat Modeling Building Blocks]() Original publisher: [Read original article]() Author: Adam Published: 2019-09-04T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [data](), [Requirements]() Tags: [building](), [comparison](), [data-protection](), [models](), [requirements](), [results](), [reuse](), [tasks](), [techniques](), [things]() ### AI overview The article presents threat modeling as a collection of interconnected tasks and discusses research on breaking threat modeling into smaller, assessable building blocks. It highlights comparisons involving privacy and data protection, requirements, STRIDE, CAPEC, CWE, OWASP, data-flow-diagram variants, and CARiSMA extended. ### Source excerpt Threat modeling isn't one task -- its a collection of tasks that build on each other to produce more valuable insights. ## Features composability DevFeed: [Features composability]() Original publisher: [Read original article]() Published: 2019-03-19T14:27:48Z Content type: opinion Language: en Sources: [Blog by Michael Dubakov]() Topics: [implementation](), [Software](), [App]() Tags: [component](), [evolution](), [implementation](), [reuse](), [software](), [structure]() ### AI overview The article argues that software features should avoid depending on other features' internal details. Treating features as independent components with public interfaces and extension points improves composability, reuse, and software evolution. ### Source excerpt When we add features to a product, we rarely think about composability. We assume that it is OK for any feature to rely on internal... ## UI Testing the Clean Way DevFeed: [UI Testing the Clean Way]() Original publisher: [Read original article]() Author: Keegan Rush Published: 2018-10-23T00:00:00Z Content type: tutorial Language: en Sources: [The Coded Self]() Topics: [Testing](), [Swift](), [Xcode](), [To-Do]() Tags: [bugs](), [reuse](), [swift](), [testing](), [ui-testing](), [xcode]() ### AI overview This tutorial discusses keeping Swift UI tests clean and readable using a To-Do list app. It explains that Xcode's recorded UI tests can produce unreadable, brittle, duplicated code and may fail to capture some interactions, then introduces a cleaner testing approach. ### Source excerpt I write software, and sometimes I write bugs. But, when I do, I catch them early with testing. I do manual tests before I commit, I write unit tests as I write my code. Lately, I've also been getting into writing UI tests. One critique of UI testing is how messy and brittle it can be. Building the tests can be complicated. You might spend hours on a test just for a design to change that breaks the test and ruins all your hard work. So, I want to tell you about some problems you might face in keeping your UI tests clean and readable, and how we can leverage Swift for this endeavour. I'll walk you through my approach to UI testing with everyone's favorite example project - a To-Do list app. I know, boring, right? Well, it works perfectly for the examples we'll be looking at, so... You can download the example project here. It's a simple app that allows us to create, edit, and delete a to-do. Just press record UI testing in Xcode is easy. Click inside the body of an empty UI test, click the Record button, and you're up and running. Let's start off by recording a UI test to add a new to-do. That was easy! And it sure did create a lot of code. That must be good, right? func testExample() { let app = XCUIApplication() app.navigationBars["Todo List"].buttons["Add"].tap() let textField = app.otherElements.containing(.navigationBar, identifier:"New Todo") .children(matching: .other).element.children(matching: .other).element .children(matching: .other).element.children(matching: .textField).element textField.tap() textField.tap() let datePickersQuery = app.datePickers datePickersQuery.pickerWheels["October"]/*@START_MENU_TOKEN@*/.press(forDuration: 0.6);/*[[".tap()",".press(forDuration: 0.6);"],[[[-1,1],[-1,0]]],[0]]@END_MENU_TOKEN@*/ datePickersQuery.pickerWheels["9"]/*@START_MENU_TOKEN@*/.press(forDuration: 0.5);/*[[".tap()",".press(forDuration: 0.5);"],[[[-1,1],[-1,0]]],[0]]@END_MENU_TOKEN@*/ app.buttons["Done"].tap() } I'll be honest, most of that is unreadable to me. Run ## From ng-controller to components with Angular 1.5 DevFeed: [From ng-controller to components with Angular 1.5]() Original publisher: [Read original article]() Published: 2016-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Code](), [Routing (disambiguation)](), [modern web development]() Tags: [angular](), [architecture](), [component](), [how-to](), [refactor](), [reuse](), [router](), [routing]() ### AI overview A tutorial explaining how to migrate an Angular 1 application from an ng-controller and MV* architecture toward a component-oriented structure. It covers the "controller as" syntax, converting controllers to directives, and using the component() helper introduced in Angular 1.5. ### Source excerpt Lorem ipsum dolor sit amet ## Caviar iOS: Migrating from AdvancedCollectionView to PJFDataSource DevFeed: [Caviar iOS: Migrating from AdvancedCollectionView to PJFDataSource]() Original publisher: [Read original article]() Author: Square Engineering Published: 2016-06-13T16:11:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [iOS](), [Library](), [Framework](), [Code]() Tags: [app-architecture](), [architecture](), [engineering](), [ios](), [library](), [open-source](), [reuse]() ### AI overview This article explains how the Caviar iOS app moved from Apple's AdvancedCollectionView sample architecture to PJFDataSource. The team created an external library that retained the useful data-source patterns while reducing unnecessary complexity, then open-sourced it. ### Source excerpt Behind-the-scenes look at the evolution of PJFDataSource in our Caviar iOS app. ## Wrapping a jQuery plugin in a Ember.js component (Screencast) DevFeed: [Wrapping a jQuery plugin in a Ember.js component (Screencast)]() Original publisher: [Read original article]() Published: 2014-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [jQuery](), [reuse]() Tags: [component](), [ember](), [js](), [plugin](), [reuse]() ### AI overview A screencast demonstrates how to wrap a jQuery plugin in an Ember.js component for reuse. ### Source excerpt Time for another screencast! This one is shorter and shows how easy it is to wrap a jQuery plugin in an Ember.js component for reuse. ## Intellectual Property: Ideology vs Practicality DevFeed: [Intellectual Property: Ideology vs Practicality]() Original publisher: [Read original article]() Published: 2013-12-14T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [GNU General Public License](), [free software](), [Code](), [Software]() Tags: [apache](), [cost](), [free](), [free-software](), [intellectual-property](), [open-source](), [os](), [react](), [reactos](), [reuse](), [source](), [win32](), [winapi]() ### AI overview The article argues that the GPL's ideological goal of preserving users' rights to modify and extend software also creates obligations for developers who reuse GPL-licensed code. It contends that the resulting source-disclosure burden can make developing a separate solution or choosing a more permissive license such as Apache or BSD more practical. ### Source excerpt The thing that people need to keep in mind when discussing the GPL is that it was created to achieve an ideological and political goal, namely that users of software should have the right to modify and extend the software as they see fit. To achieve this goal, the GPL seeks to ensure that the source code is always available and that reusing the source code in question comes without any restrictions save for what the GPL itself imposes in order to ensure this " ## Interface Segregation Principle DevFeed: [Interface Segregation Principle]() Original publisher: [Read original article]() Published: 2011-08-12T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [Software Engineering](), [interfaces](), [Architecture & Design](), [Inheritance](), [abstraction](), [reuse]() Tags: [abstraction](), [code](), [inheritance](), [interfaces](), [reuse](), [software-design](), [solid]() ### AI overview This tutorial explains the Interface Segregation Principle, the final principle in the SOLID object-oriented design set. It describes how oversized interfaces create unused or dummy methods and recommends splitting them into smaller, purpose-specific interfaces, illustrated with a car example involving automatic transmission and air conditioning. ### Source excerpt I build software products and write on the Internet.