# development-process Published articles for development-process. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kanbanning the LearnStorm Dev Process DevFeed: [Kanbanning the LearnStorm Dev Process]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-12-07T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Development]() Tags: [dev](), [development](), [development-process](), [engineering](), [news](), [projects](), [web-frontend]() ### AI overview Kevin Dangoor describes how Khan Academy's LearnStorm initiative changed its development process from project-based planning with Trello and Google Sheets to task-focused tracking in Google Docs and Asana as launch requirements evolved. ### Source excerpt By Kevin Dangoor In his New Employee's Primer post from July, Riley Shaw wrote a little about our ... Read more ## Ubisoft debuts Player Council platform to expand early game development feedback DevFeed: [Ubisoft debuts Player Council platform to expand early game development feedback]() Original publisher: [Read original article]() Author: Bryant Francis Published: 2026-08-26T15:50:50Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [Game Development](), [Development]() Tags: [2026](), [communication](), [development-process](), [external](), [game-development](), [gamescom](), [multiplayer](), [platform](), [play](), [projects](), [prototype](), [prototypes]() ### AI overview Ubisoft has launched The Player Council, a platform that invites players to provide feedback on early concepts, prototypes, and live experiences. The initiative is intended to involve players before games reach the first playable prototype stage and includes projects such as Codename Split Point and Codename Rook. ### Source excerpt Player Council members will be invited to test 'early concepts, prototypes, and live experiences.' ## Design and Planning Are the Key Skills for Building Software with AI Coding Agents DevFeed: [Design and Planning Are the Key Skills for Building Software with AI Coding Agents]() Original publisher: [Read original article]() Author: Owain Lewis Published: 2026-08-14T12:12:26Z Content type: article Language: en Sources: [The AI Engineer]() Topics: [AI-assisted coding](), [AI Development](), [Software Engineering](), [Development]() Tags: [agents](), [ai](), [ai-agents](), [ai-coding](), [coding-agents](), [design](), [development-process](), [requirements](), [verification]() ### AI overview The article argues that AI coding agents can handle much of software implementation, testing, and deployment. It says engineers should focus most on design and planning: defining requirements, making technical decisions, and breaking work into tasks agents can execute reliably. ### Source excerpt How to design better software and turn it into tasks AI agents can execute reliably. ## The xEngineer: A New Blueprint for Software Engineering in the AI Era DevFeed: [The xEngineer: A New Blueprint for Software Engineering in the AI Era]() Original publisher: [Read original article]() Author: Wix Engineering Published: 2026-03-16T09:25:50Z Content type: opinion Language: en Sources: [Wix Engineering]() Topics: [Software Engineering](), [AI-assisted coding](), [Artificial Intelligence](), [Claude Code](), [codex](), [cursor]() Tags: [ai](), [ai-tools](), [code](), [debugging](), [development-process](), [event](), [legacy](), [software-engineering](), [testing]() ### AI overview A Wix article presents the xEngineer as an emerging model of software engineering in the AI era. It argues that as coding assistants make code production more routine, engineers increasingly focus on defining problems, designing systems, orchestrating intelligent tools, and applying AI across the engineering lifecycle. ### Source excerpt Aviran Mordo, Yaniv Event Haim, Asaf Yonay For decades, the role of the software engineer seemed straightforward: identify a problem and solve it by writing code. But the rise of powerful AI models is beginning to reshape that definition. With systems like Claude Code, Codex, Cursor and other advanced coding assistants, something important has become clear across the industry: writing code itself is gradually becoming a commodity. This does not mean software engineering is becoming less... ## The Design Process and Agile Development: Part 1 -- Design Is Collaborative DevFeed: [The Design Process and Agile Development: Part 1 -- Design Is Collaborative]() Original publisher: [Read original article]() Author: Daisy Mølving Published: 2026-02-05T06:00:00Z Content type: opinion Language: en Sources: [8th Light Insights]() Topics: [Agile](), [User experience (UX)](), [Development](), [Self-organizing Team]() Tags: [agile](), [delivery-and-practice](), [design-thinking](), [development](), [development-process](), [experiential-design](), [product-strategy-innovation](), [research](), [teams](), [user-experience](), [ux-design]() ### AI overview Part 1 of a series examines how design thinking and UX research can work alongside Agile development. It argues that iterative design and Agile delivery are compatible, while noting the tension between research needs, rapid timelines, client goals, and incremental development. ### Source excerpt This is Part 1 in our blog series on how the design process works alongside Agile methodology to produce results within an integrated team. Updated 2/5/2026. Originally published 2/2/2024 When it comes to developing new software, not every designer approaches the task the same way. While some use a design thinking approach, looking at the tasks from a user perspective, others use Agile methods, approaching it from an iterative project management standpoint. However, the two approaches are not mutually exclusive. The most successful designers approach their tasks using design thinking which helps inform prioritization within the Agile methodology. High performing teams delivering outcomes through the agile methodology do so with confidence when they know solutions are informed by the voice of the user. Working with Design Thinking and Agile Timelines Designers who've worked alongside Agile methodologies have likely felt the pressure of Agile timelines conflicting with the need for comprehensive design. While the approaches may feel conflicting at first, it's important to remember that both design and Agile methodologies emphasize the importance of working in small iterations to develop products that constantly evolve-- focusing on the smallest modifications that lead to making valuable products and building upon them. However, with its need for preliminary research, I've observed that user experience (UX) design can give Agile practitioners the impression of a waterfall process. Agile teams want to deliver quickly and continue iterating on the project after receiving feedback. As a UX designer, it is my responsibility to establish and fulfil the human need by talking to some users and conducting competitor research before we dive blindly into development. Working as a UX designer in this environment can feel like you're stuck between a rock and a hard place. You have a client who cares about the bottom line and wants to get to market quickly and a development team of ## Software Development Waste DevFeed: [Software Development Waste]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-01-15T16:01:54Z Content type: article Language: en Sources: [Tech World With Milan Newsletter]() Topics: [software-development](), [Software Engineering](), [Agile](), [code productivity]() Tags: [agile](), [best-practices](), [cognitive-load](), [cross-functional-teams](), [development-process](), [productivity](), [quality](), [software-development](), [switching]() ### AI overview This article explains software development waste through lean thinking. It reviews the traditional seven wastes, discusses an expanded taxonomy that includes issues such as wrong features, backlog mismanagement, over-engineering, cognitive load, communication problems, and waste from AI-generated code, and presents practices for reducing waste. ### Source excerpt Many of us can look back at a completed software project and think, "If I'd known then what I know now, I'd have done much faster." This familiar feeling reveals just how much waste creeps into the software development process. ## Weird Junos IS-IS Metrics DevFeed: [Weird Junos IS-IS Metrics]() Original publisher: [Read original article]() Published: 2025-01-14T07:13:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [IS-IS](), [networking](), [Routing (disambiguation)](), [Development]() Tags: [development-process](), [is-is](), [netlab](), [router](), [routing](), [tests](), [validation]() ### AI overview The article investigates a failing netlab IS-IS metrics test on Junos. It explains that Junos uses transitional IS-IS metrics by default and silently limits configured narrow and wide metrics above 63, causing unexpected routing costs. Configuring wide-metrics-only on levels 1 and 2 resolves the test failure. ### Source excerpt As part of the netlab development process, I run almost 200 integration tests on more than 20 platforms (over a dozen operating systems), and the amount of weirdness I discover is unbelievable. Today's special: Junos is failing the IS-IS metrics test. The test is trivial: The device under test is connected to two IS-IS routers (X1 and X2) It has a low metric configured on the link with X1 and a high metric configured on the link with X2 The validation process is equally trivial: Read more ... ## Snyk Acquires Probely to Expand API Security Testing and Modern DAST DevFeed: [Snyk Acquires Probely to Expand API Security Testing and Modern DAST]() Original publisher: [Read original article]() Author: Manoj Nair Published: 2024-11-12T05:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Security](), [DevSecOps](), [Application Security](), [Testing](), [API](), [web applications](), [API Economy]() Tags: [api-economy](), [api-security](), [api-testing](), [application-security](), [awareness](), [blog](), [customer](), [development-process](), [devsecops](), [executive](), [genai](), [pipelines](), [pmm](), [security](), [shift-left](), [snyk-platform](), [testing](), [web-applications]() ### AI overview Snyk acquired Probely to expand its DevSecOps platform with API Security Testing and modern Dynamic Application Security Testing (DAST). The article explains how CLI-driven integration with CI/CD pipelines supports earlier testing in development workflows. ### Source excerpt Snyk acquires Probely to expand its DevSecOps platform with API Security Testing and modern DAST. Learn how this acquisition will help developers build and secure web applications faster. ## Deployment-Driven Development DevFeed: [Deployment-Driven Development]() Original publisher: [Read original article]() Published: 2024-11-11T22:57:13Z Content type: article Language: en Sources: [Brave New Geek]() Topics: [Deployment](), [Domain-driven design (DDD)](), [software-architecture](), [Platform Engineering](), [Testing](), [Tech Debt](), [sdlc]() Tags: [architecture](), [ddd](), [deployment](), [deployment-driven-development](), [development-process](), [devops](), [domain-driven-design](), [konfigurate](), [platform-engineering](), [qa](), [sdlc](), [security](), [tech-debt]() ### AI overview The article introduces Deployment-Driven Development as a complement to Domain-Driven Design, focusing on delayed feedback and delivery obstacles that affect software architecture, testing, security, compliance, and production readiness. ### Source excerpt Most people use "DDD" to refer to Domain-Driven Design, which is a useful tool for thinking about API boundaries and system architecture. It provides a way to map a business problem into software. At Real Kinetic, we regularly help our clients utilize Domain-Driven Design as well as other strategies to architect their systems, avoid some of the pitfalls of DDD, and build an effective foundation for designing software. But this DDD only speaks to one small aspect of building and shipping software. ## Revealing my 3 SaaS Products DevFeed: [Revealing my 3 SaaS Products]() Original publisher: [Read original article]() Author: Nelson Djalo Published: 2024-07-10T16:00:55Z Content type: opinion Language: en Sources: [Amigoscode Newsletter]() Topics: [Software as a service](), [Development](), [JavaScript](), [TypeScript](), [Supabase](), [Tailwind CSS](), [Firebase](), [GitHub](), [Figma](), [UI/UX Design](), [Git](), [Deployment]() Tags: [deployment](), [development](), [development-process](), [figma](), [firebase](), [git](), [github](), [javascript](), [saas](), [tailwind](), [tailwind-css](), [typescript](), [ui-ux-design]() ### AI overview The author describes building three SaaS products over six months, including the selected technology stack and the decision not to use Java for these projects. The stack includes Git, GitHub, JavaScript, TypeScript, Tailwind CSS, Supabase, Firebase, and Figma. ### Source excerpt Sneak Peek: 3 SaaS Products I'm About to Release! ## The fundamentals of iOS at Revolut DevFeed: [The fundamentals of iOS at Revolut]() Original publisher: [Read original article]() Author: Illia Kucheriavyi Published: 2024-05-14T11:41:25Z Content type: tutorial Language: en Sources: [Revolut Engineering]() Topics: [iOS](), [iOS development](), [feature flags](), [Mobile](), [SDKs](), [CI/CD](), [experiments](), [Development](), [Agile](), [Testing](), [releases]() Tags: [agile](), [continuous-delivery](), [continuous-integration](), [development](), [development-process](), [experiments](), [feature-flags](), [fundamentals](), [ios](), [ios-development](), [releases](), [revolut](), [sdks](), [software-engineering](), [testing]() ### AI overview This article describes Revolut's iOS development practices, covering its applications and SDKs, weekly App Store updates, continuous integration and delivery, feature flags, gradual rollouts, rollback procedures, and experimentation with statistical measurement. ### Source excerpt Let's take a look behind the scenes of the iOS development at Revolut, where we strive to provide exceptional financial services and seamless customer experiences for the customers who rely on our iOS apps to manage their financial lives. We believe that it's possible to deliver high-quality software, fast. To achieve this we follow a set of important principles and apply a number of modern agile practices, mainly inspired by XP (eXtreme Programming). Deliver fast Currently, on the iOS platform, we have both applications and SDKs. Here's a list of what's live: Revolut, Revolut <18, Revolut Business, Revolut POS and Revolut Pay SDK. All iOS applications are updated in the App Store on a weekly basis. We operate on the principles of continuous integration and continuous delivery to swiftly deliver new functionality to customers -- as soon as a feature or part of it is ready. We've built our own in-house framework for feature-based releases. According to our process, the Product Owner specifies a feature to be enabled starting from a selected version of the application. Then both the application version and its features are rolled out gradually, starting with a small percentage of our customer base. These two approaches -- feature flagging and gradual version and feature rollout -- enable delivering value to customers with the minimum amount of risk. If anything goes wrong, the flag will be turned off or the older version will be re-submitted as rollback, to remove the problematic change. Moreover, feature flags allow team members to easily switch between different user experiences, compare them, or turn them on and off for testing. We've also developed an in-house experimentation platform that allows teams to experiment with new features and measure their impact using predefined metrics in a statistically significant way. This platform guarantees that experiments are properly set up, and that results are produced using a robust statistical framework. All ideas are teste ## A Journey from Monolith to Micro frontends at Udemy -- Part 3 of 3 DevFeed: [A Journey from Monolith to Micro frontends at Udemy -- Part 3 of 3]() Original publisher: [Read original article]() Author: Hamza ERBAY Published: 2024-01-16T18:23:06Z Content type: article Language: en Sources: [Udemy Engineering]() Topics: [Front end](), [migration](), [Design system](), [GitHub Actions](), [Monitoring](), [npm packages](), [Hackathon]() Tags: [architecture](), [design-system](), [development](), [development-process](), [frontend](), [github-actions](), [micro-frontends](), [migration](), [monitoring](), [npm-packages](), [overcoming-obstacles](), [performance-metrics]() ### AI overview Part 3 of Udemy's series describes implementing a migration from a monolithic frontend to a more modular micro-frontend architecture. It covers migration guidance, shared design-system npm packages, team education, monitoring with Datadog and Sentry, simplified local development, and GitHub Actions-based releases. ### Source excerpt Transforming Frontend Architecture: A Journey from Monolith to Micro Frontends at Udemy -- Part 3 of 3 By: Chris Nienhuis, Hamza Erbay, Matthew Bise, Nathan Chapman, Seth Hodgson, Trey Briggs, Charles Pham Photo by Venti Views on UnsplashIntroduction In the previous section, we walked through the Udemy Hackathon event, and the decisions and preparations made that laid the foundation for our move toward a more modular frontend architecture. In this section, we will focus on the implementation of our vision post-Hackathon, how we are planning to execute the migration, and the impact it has had so far. If you missed Part 1 and Part 2 of this series, you can find them here: Transforming frontend Architecture: A Journey from Monolith to Micro frontends at Udemy -- Part 1... Transforming frontend Architecture: A Journey from Monolith to Micro frontends at Udemy -- Part 2... Post-Hackathon: Implementing the Vision Following the green light from the Shark Tank jury, we've taken decisive steps to translate our hackathon prototype into a scalable and robust frontend architecture. A dedicated frontend team has been formed at Udemy with the express purpose of driving this evolution. "Where the journey began... A throwback to the spark that ignited our incredible voyage. Thanks to Gregg (our former CEO) for recognizing the hard work! #Milestone #Hackathon #OriginStory" Our commitment to this new direction is reflected in a series of strategic actions: Migration Guidance: We've laid out clear guidelines for transitioning (transitioning implies migration) from the monolithic application, ensuring a smooth and structured shift to the new architecture. Collaboration with Design Systems: By partnering with the design system team, we've begun decoupling foundational components and design tokens, packaging them into shared npm packages. This initiative is critical for consistency and efficiency across all applications. Education and Alignment: Recognizing the importance of knowledge sharing, we ## Architecture Principles streamline development DevFeed: [Architecture Principles streamline development]() Original publisher: [Read original article]() Author: Mike Published: 2023-08-10T08:26:21Z Content type: tutorial Language: en Sources: [Dev Details]() Topics: [Development](), [Software Engineering](), [Software](), [decision-making]() Tags: [architecture](), [autonomy](), [decision-making](), [design](), [development-process](), [quality](), [reliability](), [software-development](), [user-experience]() ### AI overview The article explains that shared architectural principles can align developers, teams, and business leaders around software decisions. It argues that this alignment simplifies development, supports team autonomy, reduces technical debt, and improves software quality, reliability, scalability, and user experience. ### Source excerpt Architecture Principles guide the development, design, and operation of software systems. ## Why you should consider migrating your Gradle scripts to Kotlin DSL DevFeed: [Why you should consider migrating your Gradle scripts to Kotlin DSL]() Original publisher: [Read original article]() Published: 2023-05-10T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Gradle](), [Kotlin](), [domain-specific language](), [Development]() Tags: [build](), [code-analysis](), [code-completion](), [dependencies](), [development-process](), [dsl](), [gradle](), [interoperability](), [kotlin](), [migrate](), [workshop-learning-programming]() ### AI overview This article explains Gradle Kotlin DSL, describing its benefits over Groovy-based Gradle scripts, including static typing, code completion, type-safe APIs, concise syntax, and improved maintainability. It also outlines steps for migrating build scripts to Kotlin DSL. ### Source excerpt Discover the benefits of migrating your Gradle scripts to Kotlin DSL and streamline your development process. ## Double Fine Adventure documents the development of Broken Age DevFeed: [Double Fine Adventure documents the development of Broken Age]() Original publisher: [Read original article]() Author: Ole Begemann Published: 2023-01-31T18:39:27Z Content type: opinion Language: en Sources: [Ole Begemann]() Topics: [Development](), [Process]() Tags: [development](), [development-process](), [experience](), [financial](), [kickstarter](), [people](), [platforms](), [play](), [production](), [project](), [team](), [video](), [work](), [youtube]() ### AI overview This opinion article recommends the Double Fine Adventure documentary, which follows the three-year development of Broken Age and offers candid insight into game development, including financial problems, layoffs, and long work hours. It also discusses experiencing the documentary alongside the game. ### Source excerpt I know I'm almost a decade late to this party, but I'm probably not the only one, so here goes. Double Fine Adventure was a wildly successful 2012 Kickstarter project to crowdfund the development of a point-and-click adventure game and, crucially, to document its development on video. The resulting game Broken Age was eventually released in two parts in 2014 and 2015. Broken Age is a beautiful game and I recommend you try it. It's available for lots of platforms and is pretty cheap (10-15 euros/dollars or less). I played it on the Nintendo Switch, which worked very well. Broken Age. But the real gem to me was watching the 12.5-hour documentary on YouTube. A video production team followed the entire three-year development process from start to finish. It provides a refreshingly candid and transparent insight into "how the sausage is made", including sensitive topics such as financial problems, layoffs, and long work hours. Throughout all the ups and downs there's a wonderful sense of fun and camaraderie among the team at Double Fine, which made watching the documentary even more enjoyable to me than playing Broken Age. You can tell these people love working with each other. I highly recommend taking a look if you find this mildly interesting. The Double Fine Adventure documentary. The first major game spoilers don't come until episode 15, so you can safely watch most of the documentary before playing the game (and this is how the original Kickstarter backers experienced it). However, I think it's even more interesting to play the game first, or to experience both side-by-side. My suggestion: watch two or three episodes of the documentary. If you like it, start playing Broken Age alongside it. ## Introducing Public Design Specs DevFeed: [Introducing Public Design Specs]() Original publisher: [Read original article]() Author: Sterling Greene Published: 2022-12-07T05:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Open Source](), [Development](), [Google]() Tags: [contributions](), [development-process](), [gradle](), [open-source](), [specifications]() ### AI overview Gradle has made its design specifications publicly available through a Google Drive folder to make development of new features more open and transparent. The documents are a work in progress, and community members can comment on in-progress specifications to provide feedback and help guide future contributions. ### Source excerpt Gradle Build Tool is an open source project, but a lot of the design work has not been as visible as it could be. Internally, we use design specifications to collaborate on new Gradle features. To make our development process more open and transparent, our design specifications are publicly available via a Google Drive folder. This is still a work-in-progress and new documents will be added over time. We welcome community members to take a look. You can comment and provide feedback on all documents still In-Progress. We plan to use these documents to help guide new community contributions. Feel free to link to these documents in GitHub or share them with others. Along with the public roadmap, we hope opening up the behind-the-scenes work will provide more insight into our future plans. Please let us know if you have any questions or feedback. You can always reach out to us on Community Slack. ## Converting Gradle convention plugins to binary plugins DevFeed: [Converting Gradle convention plugins to binary plugins]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2022-04-17T06:30:00Z Content type: tutorial Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Gradle](), [configuration](), [build performance](), [modules](), [Maven](), [Android Library]() Tags: [build](), [compilation](), [configuration](), [convention-plugins](), [dependencies](), [development-process](), [gradle](), [incremental](), [maven](), [modules](), [plugins](), [publishing]() ### AI overview This tutorial explains why Gradle convention plugins may be converted into binary plugins. It discusses IDE support and incremental build issues, then describes distributing plugins as Maven dependencies to avoid repeated compilation and simplify reuse across projects. ### Source excerpt Gradle's convention plugins are a fantastic way to share common build configuration, why not take them a step further? ## 11 Authorization Best Practices DevFeed: [11 Authorization Best Practices]() Original publisher: [Read original article]() Author: sakshyam.shah@goteleport.com (Sakshyam Shah) Published: 2022-03-22T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Authorization](), [Access Control](), [Vulnerabilities](), [Security](), [Development]() Tags: [access-control](), [authorization](), [best-practices](), [development-process](), [scope](), [security](), [vulnerabilities](), [web]() ### AI overview This article presents 11 authorization best practices for reducing vulnerabilities and resisting attack vectors. It recommends designing authorization early, using middleware on every request, applying fine-grained policies with deny-by-default behavior, and limiting feature scope. ### Source excerpt This blog post recommends 11 authorization best practices to avoid vulnerabilities and defeat specific attack vectors. ## Kotlin Code Review: Avoiding Unproductive Nitpicking Over Concise and Idiomatic Code DevFeed: [Kotlin Code Review: Avoiding Unproductive Nitpicking Over Concise and Idiomatic Code]() Original publisher: [Read original article]() Published: 2020-10-14T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Code review](), [Kotlin](), [code style](), [Development]() Tags: [code-review](), [code-style](), [development-process](), [kotlin](), [quality]() ### AI overview This article examines how code review can become unproductive when reviewers focus excessively on style, concision, or idiomatic Kotlin patterns. It discusses the trade-offs behind some Kotlin constructs and argues that shorter code is not automatically better. ### Source excerpt Introduction Code review is an essential tool for a development team, which helps ensure high-quality standards of code. While reviewing others' code one might find bugs, design issues, and so on. One another part of reviewing is getting used to the codebase and following team's code style for better maintenance. Though it is pretty cool in theory, in practice team might face few issues, one of which is nitpicking. When review is bloated with dozens of similar comments related to e.g. how beautifully code looks like. Common code style is important, but having a lot of similar comments in each review doesn't help. Instead of trying to understand what code is doing, nitpicker writes a lot of similar comments on the style. Back and forth discussions or fixes of such slow down development process and overall make team's morale worse. ## Includes No Dirt: Healthcare Threat Modeling (Thursday) DevFeed: [Includes No Dirt: Healthcare Threat Modeling (Thursday)]() Original publisher: [Read original article]() Author: Adam Published: 2019-10-31T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [Security & Privacy](), [risk-management](), [Development]() Tags: [development-process](), [healthcare](), [risk](), [risk-management](), [security](), [security-privacy]() ### AI overview A commentary on the "Includes No Dirt" threat modeling approach by William Dogherty and Patrick Curry of Omada Health. The article describes its focus on security, privacy, and compliance, outlines the NO DIRT model and supporting worksheets, and discusses its potential use in development and vendor risk management. ### Source excerpt "Includes No Dirt" is a threat modeling approach by William Dogherty and Patrick Curry of Omada Health, and I've been meaning to write about it since it came out. ## Namespacing in Kotlin DevFeed: [Namespacing in Kotlin]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2019-07-29T00:00:00Z Content type: tutorial Language: en Sources: [Artur Dryomov]() Topics: [Kotlin](), [Code](), [Development]() Tags: [architecture](), [c-plus-plus](), [c-sharp](), [classes](), [code](), [components](), [development-process](), [java](), [kotlin](), [php](), [typescript](), [view](), [viewmodel]() ### AI overview This article examines how to represent a fractal component structure in Kotlin, focusing on naming and namespace-like organization. It compares several implementation approaches, including their Java representations, compiler behavior, object creation, inheritance, semantics, and generated size. ### Source excerpt The development process is a research. Find the state machine, organize mutations, wire it for consumers. The process repeats and leads to the meta-research. We investigate scenarios and search for reusable parts. Patterns arise, implementations follow. Ideally, the code resembles a fractal structure. An architecture is said to be fractal if subcomponents are structured in the same way as the whole is. -- André Staltz The Problem Let's say we have a fractal components structure. Each one has a View and a ViewModel. ## It's not just Standing Up DevFeed: [It's not just Standing Up]() Original publisher: [Read original article]() Published: 2019-01-11T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [Self-organizing Team](), [Development](), [Software Engineering](), [dashboards]() Tags: [agile](), [article](), [developers](), [development](), [development-process](), [scrum](), [self-organizing-team](), [software-development](), [software-process](), [standup-meeting](), [talk](), [team]() ### AI overview The article argues that people and organizational practices are at least as important as technical skills in software development. It presents notes on effective daily standups, emphasizing self-organizing teams, work-item-focused discussion, communication, impediment tracking, varied speaking order, suitable timing, and maintaining productivity. ### Source excerpt Lorem ipsum dolor sit amet ## Patterns for Major Dependency Upgrades DevFeed: [Patterns for Major Dependency Upgrades]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2018-03-18T00:00:00Z Content type: article Language: en Sources: [Artur Dryomov]() Topics: [upgrade](), [RxJava](), [Development](), [Software]() Tags: [dependencies](), [development-process](), [libraries](), [maintainers](), [rxjava](), [upgrade]() ### AI overview The article discusses patterns for major dependency upgrades, using RxJava's transition and EOL as a central example. It explains that major upgrades can drastically change APIs, break code, consume substantial time, affect development processes, and require careful consideration of benefits and migration costs. ### Source excerpt RxJava 1.x reaches EOL on March 31, 2018, meaning no further development. That's not surprising since the 1.x was in a bugfix-only mode since June 1, 2017. This is an interesting event in a software lifetime, since not so many libraries actually live and prosper long enough to produce a superior version, at the same time handling support for an older version for so long. Fortunately enough, RxJava is one of these lucky projects with maintainers actually caring about users. Thank you, RxJava maintainers, you are real human beings and real heroes. ## Holacracy - Whatˋs The Fuss About? Part 1 DevFeed: [Holacracy - Whatˋs The Fuss About? Part 1]() Original publisher: [Read original article]() Author: Peter Krauß (peter.krauss@upday.com) Published: 2017-06-26T19:39:55Z Content type: opinion Language: en Sources: [Upday]() Topics: [Agile](), [Development](), [Self-organizing Team]() Tags: [agile](), [culture](), [development-process](), [efficiency](), [rules]() ### AI overview This article examines Holacracy as an alternative to traditional hierarchical management. It describes principles such as distributed decision-making, defined responsibilities, and a constitution of organizational rules, while noting that Holacracy is not a universal solution. ### Source excerpt What is the right approach to being as happy, productive and as innovative as possible? Well, I guess this question pops up in many companies and there are many books out there trying to give an answer to this question. However, I deeply believe there is not one answer "to bind them all". However some principles are helpful to create a healthy environment - this means for us updudes: you need independence to make your own decisions you need to know what you are responsible for you need to know what you can expect from others and what they are responsible/accountable for If all these conditions are met, the probability you finish your task with the highest quality and efficiency is high - and you may even have some fun in the meantime. One guide that everyone is talking about in the moment is Holacracy. So we decided to have a closer look. And what did we realize? It is not the "Silver Bullet" to solve all our problems! (What a surprise!) But Holacracy offers many tools we started using to come closer to our Garden of Eden. In the next sections I will describe some key aspects of Holacracy. Our experiences will be part of a follow-up post. The CTO is Dead - Long Live The Constitution The classical hierarchical system - one person is in charge and takes all the decisions - worked pretty well for a few hundred years. It assumes this person is able to take the best possible decisions because he or she foresees every requirement and fully understands the big picture. This might be true for assembly lines producing simple things. But it already becomes unlikely if you think about fully automated, robot-controlled assembly lines in car production. It is completely impossible in an agile and fast changing software development process. What could be the alternative? Anarchy, grass-roots democracy based decisions or maybe hiring an almighty genius who knows everything? But this would be the omniscient leader again... And how would you know he/she knows everything? The answer Ho [Next page]()