# ownership Published articles for ownership. 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 Decide How Much Authorship AI Should Have in Software Work DevFeed: [How to Decide How Much Authorship AI Should Have in Software Work]() Original publisher: [Read original article]() Author: Kyle Humphrey Published: 2026-09-17T12:00:32Z Content type: opinion Language: en Sources: [Atomic Object]() Topics: [agentic-engineering](), [Artificial Intelligence](), [implementation](), [Software]() Tags: [agentic](), [agentic-engineering](), [ai](), [artificial-intelligence](), [development-practices](), [engineering](), [implementation](), [ownership](), [software](), [workflow]() ### AI overview This commentary examines how AI-generated meeting summaries, backlog items, and implementation work can introduce vocabulary, decisions, scope, and structure that a team does not recognize or own. It argues that the artifact's purpose should guide how much authorship is delegated to AI, using Curiosity, Craft, and Care as principles for making that decision. ### Source excerpt Atomic's Agentic Engineering for Teams describes how work moves through a product backlog, definition, planning, implementation, and review when agents do much of the building. While working with a small team during a Research, Design, and Planning (RDP) engagement, I started paying attention to a smaller decision inside that process: how much authorship we give [...] The post Use Curiosity, Craft, and Care to Decide What AI Should Write appeared first on Atomic Spin. ## What a Technical Program Manager actually does DevFeed: [What a Technical Program Manager actually does]() Original publisher: [Read original article]() Author: Dean Hume Published: 2026-09-14T15:54:31Z Content type: opinion Language: en Sources: [Dean Hume]() Topics: [Software Engineering]() Tags: [delivery](), [dependency](), [engineering](), [execution](), [meetings](), [ownership](), [project](), [software-engineering](), [teams](), [technical](), [technical-program-manager]() ### AI overview This article explains the role of a Technical Program Manager, focusing on the gaps between engineering teams, explicit ownership, cross-team dependencies, and proactive identification of release-blocking problems. ### Source excerpt What does a Technical Program Manager actually do? A look at the gaps they fill, the decisions they chase, and the reactive vs proactive split. ## A working incident response model for GPU clouds DevFeed: [A working incident response model for GPU clouds]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-09-12T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [incident](), [Incident response](), [GPU](), [Monitoring](), [Tooling]() Tags: [communication](), [debugging](), [gpu](), [gpu-cloud](), [grafana](), [incident](), [incident-management](), [incident-response](), [jira](), [management](), [on-call](), [operations](), [ownership](), [pagerduty](), [review](), [slack](), [sre]() ### AI overview This article presents an incident response model for GPU clouds and other customer-facing infrastructure businesses. It emphasizes preparation, named ownership, meaningful alert paths, incident command, separation of technical work from customer communication, and post-incident learning. It argues that tools such as PagerDuty, Jira, Grafana, and Slack are useful only within a clear operating model. ### Source excerpt The tools matter, but they only work when they sit inside a clear operating model: ownership, signal, command, communication, and learning. ## Every service needs an owner DevFeed: [Every service needs an owner]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-09-12T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [systems](), [incident]() Tags: [catalog](), [customer](), [incident](), [on-call](), [ownership](), [platform-engineering](), [production](), [reliability](), [service](), [service-catalog](), [sre](), [startups](), [team]() ### AI overview The article argues that growing organizations need a focused service catalog to make production ownership visible. It recommends recording each service's customer outcome, owning team, current on-call contact, deployment path, health dashboard, runbook, and dependencies, and maintaining those records as part of engineering work. ### Source excerpt A useful service catalog is not an inventory project. It is a public record of who owns a customer outcome when the system is healthy and when it fails. ## Community updates: taking time off, AI club, and next events 💬 DevFeed: [Community updates: taking time off, AI club, and next events 💬]() Original publisher: [Read original article]() Author: Luca Rossi Published: 2026-08-28T07:01:45Z Content type: article Language: en Sources: [Refactoring]() Topics: [sessions](), [Artificial Intelligence](), [Processes](), [legacy]() Tags: [ai](), [community](), [events](), [ownership](), [processes](), [projects](), [sessions](), [slack]() ### AI overview A community update recaps discussions from the August Mastermind and AI Club, including planning time off without disrupting team ownership, AI learning and legacy migrations, and upcoming events. ### Source excerpt A special edition focused on our community activities! ## TBM 434: How Maps Can Hide Problems DevFeed: [TBM 434: How Maps Can Hide Problems]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-08-01T09:13:07Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [context](), [structure]() Tags: [design](), [mapping](), [maps](), [organizations](), [ownership](), [problems](), [product](), [reporting](), [silos](), [structure](), [technology]() ### AI overview The article argues that organizational maps can conceal incoherence when strategy, structure, technology, incentives, goals, ownership, teams, and funding do not align. It contrasts coherent organizations, where context transfers across map layers, with incoherent organizations, where people must repeatedly reorient and translate. ### Source excerpt If what you are mapping is incoherent, don't fall in love with the map (or your personal ability to navigate with it). ## Why AI Still Requires Human Delegation and Ownership DevFeed: [Why AI Still Requires Human Delegation and Ownership]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-05-09T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Artificial Intelligence](), [Job](), [context](), [round robin]() Tags: [agents](), [ai](), [delegation](), [job](), [ownership](), [tasks]() ### AI overview The article argues that AI can provide more hands to do work but does not eliminate the human responsibility of managing context, tracking tasks, delegating, and taking ownership of problems and domains. ### Source excerpt On AI, mental load, and delegation ## Code is cheap, reliability isn't DevFeed: [Code is cheap, reliability isn't]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-02-16T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [reliability](), [Artificial Intelligence](), [Large Language Model](), [Code]() Tags: [accountability](), [ai](), [code](), [llms](), [ownership](), [reliability]() ### AI overview An interview with Swizec Teller examines production ownership and reliability in the AI era, including SLAs, useful logs, accountability, and the continuing need for human responsibility when using LLMs for coding. ### Source excerpt Humans of Reliability talks with Swizec Teller about owning production in the AI era. ## Big Tech and Startup Software Engineering Experiences DevFeed: [Big Tech and Startup Software Engineering Experiences]() Original publisher: [Read original article]() Author: Mike Yerou Published: 2026-01-22T15:41:08Z Content type: opinion Language: en Sources: [Rock and Null]() Topics: [Software](), [coding](), [Job]() Tags: [company](), [engineering](), [lifecycle](), [ownership](), [scale](), [software](), [software-engineer](), [startup](), [thoughts]() ### AI overview The article compares software engineering in a large technology company with launching a startup. It argues that big companies provide scale, rigor, and specialization, while startups require broad ownership, adaptability, and responsibility across the product lifecycle; neither experience is inherently better. ### Source excerpt Working in a big tech company feels like being a cog in a powerful, well-oiled machine, while launching your own startup means building a smaller machine from scratch and owning every decision. Both paths are exciting, challenging, and valuable, but in completely different ways. ## \*People\* detangle a ball of mud DevFeed: [\*People\* detangle a ball of mud]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2025-11-15T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Architecture & Design](), [software-architecture](), [Development](), [Code]() Tags: [architecture](), [async](), [complexity](), [decoupling](), [ownership](), [patterns](), [processes](), [pull-requests](), [software-architecture](), [teams]() ### AI overview This opinion argues that teams and processes, rather than a lone architect, are the best way to gradually untangle a deteriorating "ball of mud" codebase. Giving teams ownership, allowing space for refactoring, formalizing recurring patterns, and discussing interfaces before coding can encourage decoupled subsystems. ### Source excerpt Ball of mud is the world's most popular software architecture. The one we all use at work. But it sucks to work with. So what do you do? ## AI Interview Success: An Interviewer's Inside Guide DevFeed: [AI Interview Success: An Interviewer's Inside Guide]() Original publisher: [Read original article]() Author: Karl Hörnlund Published: 2025-10-20T00:00:01Z Content type: article Language: en Sources: [Canva Engineering]() Topics: [Artificial Intelligence](), [Development](), [Programming]() Tags: [ai](), [ai-assisted-programming](), [development](), [guide](), [implementation](), [interview](), [interviews](), [ownership](), [production](), [programming](), [requirements](), [review](), [technical](), [workflow]() ### AI overview An interviewer shares guidance for succeeding in AI-assisted programming interviews. The article emphasizes using AI strategically while retaining ownership of technical decisions, understanding requirements, evaluating generated code, maintaining production-quality standards, and clearly explaining trade-offs. ### Source excerpt From the Other Side of the Screen: What We're Looking For in Your AI-Assisted Interview ## Why Delegation Fails - and What to Do About It DevFeed: [Why Delegation Fails - and What to Do About It]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2025-05-30T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [trust](), [context](), [execution]() Tags: [autonomy](), [ceo](), [context](), [delegation](), [leadership-delegation-decision-making-practices-goal-setting-startup](), [ownership](), [teams](), [trust]() ### AI overview The article argues that delegation often fails because leaders provide insufficient context, unclear expectations, limited autonomy, and inconsistent trust. It recommends defining the desired result, sharing context, aligning on expectations and autonomy, and giving teams meaningful ownership. ### Source excerpt "You don't have a delegation problem. You have a clarity and trust problem." I used to think I was helping my team by staying involved. Answering every question. Checking every detail. In reality, I was slowing everyone down - including myself. ## How Ownership and Impact Help Engineers Become Senior DevFeed: [How Ownership and Impact Help Engineers Become Senior]() Original publisher: [Read original article]() Author: Tiger Abrodi Published: 2024-05-14T05:56:49Z Content type: opinion Language: en Sources: [Saiyan Growth Letter]() Topics: [Programming](), [Refactoring](), [trust]() Tags: [communication](), [developers](), [ownership](), [productivity](), [programming](), [refactor](), [team](), [trust]() ### AI overview This commentary argues that becoming a senior engineer depends mainly on ownership and impact, supported by technical ability, communication, reliability, and teamwork. ### Source excerpt Two main ingredients: Ownership and Impact! ## My First 4 months at Bazaarvoice as a DevOps Engineer DevFeed: [My First 4 months at Bazaarvoice as a DevOps Engineer]() Original publisher: [Read original article]() Author: Edward Davies Published: 2024-03-18T13:34:17Z Content type: opinion Language: en Sources: [Bazaarvoice]() Topics: [DevOps](), [Cloud](), [jira](), [Slack]() Tags: [bazaarvoice](), [cloud](), [communication](), [culture](), [devops](), [devops-engineer](), [engineering](), [error-messages](), [jira](), [new-hire-onboarding](), [newhire](), [onboarding](), [ownership](), [slack](), [soft-skills](), [team](), [waysofworking]() ### AI overview A DevOps engineer reflects on their first four months at Bazaarvoice, focusing on public communication in Slack, searchable team knowledge, and shared ownership of Jira work. The post describes how public questions, documented updates, error messages, and blockers help distributed teams collaborate and continue work across time zones. ### Source excerpt I joined Bazaarvoice as a DevOps engineer into the Cloud engineering team in September 2023. It has been a very busy first 4 months learning a lot in terms of technical and soft skills. In this post I have highlighted my key learnings from my start at BV. Communication One of the key takeaways I [...] ## How BRYTER Achieved Increased Developer Experience, Ownership, Product Quality, and Engineering Effectiveness through Continuous Deployments DevFeed: [How BRYTER Achieved Increased Developer Experience, Ownership, Product Quality, and Engineering Effectiveness through Continuous Deployments]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-09-22T08:00:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Deployment](), [Developer experience](), [Testing](), [Selenium](), [TypeScript]() Tags: [case-study](), [case-study-continuous-deployment-developer-experience-developer-productivity-leadership-practic](), [deployment](), [deployments](), [developer-experience](), [ownership](), [qa](), [quality](), [resilience](), [selenium](), [typescript]() ### AI overview This case study describes how BRYTER addressed a monolithic deployment process in which deployments occurred twice weekly and were managed by QA. The resulting lack of visibility, ownership, and understanding affected engineering teams, testing, and resilience. BRYTER began moving toward continuous deployments and created a dedicated Developer Experience Team. ### Source excerpt How BRYTER Achieved Increased Developer Experience, Ownership, Product Quality, and Engineering Effectiveness through Continuous Deployments BRYTER, a German LegalTech scale-up, faced challenges with its monolithic deployment process and limited understanding of the deployment process within its engineering teams. Deployments occurred only twice a week and were managed by the QA team, leading to a lack of visibility and ownership among the other teams. ## The Importance of Values and Guiding Principles for Distributed Decision-Making (High-Purpose Environments, Part 4) DevFeed: [The Importance of Values and Guiding Principles for Distributed Decision-Making (High-Purpose Environments, Part 4)]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-05-27T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [decision-making](), [integrity](), [trust]() Tags: [alignment](), [collaboration](), [culture](), [culture-high-purpose-environments-engineering-excellence-organizational-design](), [decision-making](), [distributed](), [efficiency](), [integrity](), [ownership](), [supervision](), [trust](), [values](), [work]() ### AI overview This article explains how organizational values and guiding principles can support distributed decision-making. It argues that practical principles help employees make autonomous decisions aligned with the organization's vision and mission, reducing lengthy discussions and top-down approvals. ### Source excerpt The Importance of Values and Guiding Principles for Distributed Decision-Making (High-Purpose Environments, Part 4) Values and guiding principles are crucial in enabling distributed decision-making within an organization. They empower individuals to make decisions autonomously, without constant supervision or hierarchical approval. This leads to increased efficiency and agility and fosters a sense of ownership and responsibility among team members. ## Code Ownership: Keeping the balance between structure and agility DevFeed: [Code Ownership: Keeping the balance between structure and agility]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2022-02-12T12:53:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Code](), [modules](), [structure](), [code reviews](), [systems]() Tags: [code](), [code-reviews](), [developers](), [modules](), [ownership](), [practices-software-development-technical-leadership-organizational-design-software-craft](), [scale](), [structure](), [systems](), [teams]() ### AI overview The article explains strong, weak, and collective code ownership. It argues that team ownership reduces dependence on individual developers, while knowledge sharing through collaborative editing and code reviews helps teams maintain responsibility for modules. It also notes that collective ownership becomes harder to sustain as systems and teams grow. ### Source excerpt Code Ownership: Keeping the balance between structure and agility Code ownership is an important topic when it comes to enabling your teams and allowing developers to improve the system while keeping the overhead of changes low. ## Adopting Continuous Delivery: More a culture change than automation of processes DevFeed: [Adopting Continuous Delivery: More a culture change than automation of processes]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2021-12-04T12:07:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Continuous Delivery (CD)](), [Automation](), [Software]() Tags: [automation](), [burnout](), [continuous-delivery](), [continuous-deployment-software-development-developer-productivity-engineering-excellence-organiz](), [faster](), [ownership]() ### AI overview The article argues that adopting continuous delivery requires a culture and process change, not merely automating manual deployment activities. It recommends understanding existing delivery processes, responsibilities, risks, and safety mechanisms before simplifying or automating them. ### Source excerpt Adopting Continuous Delivery: More a culture change than automation of processes Continuous delivery, the process of automatically delivering changes of a system without human interaction, is one of the most beneficial practices that software teams can adopt. In Accelerate, the authors Nicole Forsgren, Jez Humble and Gene Kim, discovered a strong link between using continuous delivery and organisational performance: Teams that continuously deliver their changes have a stronger sense of ownership, get faster feedback and need to rework their code less. Furthermore, deployments are less stressful and the risk of burnout is reduced. ## Three things I wish I'd known learning Rust DevFeed: [Three things I wish I'd known learning Rust]() Original publisher: [Read original article]() Author: Graham King Published: 2020-11-19T00:04:14Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Rust](), [Learning](), [Library]() Tags: [dependencies](), [learning](), [ownership](), [rust](), [software](), [standard-library]() ### AI overview The author shares three lessons from learning Rust: it takes longer to learn because of its size and concepts such as ownership and lifetimes, its small standard library means most projects need dependencies, and much of its behavior comes from traits. ### Source excerpt It will take longer to learn than most languages, the standard library is small so you'll need dependencies, and a lot of behavior is in traits. ## How to Handle Workplace Issues Proactively DevFeed: [How to Handle Workplace Issues Proactively]() Original publisher: [Read original article]() Author: Map Published: 2010-01-26T01:30:10Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Job]() Tags: [issue](), [job](), [office](), [ownership](), [solve](), [work]() ### AI overview This workplace commentary explains that employees should communicate about problems early, adapt the amount of detail to their manager's preferences, take ownership of issues, and present possible solutions with their advantages and disadvantages. ### Source excerpt I often encounter people whether at my office or at other places of employment that are distraught after getting an earful from a manager from some problem arising. The problem usually isn't in their control, and therefore they don't understand why they get heat for this. Most managers though do actually understand when issues come up, however what they don't appreciate is late notice, lack of problem solving, and dictating what should be done next. Managers typically want individuals to take control of a situation and work towards resolving it. One thing you can do to ease the backlash that may occur for issues coming up is to communicate proactively as things develop/occur or lack there of. Keep in mind this should relate well to your managers style, some managers only want details when they absolutely have to have them. In that case you'll want to gradually give your manager a heads up, but not burden him with too much information. I would venture to say however that most managers appreciate details, details are great to give them insight into how things are going and allow them to feel engaged at a lower level. So assume you've communicated regularly to your manager, this still does not prevent any issues from happening, but rather reduces the shock when something does. At this point a manager still does not want a fact stated that there's a problem. In every case I've encountered the manager wants you to take ownership of the issue, meaning to give some options. Once the problem has arisen you should instantly start looking for ways to solve it. Often time these ways are not within your power to make the final decision, though you do have a great deal of control in presenting the case to a manager. Finally if you want brownie points, take less credit for any of the work you've done and give your manager more. If you've communicated early, laid out various options for how to resolve the issue with pros and cons of each you've done what you can. This should make ## Employees' rights to work on projects outside their jobs DevFeed: [Employees' rights to work on projects outside their jobs]() Original publisher: [Read original article]() Author: Map Published: 2008-08-30T00:44:19Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Job](), [Statement]() Tags: [google](), [job](), [ownership](), [startup](), [work]() ### AI overview The author argues that employees should generally be free to pursue additional work in their spare time, provided it does not damage their employer's brand or business effectiveness. The article also discusses how startup equity can create a sense of ownership without giving companies full claim over employees' personal time. ### Source excerpt As I currently work at a startup I have a small stake in the company. When talking with one friend of something I have been working with someone with on the side, the question came up over if this was a conflict of interest. I was actually quite shocked to hear the question at first, not only did I expect them to do likewise, as I know many that do. The full on conflict of interest statement just shocked me. Being at a startup it does make it slightly more of an interesting statement, but I received similar comments sometimes at my former Fortune 100 employer. I'll start with that place and then migrate to the startup environment. I could not disagree more being an employee at some place, and working on additional things being a conflict of interest. In short you are an employee, not property, your best interests lie with yourself. Sure its great if you believe in the company and what they do, but in our generation you are not attached for life to the company you work for. The company has claim on what you do between 8-5 with regards to work, sure if you do things that may damange a company brand or your effectiveness to do business its fair for them not to retain you, but simply doing additional work in your spare time? Hardly! Now as we move on to the startup atmosphere, where it's pretty standard that when becoming employed you receive some amount of equity in the company. In most cases with not being a founder this stake is of relatively small size. Sure you could consider Google where I believe it was over 400 employees that were made millionaires by their IPO, but these situations are very rare. The equity receive normally vessts over a period of time, and from my perception is simply equivilant to a portion of your pay no more no less. Sure it does make you feel more of a sense of ownership, but does not extend to the full extent of the business owning you. As an employee you're being paid to perform a job, they don't have full claim to what you do on your ti