# progress Published articles for progress. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build Trust on a Short Software Project DevFeed: [Build Trust on a Short Software Project]() Original publisher: [Read original article]() Author: Viviana Rosas Published: 2026-09-17T12:00:17Z Content type: opinion Language: en Sources: [Atomic Object]() Topics: [trust](), [Software](), [Testing]() Tags: [client](), [progress](), [project](), [project-communication](), [project-team-management](), [regression](), [testing](), [the-software-life](), [trust]() ### AI overview This article explains how software teams can build client trust during short projects. It recommends frequent feedback and check-ins, making progress visible, and using a limited regression test suite focused on important functionality. ### Source excerpt On a short project, clients need evidence not only that work is happening, but that the team knows when to continue, when to change direction, when to raise concern, and how to leave others capable of carrying the work forward. 1. Close the Feedback Loop - Show Responsiveness. It's extremely important to get feedback quickly [...] The post Build Trust on a Short Software Project appeared first on Atomic Spin. ## Cutting the Noise. DevFeed: [Cutting the Noise.]() Original publisher: [Read original article]() Author: David Pereira Published: 2026-08-13T12:29:59Z Content type: opinion Language: en Sources: [Untrapping Product Teams]() Topics: [meetings](), [Processes]() Tags: [focus](), [meetings](), [processes](), [progress](), [simplify](), [workflow]() ### AI overview This opinion article argues that professional growth can come from "adding by subtracting": questioning routines, processes, meetings, and other work practices that no longer serve their original goals. It identifies predictability and stability as factors that can reduce progress and innovation. ### Source excerpt What can you stop doing now? ## EU & Civil Society need to progress on Digital Autonomy DevFeed: [EU & Civil Society need to progress on Digital Autonomy]() Original publisher: [Read original article]() Published: 2026-06-15T13:00:00Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [digital sovereignty](), [digital](), [Software]() Tags: [digital-autonomy](), [digital-sovereignty](), [eu](), [government](), [influence](), [people](), [progress]() ### AI overview The article argues that European discussions about digital autonomy and sovereignty are stalled and need to move beyond legislation and references to European values. It calls for broader civil-society involvement, including procurement officials, IT departments, vendors, and government executives, to support practical progress. ### Source excerpt By now (happily) everyone wants to talk about digital autonomy, although some parties insist we talk about sovereignty. Fine. tl;dr: The discussions on digital autonomy are now going round in circles. Civil society and think tanks want to contribute, and are well placed to do so. In this piece, I urge everyone to look further ahead, beyond legislation and talking about European values. The road to digital sovereignty is very long, and we need to make progress along that entire road, which includes things further afield than what we are discussing now. ## How to lead a project DevFeed: [How to lead a project]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2025-11-19T00:00:00Z Content type: tutorial Language: en Sources: [Swizec Teller]() Topics: [task management](), [To-Do]() Tags: [how-to](), [practical](), [progress](), [project](), [real-time](), [review](), [scope](), [task-management](), [team](), [weekly]() ### AI overview A practical guide to leading a project by defining its outcome, target date, and scope; organizing work in a task management system; meeting weekly with stakeholders; and shipping work in small, reviewable increments. ### Source excerpt you were asked to lead or own a project. Now what? Here are a few practical steps to help you succeed. ## SharedFlow vs StateFlow DevFeed: [SharedFlow vs StateFlow]() Original publisher: [Read original article]() Published: 2024-06-27T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [LineageOS](), [Back end](), [WebSocket]() Tags: [android](), [backend](), [exceptions](), [kotlin](), [messages](), [parameter](), [progress](), [service](), [sharedflow](), [state](), [stateflow](), [users](), [value](), [websocket](), [workshop-learning-programming]() ### AI overview This tutorial explains the distinction between Kotlin's StateFlow and SharedFlow. StateFlow represents observable application state, while SharedFlow broadcasts events to observers. It discusses replay, required initial values, distinct updates, conflation, and examples for Android and backend services. ### Source excerpt When to use SharedFlow and when to use StateFlow. ## How I build side projects DevFeed: [How I build side projects]() Original publisher: [Read original article]() Author: Tiger Abrodi Published: 2024-03-23T10:12:46Z Content type: tutorial Language: en Sources: [Saiyan Growth Letter]() Topics: [Requirements](), [Figma](), [GitHub](), [Deployment](), [Vercel]() Tags: [deployment](), [figma](), [github](), [how-to](), [progress](), [requirements](), [side-projects]() ### AI overview The author presents an end-to-end process for building side projects: define and reduce requirements to a minimal viable product, sketch and design the interface, build iteratively, deploy early with automatic deployment, and test where appropriate. ### Source excerpt My strategic end-to-end approach for building side projects ## 11 Aspects Most Startups Get Wrong About OKRs and How to Fix it DevFeed: [11 Aspects Most Startups Get Wrong About OKRs and How to Fix it]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-02-24T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Framework](), [Tool](), [implementation](), [Google](), [intel]() Tags: [alignment](), [andy-grove](), [article](), [engineering-leadership-goal-setting-leadership-product-management-engineering-excellence](), [focus](), [framework](), [google](), [growth](), [intel](), [mistakes](), [objectives](), [organization](), [progress](), [startups](), [tool]() ### AI overview This article explains what OKRs are, defines objectives, key results, and initiatives, and discusses why startups may implement OKRs unsuccessfully. It recommends first identifying the problems an organization wants to solve and adjusting the approach to fit its needs. ### Source excerpt 11 Aspects Most Startups Get Wrong About OKRs and How to Fix it Objectives and key results (OKRs) can be a powerful tool. But as with any framework or methodology out there, just applying it as others do will likely not yield the best results. It can even harm your organization. ## Temporal Schedules: Reliable, scalable, and more flexible than Cron jobs DevFeed: [Temporal Schedules: Reliable, scalable, and more flexible than Cron jobs]() Original publisher: [Read original article]() Author: Irina Belova Published: 2023-11-15T07:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Job](), [Scalability](), [Monitoring](), [observability]() Tags: [execution](), [monitoring](), [observability](), [product-news](), [progress](), [scalability](), [scheduling](), [temporal]() ### AI overview Temporal announces the general availability of Temporal Schedules, a replacement for traditional Cron jobs. The feature supports durable task execution, workflow controls, progress insight, observability, flexible intervals, and reduced reliance on external scheduling systems. ### Source excerpt Replace traditional Cron jobs with Temporal Schedules for durable task execution, progress insights, and enhanced scalability. ## Temporal Transparency Update #2 DevFeed: [Temporal Transparency Update #2]() Original publisher: [Read original article]() Author: Ryland Goldstein Published: 2020-07-18T04:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Code](), [GitHub](), [GitHub Issues]() Tags: [github](), [github-issues](), [product-news](), [progress](), [release](), [transparency](), [update]() ### AI overview Temporal's second V1 status update says the July 31, 2020 code-completion date remains unchanged. The team added tasks from open issues in public GitHub repositories, prioritized the remaining work, and expected many in-progress items to be completed that week. ### Source excerpt Hope everyone is having a great Friday. I'm happy to share our second V1 status update as part of our continued effort to be more transparent. ## el-get 2.2 DevFeed: [el-get 2.2]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2011-05-26T10:00:00Z Content type: release Language: en Sources: [Dimitri Fontaine]() Topics: [maintenance](), [Git]() Tags: [git](), [maintenance](), [progress](), [release](), [source](), [stable]() ### AI overview The el-get 2.2 release followed cleanup of a source-tree discrepancy caused by a work-in-progress patch landing in Git before the stable release. The project then branched a stable maintenance tree and released version 2.2. ### Source excerpt We've spotted a little too late for our own taste a discrepancy in the source tree: a work in progress patch landed in git just before to release el-get stable. So we cleaned the tree (thanks again Julien), branched a stable maintenance tree, and released 2.2 from there. You're back to enjoying el-get :) ## WPF/Silverlight visual states with DataTemplates DevFeed: [WPF/Silverlight visual states with DataTemplates]() Original publisher: [Read original article]() Author: Andrew Khmylov Published: 2010-11-19T00:00:00Z Content type: tutorial Language: en Sources: [Despite the odds]() Topics: [WPF](), [XAML](), [MVVM](), [ui]() Tags: [mvvm](), [progress](), [screen](), [state](), [threading](), [xaml]() ### AI overview This tutorial presents a WPF technique for switching among page, window, or control states by defining different DataTemplates. It contrasts this approach with VisualStateManager and Silverlight Activity Control, then demonstrates a welcome screen and a busy-progress state backed by a ViewModel. ### Source excerpt Consider a common task - you need to switch between different screens in your application, that represent various states (e.g. Normal/Loading/Error). How are you going to implement this? You can start with VisualStateManager and define appropriate visual states. Well, this will surely do the thing, but you will have to create lots of controls and manage their Visibility or Opacity. And what if you have a complex markup? And I suppose that switching the state will not remove invisible items from the visual tree. And even more, with VisualStateManager you are bound to Expression Blend, because, you know, it's not very convenient to edit VSM settings by hands in XAML (which I prefer, but it is a topic for another article). The second option that may fit well, if you just need something like "I'm busy!" overlay is Silverlight Activity Control. Works like a charm with RIA services, but I find it limited for complex scenarios (and it's not available for WPF). I've found another approach (it becomes especially useful with MVVM and improved DelegateCommand implementations - I will blog about this in a few days). The idea behind this technique is quite simple. You define different templates for different page/window/control states. Yeah, that's it. Let's start with our implementation. Our application will have only one page with 2 different states: A welcome screen, that hosts a button to start 'the heavy' calculation. Busy window" that shows information about the current processing progress. I decided to create a simple ViewModel as a backing storage for our UI properties. It has two properties - IsBusy that says whether some hard work is executing now, and Progress - simple execution progress indicator. Method StartCalculation runs a new thread executes a number of loop steps. On each step the executing thread is suspended for 100ms (to imitate a slow operation). Normally you will create a DelegateCommand that will handle all the execution logic, but I decided to keep thin