# strategies Published articles for strategies. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Choosing among write-through, write-behind, and write-around caching strategies DevFeed: [Choosing among write-through, write-behind, and write-around caching strategies]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Caching](), [Databases](), [Redis](), [consistency](), [Latency]() Tags: [cache](), [caching](), [consistency](), [database](), [latency](), [orders](), [postgres](), [redis](), [strategies](), [system-design](), [write](), [write-behind](), [write-through]() ### AI overview This article compares write-through, write-behind, and write-around caching strategies. It explains their trade-offs among database latency, cache hit rates, consistency, and the risk of losing acknowledged writes when a process fails. ### Source excerpt The three write strategies differ in what happens between the cache write and the database write, and that gap is where correctness lives. Write-through updates both before acknowledging, so it is safe and pays the full database latency. Write-behind acknowledges after the cache write and flushes later, which is fast and can lose acknowledged writes if the process dies. Write-around skips the cache entirely on write, which avoids caching data nobody reads and costs a miss on the next read. ## How Software Engineers Progress from Entry-Level to Senior Roles DevFeed: [How Software Engineers Progress from Entry-Level to Senior Roles]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-09-10T12:17:04Z Content type: opinion Language: en Sources: [AlgoMaster Newsletter]() Topics: [Software](), [Job]() Tags: [article](), [career-growth](), [engineering](), [guest-post](), [software-engineer](), [strategies]() ### AI overview A guest post explains how software engineers progress toward senior roles by taking on broader problems, more ambiguity, greater ownership, and larger impact. It outlines changing expectations from entry-level to mid-level engineering, including driving loosely defined work through design, implementation, testing, and delivery. ### Source excerpt Growing Through the Levels ## Strategies for Migrating from a Monolith to Microservices DevFeed: [Strategies for Migrating from a Monolith to Microservices]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-06-23T07:55:12Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Architecture & Design](), [microservices architecture](), [migration](), [legacy systems](), [gateway]() Tags: [api-gateway](), [architecture](), [automated](), [big-bang](), [feature-flags](), [incremental](), [legacy-systems](), [microservices](), [migration](), [monolith](), [parallel](), [rewrite](), [strategies](), [testing]() ### AI overview This tutorial outlines patterns for gradually moving from a monolithic architecture to microservices. It describes the Strangler Fig Pattern, Parallel Run Pattern, and Collaborator Pattern, covering techniques such as API gateways, incremental migration, traffic splitting, feature flags, and automated comparison testing. ### Source excerpt Top Strategies ## Top Cache Eviction Strategies DevFeed: [Top Cache Eviction Strategies]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-04-28T09:03:41Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Caching](), [Cache](), [Latency](), [App](), [Databases](), [Redis]() Tags: [browsers](), [cache](), [caching](), [database](), [operating-systems](), [performance](), [redis](), [strategies](), [ttl]() ### AI overview The article explains cache eviction as a way to manage limited cache memory and reviews TTL, LRU, and LFU strategies, including their operation, use cases, advantages, and drawbacks. ### Source excerpt Caching is a crucial technique for improving application performance and responsiveness. ## Why focused coding time may be limited to a few hours per day DevFeed: [Why focused coding time may be limited to a few hours per day]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-01-29T16:02:51Z Content type: opinion Language: en Sources: [Tech World With Milan Newsletter]() Topics: [coding](), [meetings](), [Computer science]() Tags: [burnout](), [coding](), [context](), [cycle-time](), [developer](), [meetings](), [strategies](), [techniques]() ### AI overview This commentary argues that developers may have only three to four hours of high-focus coding capacity per day. It discusses cognitive limits, interruptions, meetings, flow, and deep-work strategies, while recommending practices such as time-blocking, batching communication, async defaults, and no-meeting days. ### Source excerpt Most of us have felt it: after a few solid hours of coding, your brain starts shutting down. ## Why traditional motivation techniques can undermine intrinsic motivation in tech teams DevFeed: [Why traditional motivation techniques can undermine intrinsic motivation in tech teams]() Original publisher: [Read original article]() Author: Tom Published: 2025-09-26T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [DRIVE]() Tags: [autonomy-mastery-purpose](), [best-practices](), [daniel-pink-drive](), [effective-leadership-strategies](), [intrinsic-motivation](), [leadership](), [leadership-best-practices](), [motivation-in-tech-teams](), [people](), [practical](), [strategies](), [team](), [team-engagement](), [tech]() ### AI overview This workshop-style article examines how traditional rewards, pressure, and micromanagement can undermine intrinsic motivation, especially in complex and creative tech work. Drawing on Daniel Pink's Drive, it encourages team leaders to support autonomy, mastery, and purpose. ### Source excerpt Discover why traditional motivation techniques can backfire in tech teams and how leaders can foster intrinsic motivation through autonomy, mastery, and purpose. Learn actionable strategies to empower your team and boost engagement, based on insights from Daniel Pink's "Drive." ## Whodunit: LLM Murder Mysteries DevFeed: [Whodunit: LLM Murder Mysteries]() Original publisher: [Read original article]() Author: James Heller Published: 2025-08-26T07:00:00Z Content type: article Language: en Sources: [Apartment 304]() Topics: [LLM Techniques](), [Go Language]() Tags: [ai-authored](), [apartment-304](), [custom-software-solutions](), [devops](), [devops-engineer](), [go](), [golang](), [language-models](), [large-language-models](), [llm](), [logic](), [models](), [puzzle](), [puzzles](), [software-architecture](), [software-development](), [software-engineer](), [strategies](), [test]() ### AI overview This article describes building Whodunit, a low-tech murder-mystery game whose mysteries are written with large language models. It discusses developing a mental model for calling LLMs, testing LLM services and Go libraries, improving logical soundness through trial and error, and managing unreliable LLM APIs. ### Source excerpt Can Large Language Models write engaging mysteries? Find out in this week's episode of "Whodunit?" ## Transforming Developer Experience: Lessons from Building a Platform Team DevFeed: [Transforming Developer Experience: Lessons from Building a Platform Team]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2025-07-10T00:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [devex](), [Developer experience](), [code productivity]() Tags: [cognitive-load](), [developer](), [developer-experience](), [engineering](), [platform](), [productivity](), [strategies](), [workflow]() ### AI overview A talk about founding and running a Developer Experience team within a hypergrowth startup from 2021 to 2023. It covers team selection, building a high-performing group, task prioritization, cross-department collaboration, challenges, mistakes, and lessons learned. ### Source excerpt Creating a superior developer experience is key to motivating and streamlining engineering teams, serving as a strategic pillar for business success. Focus areas include optimizing workflow, reducing cognitive load, and establishing efficient feedback loops. As technology grows more complex, achieving these becomes increasingly challenging. ## How Anaconda writes documentation DevFeed: [How Anaconda writes documentation]() Original publisher: [Read original article]() Author: Tiffany Chen Published: 2025-05-16T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Artificial Intelligence](), [Microsoft]() Tags: [ai](), [best-practices](), [documentation](), [strategies](), [strategy](), [structure](), [technical](), [technical-writing](), [workflow]() ### AI overview Anaconda's technical writing manager explains how he scaled documentation from a solo effort into a team workflow using prioritization, style guides, and formal new-product introduction processes. He also describes AI's role in repetitive tasks while emphasizing human oversight for quality and accuracy. ### Source excerpt We sat down with Idan Englander, Manager of Technical Writing at Anaconda, to discuss how he scaled from being a solo writer, what documentation processes actually work, and where AI fits (and doesn't) in the writing workflow. If you're curious about more of Idan's writing principles, check out our Guide to Technical Writing. ## Packing Matrix-Vector Multiplication in Fully Homomorphic Encryption DevFeed: [Packing Matrix-Vector Multiplication in Fully Homomorphic Encryption]() Original publisher: [Read original article]() Published: 2024-09-07T04:18:09Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [homomorphic encryption](), [FHE](), [Encryption](), [layout](), [parallel](), [Python]() Tags: [arithmetic](), [code](), [cryptography](), [data](), [encryption](), [fhe](), [github-repository](), [homomorphic-encryption](), [layout](), [linear-algebra](), [lwe](), [mathematics](), [packing](), [parallel](), [programming](), [python](), [rlwe](), [simd](), [strategies]() ### AI overview This article explains packing for SIMD-style fully homomorphic encryption. It describes how to arrange plaintext data in RLWE ciphertexts so matrix-vector multiplication requires fewer alignment multiplications and rotations, then introduces two basic packing techniques and a computational model. ### Source excerpt In my recent overview of homomorphic encryption, I underemphasized the importance of data layout when working with arithmetic (SIMD-style) homomorphic encryption schemes. In the FHE world, the name given to data layout strategies is called "packing," because it revolves around putting multiple plaintext data into RLWE ciphertexts in carefully-chosen ways that mesh well with the operations you'd like to perform. By "mesh well" I mean it reduces the number of extra multiplications and rotations required merely to align data elements properly, rather than doing the actual computation you care about. ## Streamlining Design Workflows: Best Practices and Strategies for Success DevFeed: [Streamlining Design Workflows: Best Practices and Strategies for Success]() Original publisher: [Read original article]() Author: Jacqueline Rhoda Published: 2024-08-21T18:53:49Z Content type: tutorial Language: en Sources: [Apartment 304]() Topics: [User Experience](), [consistency](), [Users](), [file]() Tags: [apartment-304](), [best-practices](), [components](), [consistency](), [custom-software-solutions](), [design](), [devops](), [devops-engineer](), [efficiency](), [file](), [guide](), [software-architecture](), [software-development](), [software-engineer](), [strategies](), [style-guide](), [users](), [workflows]() ### AI overview This article explains how to streamline design workflows by defining user objectives, using product requirement documents and low-fidelity wireframes, organizing design files, and integrating design elements into applications. ### Source excerpt Enhance your design workflows to achieve more efficient and successful design outcomes. ## Optimizing Gradle Builds in Multi-module Projects - Jigar Brahmbhatt DevFeed: [Optimizing Gradle Builds in Multi-module Projects - Jigar Brahmbhatt]() Original publisher: [Read original article]() Published: 2023-10-04T15:46:40Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Gradle](), [build performance](), [build times](), [Kotlin Multiplatform](), [Benchmark](), [Cache](), [Android Studio]() Tags: [android-studio](), [benchmark](), [build-performance](), [build-times](), [cache](), [gradle](), [kotlin](), [kotlin-multiplatform](), [modules](), [optimizing](), [strategies]() ### AI overview A practical guide to reducing Gradle build times in large Kotlin Multiplatform multi-module projects. It recommends benchmarking builds, using Gradle Build Scan and Android Studio Build Analyser, reviewing cache and configuration settings, and improving dependency visibility. ### Source excerpt Explore practical use cases and strategies for speeding up Gradle builds in your multi-module projects. ## Six Strategies for Making Data Visualizations Accessible, Scalable, and Helpful DevFeed: [Six Strategies for Making Data Visualizations Accessible, Scalable, and Helpful]() Original publisher: [Read original article]() Published: 2022-11-08T13:00:00Z Content type: tutorial Language: en Sources: [Material.io - Material Design]() Topics: [Data visualization](), [Accessibility]() Tags: [accessibility](), [accessible](), [data](), [data-visualization](), [making](), [strategies](), [tips](), [visualization]() ### AI overview The article presents six strategies for making data visualizations accessible, scalable, and helpful. ### Source excerpt Six strategies for making your data visualization accessible, scalable, and helpful ## Card Soccer DevFeed: [Card Soccer]() Original publisher: [Read original article]() Published: 2022-07-10T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Compose](), [ui](), [compose-for-desktop](), [Web]() Tags: [ai](), [compose](), [compose-ui](), [desktop](), [game](), [how-to](), [kotlin](), [kotlin-multiplatform](), [multiplatform](), [port](), [strategies](), [web]() ### AI overview Card Soccer is a turn-based card game against an AI opponent. Players move a card-based ball through rows by matching its value or suit, using passes or shots to score goals. The author describes developing desktop and web versions with Kotlin Multiplatform and Jetpack Compose UI. ### Source excerpt How to play The goal of the game is to win AI opponent by scoring more goals. The game is turn based. On your turn you should move the "ball" (card opened from your deck) to opponents goal. You start from the row that is close to your goal: you should select a card in a row and if it matches by value or suite - proceed to the next row up until the opponent's goal. If there is no match - your turn is over. You can select opened and closed cards. If the whole row is opened - you can skip it and procced to the next one. You score when your "ball" matches opponent goal. ## Temporal Transparency Update #8 DevFeed: [Temporal Transparency Update #8]() Original publisher: [Read original article]() Author: Ryland Goldstein Published: 2020-09-18T04:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Testing](), [Deployment Strategies](), [elasticsearch](), [Replication]() Tags: [announcements](), [deployment](), [strategies](), [testing](), [update]() ### AI overview Temporal's eighth transparency update reports that the V1 stabilization effort is code complete, required tests are running in the pipeline, some system components have been stabilized, and several features remain experimental for the V1 release. ### Source excerpt Hey Temporal community, it's Friday! It's been a long week but the end is almost here, but not before we share some exciting updates about Temporal. ## Technical Debt and Legacy Code: Techniques for Improving Code Health DevFeed: [Technical Debt and Legacy Code: Techniques for Improving Code Health]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2020-03-13T00:00:00Z Content type: opinion Language: en Sources: [Fernando Cejas Blog]() Topics: [Software Engineering](), [legacy](), [maintenance](), [Testing](), [Unit testing]() Tags: [android](), [clean-code](), [culture](), [development](), [engineering](), [how-to](), [infrastructure](), [ios](), [java](), [kotlin](), [legacy-code](), [linux](), [maintenance](), [open-source](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [strategies](), [technical](), [unit-testing](), [web-development]() ### AI overview This article examines technical debt and legacy code in software projects, defines legacy code as code without tests, and discusses techniques and strategies for assessing and addressing code health and maintenance challenges. ### Source excerpt As **Software Engineers** we know that **Technical Debt** and **Legacy Code** are familiar concepts we have to live with. **Code healthiness and maintenance are challenging**, so let's dive into **tips and techniques on how to effectively address this problem.** ## A Possible Solution To The Open Source Funding Problem DevFeed: [A Possible Solution To The Open Source Funding Problem]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2017-09-11T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Open Source](), [Software]() Tags: [bounty](), [open-source](), [open-source-software](), [projects](), [strategies]() ### AI overview The article discusses the open-source funding problem and considers bounty-based approaches as a possible partial solution. It argues that enabling people to get paid for developing open-source software is important to the future of the field. ### Source excerpt William Gross has posted Give Away Your Code, But Never Your Time, a potential and/or partial solution to the problem of funding open source projects, which I offered a solution for here. I've since heard from people pointing out projects that have actually used the "bounty" approach - I was unintentionally describing something that already exists. We've been solving all these other problems around open source, but not the essential one: how can people get paid for developing open-source software. ## Post-Mortem: Applied Image Optimization DevFeed: [Post-Mortem: Applied Image Optimization]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-12-07T18:11:00Z Content type: article Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Optimization](), [Image](), [Website](), [benchmarking]() Tags: [applying](), [benchmarking](), [image](), [loading](), [optimization](), [performance](), [post-mortem](), [post-mortems](), [project](), [results](), [shows](), [speed](), [strategies](), [website]() ### AI overview This project post-mortem describes applying image optimization techniques to improve website loading performance. Lazy-loading below-the-fold images, responsive server-side image processing, progressive JPEGs, and HTTP/2 reduced load time from 107.8 seconds to 2.8 seconds, Start Render from 29.8 seconds to 1.4 seconds, and Visually Complete from 35.5 seconds to 1.7 seconds. ### Source excerpt This project post-mortem shows the results of applying image optimization strategies to speed up the loading of a website ## Effective Learning Strategies for Programmers DevFeed: [Effective Learning Strategies for Programmers]() Original publisher: [Read original article]() Published: 2015-10-10T22:15:00Z Content type: article Language: en Sources: [Allison Kaptur]() Topics: [Learning](), [Programming]() Tags: [effective](), [learning](), [programming](), [research](), [skills](), [strategies]() ### AI overview An article about effective learning for programmers, presented as an edited transcript of a Kiwi PyCon keynote. It introduces mindset and learning strategies, drawing on experiences at the Recurse Center and research on effective learning. ### Source excerpt In early September I gave a keynote at Kiwi PyCon in New Zealand on effective learning for programmers. There were two pieces to the talk: one about mindset, and one about particular strategies we can use. The text below is an aspirational and lightly edited transcript of the mindset piece of that talk. There's also a video available if you'd like to see the strategies piece. Recurse Center Before I joined Dropbox last year, I spent two years working at a company in NYC called the Recurse Center. The Recurse Center is like a writers' retreat for programmers. Participants spend 3 months working on whatever is most interesting to them. So someone who'd been writing Java for ten years might come to RC to learn a new language like Clojure, or someone who just graduated with a CS degree might come work on their web development skills, or someone who'd been learning programming in their spare time might come to turbo-charge their learning. There's almost no structure to the program - no deadlines, no assignments, no teaching. It's an experiment in unstructured learning for adults. My role as a facilitator was to help people make the most of that disorienting amount of freedom that they had at RC. People who come out of traditional educational experiences or traditional jobs very often don't know what to do with that. So I'd help them with goal-setting and help them make the most of the experience. One of the things we thought a lot about was how to have the most effective learning experience possible for programmers. Today I'll talk about some of the research into how to be an effective learner, and how we can apply that research to our daily lives as programmers and engineers. What to get out of this post Take a minute and consider what you'd like to get out of this post. You might want to learn something new about how to be as efficient and effective in your job as possible. You might want to hear about how you can be a better teacher or mentor to junior engineers. Or y ## Relational Database Design DevFeed: [Relational Database Design]() Original publisher: [Read original article]() Author: Justin Oakley (justin.oakley@zumba.com) Published: 2015-05-22T00:00:00Z Content type: tutorial Language: en Sources: [Zumba]() Topics: [Database](), [Databases](), [Structured-data]() Tags: [database](), [schema](), [strategies]() ### AI overview An article presents conventions and strategies for designing a relational database schema that can grow with an application and organization. ### Source excerpt Conventions and strategies to create a schema that will grow with your application and organization.