# continuous Published articles for continuous. 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 to Make Team Retrospectives Effective DevFeed: [How to Make Team Retrospectives Effective]() Original publisher: [Read original article]() Author: Domenico Luciani Published: 2025-11-02T23:00:00Z Content type: opinion Language: en Sources: [Domenico Luciani]() Topics: [retrospectives]() Tags: [continuous](), [effective](), [retrospective](), [self-improvement](), [team](), [team-dynamics]() ### AI overview This opinion article explains how team retrospectives can support learning, self-improvement, idea sharing, celebration, and continuous improvement. It emphasizes psychological safety, focusing on processes rather than blaming people, and adapting the retrospective format to the team's situation. ### Source excerpt A team retrospective is not just another useless meeting, and if you feel so, it means you are doing it wrong, and this article is for you. ## Build resilient Agentic AI with Temporal DevFeed: [Build resilient Agentic AI with Temporal]() Original publisher: [Read original article]() Author: Tim Imkin Published: 2025-02-25T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Artificial Intelligence](), [Orchestration](), [reliability](), [Scalability](), [retry](), [real-time](), [Processes](), [SDK](), [context]() Tags: [agentic-ai](), [agents](), [ai-agents](), [continuous](), [durability](), [metrics](), [orchestration](), [state-management](), [temporal-concepts]() ### AI overview This tutorial explains how Temporal supports durable, scalable Agentic AI workflows that can preserve state, involve humans, schedule execution, provide observability, and recover from failures through retries. ### Source excerpt Learn how Temporal powers durable, scalable Agentic AI workflows with reliable state management, human-in-the-loop, and seamless orchestration. ## The foundations of Canva's continuous data platform with Snowpipe Streaming DevFeed: [The foundations of Canva's continuous data platform with Snowpipe Streaming]() Original publisher: [Read original article]() Author: Jack Caperon Published: 2025-01-06T00:00:01Z Content type: article Language: en Sources: [Canva Engineering]() Topics: [Streaming](), [product analytics](), [data-platforms](), [Amazon S3](), [Serverless]() Tags: [analytics](), [continuous](), [data](), [data-platform](), [partitioning](), [performance](), [s3](), [snowflake](), [streaming]() ### AI overview Canva describes how it is building a continuous data platform with Snowpipe Streaming to support product analytics as its user base, workforce, and data volume grow. The article discusses schema management, streaming changes, cost reduction, and the limitations of its previous AWS Data Firehose-based approach. ### Source excerpt Leveraging Snowpipe Streaming to build a continuous data platform. ## 💚 Big Changes - Continuous Improvement DevFeed: [💚 Big Changes - Continuous Improvement]() Original publisher: [Read original article]() Author: Richard Donovan Published: 2024-01-27T10:42:55Z Content type: opinion Language: en Sources: [The Modern Software Developer]() Topics: [Software Engineering](), [Development](), [Test-driven development]() Tags: [changes](), [continuous](), [efficiency](), [software-developer](), [software-development](), [test]() ### AI overview The author describes applying continuous improvement to a software development newsletter by making the writing more concise, increasing publishing frequency gradually, using a consistent template, focusing on smaller topics, and helping readers act on the content. The article connects this approach to software development feedback loops and test-driven development. ### Source excerpt Words: < 1050 - Read time: < 5 mins ## How To Create A Culture Of Continuous Improvement In Mobile Engineering Teams DevFeed: [How To Create A Culture Of Continuous Improvement In Mobile Engineering Teams]() Original publisher: [Read original article]() Author: Sarah Gruneisen Published: 2023-07-17T15:44:29Z Content type: tutorial Language: en Sources: [Novoda]() Topics: [Mobile](), [mobile devops](), [DevOps](), [Learning]() Tags: [continuous](), [devops](), [engineering](), [how-to](), [mobile-engineering](), [scaling](), [teams]() ### AI overview This article explains how mobile engineering teams can build a culture of continuous improvement through reflection, adaptation, and iterative work. It discusses the risks of scaling immature processes or over-engineering products, and describes continuous improvement as a way to support effective growth. ### Source excerpt Having a culture of continuous improvement within your mobile developer teams ensures you remain effective as you scale - and most importantly, that you don't scale problems with solutions. The post How To Create A Culture Of Continuous Improvement In Mobile Engineering Teams appeared first on Novoda. ## Crucial developer practices: Decoupling deployments and releases DevFeed: [Crucial developer practices: Decoupling deployments and releases]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2021-11-27T12:02:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [feature flags](), [Deployment](), [releases](), [systems](), [Risk](), [Testing]() Tags: [continuous](), [continuous-deployment-software-development-software-craft](), [decoupling](), [deployments](), [developer](), [feature-flags](), [practices](), [risk](), [test](), [testing]() ### AI overview The article explains why growing systems should decouple deployments from releases. It focuses on release toggles, a type of transient feature flag that lets developers change application behavior at runtime, gradually roll out changes, roll them back, and test in production without breaking the system. ### Source excerpt Crucial developer practices: Decoupling deployments and releases When systems are small and the risk of introducing defects when changing its behaviour is low, these changes can happen during deployment. However, when systems grow, the behaviour becomes more complex and more people are working on the system, it is essential to decouple behaviour changes, the releases, from deployments. ## Mobile NixOS Project Progress During 2020 DevFeed: [Mobile NixOS Project Progress During 2020]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2021-01-11T00:00:00Z Content type: article Language: en Sources: [Mobile NixOS news]() Topics: [Mobile](), [Nix](), [modules](), [CI/CD](), [pull-requests]() Tags: [continuous](), [mobile](), [modules](), [pull-requests]() ### AI overview A retrospective on Mobile NixOS progress during 2020, covering project activity, stage-1 improvements, continuous delivery builds, and expanded device support. ### Source excerpt The year 2020 was my first full calendar year dedicated to working on the Mobile NixOS project. Let's look at the progress, from the state of the project before January 2020, up to the state after December 2020. Comparisons will start from the last commit of 2019, 7803d9ec0e35fe602f75d08e6bcb6db720ad897c. They are compared against the last commit for 2020, d5869523869eb029b712a3f2b7b1c3199874f221. You might also be interested in looking at all the merged pull requests for 2020. Some numbers They're quite arbitrary. I don't know what other relevant stats could be used here. 111 merged pull requests 805 commits (skipping merge commits) 10 commit authors (filtering duplicates) Devices: 10 -> 16 Modules: 39 -> 56 (Nix files in modules/) And here's what cloc reveals: [nix-shell:~/.../mobile-nixos/2019]$ cloc . 274 text files. 263 unique files. 36 files ignored. -------------------------------------------------------------------------------- Language files blank comment code -------------------------------------------------------------------------------- diff 55 741 2623 16308 Nix 108 719 772 4311 SVG 7 4 4 2950 LESS 24 263 333 1257 Ruby 16 147 85 706 AsciiDoc 7 130 3 243 XML 5 19 12 160 ERB 8 4 0 89 Markdown 4 43 0 85 Lua 1 15 41 58 Bourne Again Shell 2 9 10 21 C/C++ Header 1 13 35 21 C 1 1 0 17 -------------------------------------------------------------------------------- SUM: 239 2108 3918 26226 -------------------------------------------------------------------------------- [nix-shell:~/.../mobile-nixos/2020]$ cloc . 482 text files. 463 unique files. 54 files ignored. -------------------------------------------------------------------------------- Language files blank comment code -------------------------------------------------------------------------------- diff 89 1429 5081 22047 Nix 170 1266 1149 7576 Ruby 76 690 575 4132 SVG 10 4 4 3538 LESS 25 291 334 1413 JSON 6 0 0 959 AsciiDoc 25 396 3 844 XML 5 19 12 160 Markdown 8 88 0 159 ERB 10 23 0 130 Lua 1 15 41 58 YA ## Atomic Deployments Without Tears DevFeed: [Atomic Deployments Without Tears]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-06-30T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [CI/CD](), [Deployment](), [Git](), [Content Management System](), [Development]() Tags: [amazon-s3](), [atomic](), [automatically](), [changes](), [continuous](), [continuous-integration](), [deploy](), [deployments](), [downtime](), [git](), [how-to](), [insights](), [integration](), [learn](), [safely](), [tools](), [using](), [website](), [zero]() ### AI overview This tutorial explains how to use Continuous Integration tools to perform atomic, zero-downtime deployments for Craft CMS websites. It covers a workflow based on local development, a cloud Git repository, and automated deployment to production or staging servers. ### Source excerpt Learn how to use atomic deployments to automatically and safely deploy changes to your website with zero downtime using Continuous Integration (CI) tools ## Managing fatigue during continuous and sustained operations DevFeed: [Managing fatigue during continuous and sustained operations]() Original publisher: [Read original article]() Author: Graham King Published: 2006-01-01T13:59:05Z Content type: article Language: en Sources: [Graham King]() Topics: [maintenance]() Tags: [behaviour](), [blog-post](), [continuous](), [maintenance](), [performance](), [research](), [strategy]() ### AI overview This article explains how sleep loss, disrupted circadian rhythms, and hard work cause fatigue during continuous and sustained operations. It describes fatigue-management practices including short power naps, while noting that cumulative sleep debt eventually overwhelms performance. ### Source excerpt Awake, alert, and ready to tackle the day - a blog post on staying sharp during continuous operations