# Good Practices Published articles for Good Practices. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Using coding agents as modular components in developer tools DevFeed: [Using coding agents as modular components in developer tools]() Original publisher: [Read original article]() Author: Leonidas Partsas Published: 2026-03-18T17:51:32Z Content type: opinion Language: en Sources: [le0nidas]() Topics: [coding](), [Tooling](), [Terminal](), [Git](), [Bash]() Tags: [agent](), [ai](), [bash](), [beads](), [coding](), [git](), [good-practices](), [open-code](), [opencode](), [productivity](), [thoughts](), [workflow]() ### AI overview The article argues that coding agents should be embedded as focused components within developer tools rather than treated as monolithic tools. It illustrates the approach by decomposing an OpenCode-based commit workflow into Bash scripts and a custom agent, following single-responsibility and composability principles. ### Source excerpt Or to be more exact, use a coding agent in a tool. This is my new starting point every time I begin to think of a tool I want to implement. Being part of the pipeline A couple of weeks ago I thought of creating an OpenCode agent that will check my uncommitted changes, construct ... Continue reading Use AI _in_ a tool not _as_ a tool -> ## Using timeboxing and scarcity as constraints when shipping software DevFeed: [Using timeboxing and scarcity as constraints when shipping software]() Original publisher: [Read original article]() Author: Jorge Manrubia Published: 2024-09-09T17:00:00Z Content type: opinion Language: en Sources: [37signals Dev]() Topics: [Development]() Tags: [developers](), [development](), [good-practices](), [scope]() ### AI overview The article argues that shipping software requires accepting that time and development bandwidth are limited. It presents timeboxing and scarcity as constraints that help teams prioritize, simplify work, and make practical decisions about scope. ### Source excerpt If neither time nor development bandwidth is a concern, how would you make the right calls? ## The Soft Side of Software Design DevFeed: [The Soft Side of Software Design]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-06-01T11:11:37Z Content type: article Language: en Sources: [Thinking in Tech]() Topics: [Architecture & Design](), [Software Engineering](), [Software]() Tags: [design](), [good-practices](), [soft-skills](), [software](), [software-design](), [systems]() ### AI overview The article argues that software design, like soft skills, is difficult to evaluate objectively because its quality depends on context, communication, personal judgment, and real-world outcomes. It questions whether conventions such as readable code, established practices, or TDD reliably define good design. ### Source excerpt How to build systems in the real world ## How continuous product discovery works for us DevFeed: [How continuous product discovery works for us]() Original publisher: [Read original article]() Author: Sören Weber Senior Product Manager @ trivago; Core Product; AI Linkedin profile Published: 2023-02-01T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Product Management](), [Self-organizing Team](), [Agile](), [User experience (UX)](), [Development]() Tags: [cross-functional-teams](), [delivery](), [development](), [discovery](), [driving](), [engineering](), [good-practices](), [product-management](), [research](), [scope](), [software](), [strategy]() ### AI overview A trivago product manager explains continuous product discovery, distinguishing it from product delivery and describing how user research, solution ideation, and solution testing help teams decide what to build. The article also discusses trivago's adoption of Teresa Torres's continuous discovery framework alongside cross-functional teams, outcome-driven OKRs, and agile software development. ### Source excerpt Hello, I am a product manager here at trivago. I have worked on different parts of the product such as apps, alternative accommodations, landing pages, and search & flow. We work in cross-fu... ## Rewriting the trivago Android app: challenges and lessons learnt DevFeed: [Rewriting the trivago Android app: challenges and lessons learnt]() Original publisher: [Read original article]() Author: Rafael Ortega Lupión Follow Published: 2018-02-06T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Android](), [android-development](), [Development](), [Refactoring](), [Mobile]() Tags: [android](), [android-development](), [architecture](), [clean-architecture](), [code](), [cross-functional-teams](), [development](), [good-practices](), [legacy-code](), [mobile](), [refactoring](), [tests](), [ux]() ### AI overview The trivago Android development team describes the challenges and lessons of rewriting its app, focusing on architectural decisions, cross-functional collaboration, workflow, product goals, and user experience. ### Source excerpt How the Android development team came up with a new architecture based on clean principles and what we learnt along the way. ## Code reviews DevFeed: [Code reviews]() Original publisher: [Read original article]() Published: 2017-08-29T00:00:00Z Content type: opinion Language: en Sources: [Paweł Chudzik]() Topics: [Code review](), [engineering-culture](), [Code quality]() Tags: [code-quality](), [code-reviews](), [good-practices](), [team](), [trust]() ### AI overview This opinion argues that code reviews should be a team effort rather than the responsibility of one person. It explains that shared reviews improve product ownership, expose more issues, spread knowledge, support learning, and contribute to better design. ### Source excerpt Code review is a great process which gradually improves code quality. It is a system you can implement in many ways. In this post I'm going to grumble about one particular way of performing code reviews - when there is only one person responsible for doing code reviews and suggesting/accepting/rejecting changes. Read more