# feature bloat

Feature bloat is the state in which a product accumulates so many features that their complexity and costs outweigh their value.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## AI-Led Development Made Features Cheap. Your Users Still Can't Find Them.

DevFeed: [AI-Led Development Made Features Cheap. Your Users Still Can't Find Them.](<https://devfeed.tech/articles/ai-led-development-made-features-cheap-your-users-still-can-t-find-them-142886.md>)

Original publisher: [Read original article](<https://hackernoon.com/ai-led-development-made-features-cheap-your-users-still-cant-find-them?source=rss>)

Author: Tanya Donska

Published: 2026-11-19T08:28:57Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [human centric design](<https://devfeed.tech/topics/human-centric-design.md>), [Interaction Design](<https://devfeed.tech/topics/interaction-design.md>), [codex](<https://devfeed.tech/topics/codex.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [after](<https://devfeed.tech/tags/after.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-led-development](<https://devfeed.tech/tags/ai-led-development.md>), [ai-led-product](<https://devfeed.tech/tags/ai-led-product.md>), [ai-ux](<https://devfeed.tech/tags/ai-ux.md>), [all](<https://devfeed.tech/tags/all.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [attention](<https://devfeed.tech/tags/attention.md>), [away](<https://devfeed.tech/tags/away.md>), [bad-ux](<https://devfeed.tech/tags/bad-ux.md>), [basic](<https://devfeed.tech/tags/basic.md>), [build](<https://devfeed.tech/tags/build.md>), [can](<https://devfeed.tech/tags/can.md>), [clicks](<https://devfeed.tech/tags/clicks.md>), [feature](<https://devfeed.tech/tags/feature.md>), [features](<https://devfeed.tech/tags/features.md>), [product-design](<https://devfeed.tech/tags/product-design.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [saas](<https://devfeed.tech/tags/saas.md>), [settings](<https://devfeed.tech/tags/settings.md>), [startups](<https://devfeed.tech/tags/startups.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>), [users](<https://devfeed.tech/tags/users.md>), [ux-design](<https://devfeed.tech/tags/ux-design.md>)

### AI overview

A feature can be built quickly and still go unused if users cannot find it. In the example, real-time co-editing sat behind four Settings screens; after 20-25 days, 8% had found it accidentally, 12% learned where it was from support, 3% read the changelog, and 77% had not found it. Adding a brief onboarding mention, a prompt when opening a document alone, and a Collaboration button in each document raised discovery to 81% and paid-plan usage from 8% to 47% in 30 days; requests fell from 47 to 11 per month. The feature itself did not change. The author argues that AI makes implementation faster but does not decide where features belong, and urges teams to check whether user requests are for capabilities already present and plan how users will discover new ones.

### Source excerpt

Users kept asking for a feature they already had. It took three months and close to $100K, sat four clicks deep in Settings, and 8% used it.

## AI feature bloat: why shipping less is better

DevFeed: [AI feature bloat: why shipping less is better](<https://devfeed.tech/articles/ai-feature-bloat-why-shipping-less-is-better-140984.md>)

Original publisher: [Read original article](<https://coderabbit.ai/blog/ai-feature-bloat-why-shipping-less-is-better>)

Author: Hendrik Krack

Published: 2026-11-17T12:00:00Z

Content type: article

Language: en

Sources: [CodeRabbit](<https://devfeed.tech/sources/coderabbit.md>)

Topics: [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-code-review](<https://devfeed.tech/tags/ai-code-review.md>), [ai-slop](<https://devfeed.tech/tags/ai-slop.md>), [api](<https://devfeed.tech/tags/api.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cost](<https://devfeed.tech/tags/cost.md>), [english](<https://devfeed.tech/tags/english.md>), [feature-bloat](<https://devfeed.tech/tags/feature-bloat.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [focus](<https://devfeed.tech/tags/focus.md>), [gate](<https://devfeed.tech/tags/gate.md>), [shipping](<https://devfeed.tech/tags/shipping.md>)

### AI overview

Hassan El-Mghari argues that AI makes features cheap to build but not cheap to get wrong: half-working features can erode user trust. He tests demand by teasing apps before committing to a build, uses repeated requests in responses to prioritize features, and launches publicly to hear feedback, including reports of security flaws such as an unauthenticated API route. His scope test is whether an app can be described in five words, with emphasis on making one thing work well. The excerpt presents these as his practices and examples, not as evidence that they guarantee success.

### Source excerpt

Coding agents make adding features nearly free, and Hassan El-Mghari of Together AI argues that is exactly why you should ship fewer of them. He explains how he tests ideas before building anything and keeps every app describable in five words.

## The Sunk Cost Fallacy of a Vibe-Coded Custom SaaS

DevFeed: [The Sunk Cost Fallacy of a Vibe-Coded Custom SaaS](<https://devfeed.tech/articles/the-sunk-cost-fallacy-of-a-vibe-coded-custom-saas-134491.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/11/15/the-sunk-cost-fallacy-of-a-vibe-coded-custom-saas.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

Published: 2026-11-15T00:00:00Z

Content type: opinion

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [implementation](<https://devfeed.tech/topics/implementation.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Google Calendar](<https://devfeed.tech/topics/google-calendar.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [cli](<https://devfeed.tech/tags/cli.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [cost](<https://devfeed.tech/tags/cost.md>), [custom](<https://devfeed.tech/tags/custom.md>), [github](<https://devfeed.tech/tags/github.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [github-copilot-cli](<https://devfeed.tech/tags/github-copilot-cli.md>), [google](<https://devfeed.tech/tags/google.md>), [google-calendar](<https://devfeed.tech/tags/google-calendar.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [rails](<https://devfeed.tech/tags/rails.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [saas](<https://devfeed.tech/tags/saas.md>), [sunk](<https://devfeed.tech/tags/sunk.md>)

### AI overview

Posebook is an open-source event-booking app built to manage a weekly figure-drawing session, handling venues and recurring programs, private invitations, date bookings, attendance, and public schedules. Participants book available dates through an invitation link; the system preserves booking history, keeps contact details private, creates Google Calendar meetings with the organizer and participant, and sends transactional email through a background worker. The author used GitHub Copilot CLI in bounded feature tasks, reviewing designs and pull requests and iterating on requirements. The excerpt notes that cancellations, rescheduling, consent, opt-outs, retries, and acknowledgments must work together, and questions whether this custom system is excessive for a single weekly event; it does not resolve that tradeoff.

### Source excerpt

I organize a weekly figure-drawing session at Enoch's Arts & Coffee in Manhattan. It runs every Monday at 6:30pm and costs $20. It's regularly attended and we were even written up in W42ST. Like any small event, it comes with the usual collection of emails, date juggling, private contact details, and calendar invitations. So, I decided to build a custom SaaS called Posebook to automate all that. The Plan The original idea was that models would register, choose a date, and get a reminder a week before posing. I chose Rails and MongoDB because I already use both, and started with one venue and one recurring program. The application now organizes venues, recurring programs, organizers, invitations, bookings, attendance, and public schedules. It is open source, and the hosted instance serves Enoch's, but could work for your event, too. The organizer creates a venue, adds its location, and sets up one or more recurring programs. A program owns its schedule, booking rules, and managers. The organizer sends a private invitation link to a participant, who creates an account if needed and books an available date. The application checks that the booking is still available, retains its history when it changes, and keeps participant contact information private. When a participant books, a configured Google Calendar integration creates one meeting with the participant and organizer on the guest list and the venue address in the location. Transactional emails go through a background worker. Cancellations, rescheduling, consent, opt-outs, retries, and acknowledgments all need to work together. Building It with an Agent I used GitHub Copilot CLI as an implementation partner. I started by asking for a plan and a name, settled the product and data model, and then gave it bounded feature requests. The agent explored the Rails application, changed code and tests on task branches, and opened pull requests. I reviewed the behavior, corrected the requirements when the implementation got t

## Feature Theater: The AI Industry's Real Product Is Mediocrity at Scale

DevFeed: [Feature Theater: The AI Industry's Real Product Is Mediocrity at Scale](<https://devfeed.tech/articles/feature-theater-the-ai-industry-s-real-product-is-mediocrity-at-scale-114851.md>)

Original publisher: [Read original article](<https://hackernoon.com/feature-theater-the-ai-industrys-real-product-is-mediocrity-at-scale?source=rss>)

Author: Andrew Schwabe

Published: 2026-11-03T11:43:04Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [product-experimentation](<https://devfeed.tech/topics/product-experimentation.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [trust](<https://devfeed.tech/topics/trust.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-industry](<https://devfeed.tech/tags/ai-industry.md>), [ai-product-management](<https://devfeed.tech/tags/ai-product-management.md>), [developer-productivity](<https://devfeed.tech/tags/developer-productivity.md>), [engineering-leadership](<https://devfeed.tech/tags/engineering-leadership.md>), [feature](<https://devfeed.tech/tags/feature.md>), [industry](<https://devfeed.tech/tags/industry.md>), [product](<https://devfeed.tech/tags/product.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [scale](<https://devfeed.tech/tags/scale.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The article argues that AI has made building features cheap without making product decisions easier, rewarding visible shipping and adoption over customer outcomes. It calls this "Feature Theater": teams add features because they are easy to build, measure clicks or demos, and often fail to check whether work improved. The author points to examples and studies that qualify the promise, including METR's early-2025 finding that experienced developers using AI took 19% longer on studied tasks despite believing they were faster; METR later said the result was outdated and newer data was inconclusive. The proposed response is to require a written spec before coding, resolve its concerns, define a measurable outcome for each feature, keep diffs small enough for real review, track time spent verifying AI output, and remove features that do not help. The article also lists warning signs such as adoption-only KPIs, post hoc specs, and demos treated as deliverables.

### Source excerpt

AI made building features nearly free. It didn't make deciding cheaper. So we ship more, measure less, and call it progress. That's Feature Theater.

## Why Most of What You Build Creates No Value

DevFeed: [Why Most of What You Build Creates No Value](<https://devfeed.tech/articles/why-most-of-what-you-build-creates-no-value-106698.md>)

Original publisher: [Read original article](<https://newsletter.techworld-with-milan.com/p/why-most-of-what-you-build-creates>)

Author: Dr Milan Milanović

Published: 2026-10-29T16:01:25Z

Content type: article

Language: en

Sources: [Tech World With Milan Newsletter](<https://devfeed.tech/sources/tech-world-with-milan-newsletter.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [product mindset](<https://devfeed.tech/topics/product-mindset.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [experiments](<https://devfeed.tech/topics/experiments.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [age-of-ai](<https://devfeed.tech/tags/age-of-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-prompts](<https://devfeed.tech/tags/ai-prompts.md>), [build](<https://devfeed.tech/tags/build.md>), [gmail](<https://devfeed.tech/tags/gmail.md>), [google](<https://devfeed.tech/tags/google.md>), [interview](<https://devfeed.tech/tags/interview.md>), [lead](<https://devfeed.tech/tags/lead.md>), [net](<https://devfeed.tech/tags/net.md>), [product](<https://devfeed.tech/tags/product.md>), [value](<https://devfeed.tech/tags/value.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The interview argues that most product ideas produce little measurable impact because users rarely change behavior, and teams often fail to measure launch outcomes. Itamar Gilad recommends evidence-guided development: set outcome goals, assess ideas by impact, cost, and confidence, validate assumptions through short experiments, and connect tasks to those steps. His Confidence Meter assigns more weight to rigorous tests, with post-launch data the strongest evidence; how much evidence is enough depends on an idea's cost and risk. He warns that AI-assisted coding does not remove the costs of shipping weak features or make launch-and-iterate a reliable learning method. AI can help analyze research, prepare experiments, and summarize interviews, but should not substitute for users or be trusted to draw broad conclusions from small samples. For engineers, he suggests starting with product teammates and asking what goal a project serves, what evidence supports its assumptions, and how to test them quickly.

### Source excerpt

An interview with Itamar Gilad, former Gmail product lead at Google and author of Evidence-Guided.

## RAG Complexity Is a Bet Against the Model

DevFeed: [RAG Complexity Is a Bet Against the Model](<https://devfeed.tech/articles/rag-complexity-is-a-bet-against-the-model-104354.md>)

Original publisher: [Read original article](<https://hackernoon.com/rag-complexity-is-a-bet-against-the-model?source=rss>)

Author: Tiger Data (creators of TimescaleDB)

Published: 2026-10-28T08:00:02Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [AI Architecture](<https://devfeed.tech/topics/ai-architecture.md>), [hybrid-search](<https://devfeed.tech/topics/hybrid-search.md>), [LLM evaluation / benchmarking](<https://devfeed.tech/topics/llm-evaluation-benchmarking.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Prompt Engineering](<https://devfeed.tech/topics/prompt-engineering.md>), [function calling](<https://devfeed.tech/topics/function-calling.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>)

Tags: [ai-agent-retrieval-systems](<https://devfeed.tech/tags/ai-agent-retrieval-systems.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-mcp-retrieval](<https://devfeed.tech/tags/claude-mcp-retrieval.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [experiments](<https://devfeed.tech/tags/experiments.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [hybrid-search](<https://devfeed.tech/tags/hybrid-search.md>), [model](<https://devfeed.tech/tags/model.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [postgresql-hybrid-search](<https://devfeed.tech/tags/postgresql-hybrid-search.md>), [postgresql-rag-architecture](<https://devfeed.tech/tags/postgresql-rag-architecture.md>), [rag](<https://devfeed.tech/tags/rag.md>), [rag-evaluation-methodology](<https://devfeed.tech/tags/rag-evaluation-methodology.md>), [rag-pipeline-optimization](<https://devfeed.tech/tags/rag-pipeline-optimization.md>), [search](<https://devfeed.tech/tags/search.md>), [stack](<https://devfeed.tech/tags/stack.md>), [tiger-cloud-fluid-storage](<https://devfeed.tech/tags/tiger-cloud-fluid-storage.md>)

### AI overview

The article reports that a minimal PostgreSQL RAG stack--a corpus table with BM25 and HNSW indexes, hybrid search via an MCP tool, and Claude--performed competitively on MuSiQue and BRIGHT. On MuSiQue, five proposed changes regressed the baseline; retrieval recall stayed above 80% at each hop depth, while lower answer accuracy suggested multi-hop reasoning remained a challenge. On BRIGHT, per-domain prompts improved several domains, and concept sketches improved retrieval recall where vocabulary gaps hid relevant robotics documents. Both additions were kept as removable prompt or column changes. The authors describe an evaluation loop using paired per-query tests and a three-attempt limit, with database forks making reverts cheap. They also acknowledge the agent loop's high inference cost compared with specialized retrievers, and frame future cost advantages as a projection dependent on continued model-price declines. BRIGHT prompts were tuned on the evaluated set, a stated methodology caveat.

### Source excerpt

See how a minimal PostgreSQL RAG stack competed on MuSiQue and BRIGHT, using hybrid search, Claude, and systematic experiments to avoid pipeline complexity.

## The Same Old Bullshit

DevFeed: [The Same Old Bullshit](<https://devfeed.tech/articles/the-same-old-bullshit-95738.md>)

Original publisher: [Read original article](<https://dpereira.substack.com/p/the-same-old-bullshit>)

Author: David Pereira

Published: 2026-10-22T12:29:32Z

Content type: opinion

Language: en

Sources: [Untrapping Product Teams](<https://devfeed.tech/sources/untrapping-product-teams.md>)

Topics: [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [To-Do](<https://devfeed.tech/topics/todo.md>)

Tags: [adapting](<https://devfeed.tech/tags/adapting.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [archive](<https://devfeed.tech/tags/archive.md>), [audacious](<https://devfeed.tech/tags/audacious.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [data](<https://devfeed.tech/tags/data.md>), [delete](<https://devfeed.tech/tags/delete.md>), [digital](<https://devfeed.tech/tags/digital.md>), [discuss](<https://devfeed.tech/tags/discuss.md>), [easy](<https://devfeed.tech/tags/easy.md>), [factory](<https://devfeed.tech/tags/factory.md>), [feature](<https://devfeed.tech/tags/feature.md>), [features](<https://devfeed.tech/tags/features.md>), [ideas](<https://devfeed.tech/tags/ideas.md>)

### AI overview

The article argues that stale backlog items can distract teams and, when connected to agentic AI, lead to implementing work that no longer fits current goals. It recommends setting direction first--where you want to go, where you are, and what comes next--then clearing work that does not support it. Suggested routines: filter for items untouched for 90 days, review and remove or archive them every two weeks, and check backlog alignment with the main goal every six weeks. The author also proposes deleting an entire backlog as a bold option, especially for startups, while acknowledging it may feel threatening and is less realistic for enterprises. Start with one neglected item and share the results.

### Source excerpt

We struggle to renounce old ideas, even when they don't serve us any longer.

## AI's Midas problem: When code is free, features are worthless

DevFeed: [AI's Midas problem: When code is free, features are worthless](<https://devfeed.tech/articles/ai-s-midas-problem-when-code-is-free-features-are-worthless-90663.md>)

Original publisher: [Read original article](<https://thenewstack.io/ai-commoditizes-software-value/>)

Author: Steve Fenton

Published: 2026-10-20T13:00:00Z

Content type: opinion

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-engineering](<https://devfeed.tech/tags/ai-engineering.md>), [contributed-octopus-deploy](<https://devfeed.tech/tags/contributed-octopus-deploy.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [development](<https://devfeed.tech/tags/development.md>), [dora](<https://devfeed.tech/tags/dora.md>), [has](<https://devfeed.tech/tags/has.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>)

### AI overview

The article argues that AI coding tools make producing code and features less distinctive, so software teams should move beyond the feature factory model. It recommends understanding users' jobs and challenges, combining that insight with domain knowledge, and creating solutions that provide value beyond what users can produce with an AI subscription.

### Source excerpt

Every team that adopted Claude Code, Cursor, or Copilot to produce more code has the same problem: When output is The post AI's Midas problem: When code is free, features are worthless appeared first on The New Stack.

## TBM 445: The Feature Factory: A 10-Year Retrospective

DevFeed: [TBM 445: The Feature Factory: A 10-Year Retrospective](<https://devfeed.tech/articles/tbm-445-the-feature-factory-a-10-year-retrospective-88143.md>)

Original publisher: [Read original article](<https://cutlefish.substack.com/p/tbm-445-the-feature-factory-a-10>)

Author: John Cutler

Published: 2026-10-15T21:51:55Z

Content type: opinion

Language: en

Sources: [The Beautiful Mess](<https://devfeed.tech/sources/the-beautiful-mess.md>)

Topics: [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>), [development-process](<https://devfeed.tech/topics/development-process.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [career](<https://devfeed.tech/tags/career.md>), [feature](<https://devfeed.tech/tags/feature.md>), [retrospective](<https://devfeed.tech/tags/retrospective.md>)

### AI overview

In a ten-year retrospective on the "feature factory" idea, the author argues that product work is a spectrum: teams balance feature delivery, outcomes, customer learning, and experimentation under constraints such as trust, access to data, and organizational incentives. They describe how AI can support discovery and prototyping, but can also amplify weak practices such as replacing customer conversations with synthetic personas or generating PRDs that reinforce poor documentation habits.

### Source excerpt

10 years ago I wrote a post on Medium about Feature Factories that literally changed my life.

## The feature works. But does it belong?

DevFeed: [The feature works. But does it belong?](<https://devfeed.tech/articles/the-feature-works-but-does-it-belong-79687.md>)

Original publisher: [Read original article](<https://coderabbit.ai/blog/the-feature-works-does-it-belong>)

Author: Hendrik Krack

Published: 2026-10-08T00:00:00Z

Content type: news

Language: en

Sources: [CodeRabbit](<https://devfeed.tech/sources/coderabbit.md>)

Topics: [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [added](<https://devfeed.tech/tags/added.md>), [advice](<https://devfeed.tech/tags/advice.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-code-review](<https://devfeed.tech/tags/ai-code-review.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [but](<https://devfeed.tech/tags/but.md>), [development](<https://devfeed.tech/tags/development.md>), [english](<https://devfeed.tech/tags/english.md>), [feature](<https://devfeed.tech/tags/feature.md>), [labs](<https://devfeed.tech/tags/labs.md>), [shipping](<https://devfeed.tech/tags/shipping.md>), [take](<https://devfeed.tech/tags/take.md>), [trm-labs](<https://devfeed.tech/tags/trm-labs.md>), [validating](<https://devfeed.tech/tags/validating.md>), [work](<https://devfeed.tech/tags/work.md>), [works](<https://devfeed.tech/tags/works.md>)

### AI overview

Both founders describe agents making implementation faster, which raises the stakes of deciding what to build and how to review it. TRM Labs uses a "product cortex" to turn customer feedback into prioritized ideas, requirements, and prototypes; adding its design system and strategic priorities improved agent suggestions, and Rahul estimated about 10% of signals became work the team would eventually build. TRM required human approval for customer-facing pull requests and deployments while developing automated test evidence and controls to route security-sensitive changes for human review. CodeRabbit is exploring an approval step before background agents open pull requests and senior review of prompts; developers remain responsible for validating changes. Faster output also pushed CodeRabbit to improve build and delivery infrastructure. Both teams let product and design contribute directly to code while engineers retain responsibility for decisions such as scale and API design.

### Source excerpt

TRM Labs' Rahul Raina and CodeRabbit's Harjot Gill on choosing, validating, and shipping work as agents take on more development.

## Recognizing when to leave an MBA, job, or product direction

DevFeed: [Recognizing when to leave an MBA, job, or product direction](<https://devfeed.tech/articles/wrong-place-63520.md>)

Original publisher: [Read original article](<https://dpereira.substack.com/p/wrong-place>)

Author: David Pereira

Published: 2026-10-01T12:46:55Z

Content type: opinion

Language: en

Sources: [Untrapping Product Teams](<https://devfeed.tech/sources/untrapping-product-teams.md>)

Topics: [product mindset](<https://devfeed.tech/topics/product-mindset.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>)

Tags: [advice](<https://devfeed.tech/tags/advice.md>), [career](<https://devfeed.tech/tags/career.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [fail](<https://devfeed.tech/tags/fail.md>), [features](<https://devfeed.tech/tags/features.md>)

### AI overview

A product manager recounts leaving a project management MBA after realizing its emphasis on predictability and control did not fit his approach to software work. He connects that choice to avoiding sunk-cost thinking in careers and products, including dropping features that create no value. The article suggests reflecting on personal priorities and distinguishing a worthwhile challenge from a poor fit.

### Source excerpt

Once a close friend of mine gave me advice that I will never forget because it changed my life.

## Zuora Review 2026: Is Enterprise Billing Software Worth the Complexity?

DevFeed: [Zuora Review 2026: Is Enterprise Billing Software Worth the Complexity?](<https://devfeed.tech/articles/zuora-review-2026-is-enterprise-billing-software-worth-the-complexity-10456.md>)

Original publisher: [Read original article](<https://dodopayments.com/blogs/zuora-review-alternative/>)

Author: Ayush Agarwal

Published: 2026-04-10T00:00:00Z

Content type: comparison

Language: en

Sources: [Dodo Payments Blog](<https://devfeed.tech/sources/dodo-payments-blog.md>)

Topics: [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [billing](<https://devfeed.tech/tags/billing.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [features](<https://devfeed.tech/tags/features.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [platform](<https://devfeed.tech/tags/platform.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [review](<https://devfeed.tech/tags/review.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [saas](<https://devfeed.tech/tags/saas.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

Zuora is presented as an enterprise billing orchestration platform suited to complex B2B contracts, ASC 606/IFRS 15 revenue recognition, CPQ workflows, and ERP integrations. Its modules cover subscription billing, revenue recognition, and payment orchestration through gateways; Zuora is not a payment processor or Merchant of Record, so sellers retain tax, compliance, and chargeback responsibilities. The article cites typical implementations of 3-6 months and estimates baseline contracts at $50,000 or more annually, plus implementation and integration costs. It says Chargebee offers more accessible onboarding for growth-stage SaaS, while Stripe Billing is faster and more developer-oriented but requires custom work for advanced billing and CPQ. Dodo Payments is described as a faster, transaction-priced Merchant of Record alternative, but not a fit for some enterprise ERP, CPQ, and multi-entity revenue needs.

### Source excerpt

An honest review of Zuora's enterprise billing platform - covering features, pricing, implementation complexity, and simpler alternatives for SaaS.

## Why we committed to a zero-bugs policy

DevFeed: [Why we committed to a zero-bugs policy](<https://devfeed.tech/articles/why-we-committed-to-a-zero-bugs-policy-83590.md>)

Original publisher: [Read original article](<https://linear.app/now/zero-bugs-policy>)

Published: 2025-09-24T13:18:00Z

Content type: article

Language: en

Sources: [Linear](<https://devfeed.tech/sources/linear.md>)

Topics: [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>)

Tags: [bug](<https://devfeed.tech/tags/bug.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [linear](<https://devfeed.tech/tags/linear.md>), [product](<https://devfeed.tech/tags/product.md>), [team](<https://devfeed.tech/tags/team.md>), [triage](<https://devfeed.tech/tags/triage.md>)

### AI overview

Linear describes how its zero-bugs policy works: the team cleared an existing bug backlog, removed the option to defer assigned bugs, and set response targets of 48 hours for high-priority bugs and seven days for others. Weekly reviews help balance assignments, spot product patterns, and address capacity. The article says the practice supports product quality, customer trust, and engineering team culture, while requiring reprioritization.

### Source excerpt

When we tell people that Linear maintains a zero-bug policy a common response is disbelief. It may sound like a ridiculous approach, but we do it because no other way makes sense. The zero-bug stance means that we address bugs immediately, with the exact number of days depending on the severity: low-priority bugs need to be addressed within 7 days, high-priority bugs within 2. We formalized this approach two years ago. The impetus was actually a bug in a popular consumer app that I had reported to their team. Finally two years ago--and five years after I first reported the bug--I saw that it got fixed. I thought to myself, "wow, millions of users suffered through this bug for years for no reason." If the company was going to fix the bug eventually, it would have been so much better to fix it right away. That's the big idea behind our zero-bug policy. We want Linear to be a solid, high-quality product, which means we're going to address any bug that comes in. Fixing a bug takes the same amount of work whether we do it right away or put it off. But it's not a zero-sum game: fixing it immediately gives us a higher-quality product and spares users unnecessary pain for the same overall effort. Plus the approach allows us to deliver a kind of magical experience for customers who report bugs and the next day (or sooner) find it's fixed. For example, this user last October who reported a problem with paragraph breaks in the Linear editor that we fixed the same day: Zero-bugs starts by clearing the backlog Once we agreed that a zero-bug policy was the only right way to go, the first step was to clean out the backlog. We had about 175 open bugs at that point and set aside three weeks to fix them all. For that period we paused all other projects. No one did anything but fix bugs. By the end we had given ourselves a clean slate. Next we had to put in place practices to maintain it. We already had rotating triage duties. Each week it would be someone's job to assign incoming bugs

## Why Quality Is Rare in Software and How Linear Treats It as a Business Strategy

DevFeed: [Why Quality Is Rare in Software and How Linear Treats It as a Business Strategy](<https://devfeed.tech/articles/why-is-quality-so-rare-83589.md>)

Original publisher: [Read original article](<https://linear.app/now/why-is-quality-so-rare>)

Published: 2025-05-27T17:45:53Z

Content type: opinion

Language: en

Sources: [Linear](<https://devfeed.tech/sources/linear.md>)

Topics: [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>)

Tags: [quality](<https://devfeed.tech/tags/quality.md>), [software](<https://devfeed.tech/tags/software.md>), [speed](<https://devfeed.tech/tags/speed.md>), [teams](<https://devfeed.tech/tags/teams.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

The author argues that software teams' emphasis on speed, metrics, and process can erode craftsmanship and product quality. Drawing on Linear's approach, the essay describes quality as a business strategy supported by small teams, customer judgment, end-to-end ownership, internal testing, and rapid bug fixes.

### Source excerpt

The modern world has made huge advances in knowledge, technology, and skill. We can build faster than ever. We know more than ever. Yet quality still feels so rare. So many things feel unfinished, broken, or forgettable - why? That's the question I've been trying to answer, almost my whole life. I remember as a kid, seeing bikes at the store, some of them just felt wrong. I couldn't understand why someone would go through the effort of making something and not make it beautiful. Later in my life, I realized it's because many don't care, many opt for cost, and many just do what's easy. What I was noticing, even as a child, was the presence or absence of craft. Craft happens in cycles Before machines, everything was made by hand. A tool, a chair, a door. They reflected the skill and care that was put into them. Some things were rough. But when someone puts their full attention into the work, the result could be truly great. This is what craft is about -- the deliberate attention put into making something excellent, not because someone is checking, but because it matters to the maker. Then came the industrial revolution and mass production. We started losing the connection to craft. We began to optimize for costs, speed, and quantity. We've been living our own version of this in the software industry. In the beginning, small teams crafted software with care. They took pride in what they built. But over time, the teams grew and the process started to look more like a manufacturing line. As we learned to ship to the cloud multiple times a day, we started to change how we work and think. "Just ship it." "Move fast and break things." We replaced purpose with metrics. If it didn't move a metric, it didn't matter. Even we, as designers, stopped asking; "Does this feel right?." Instead, we started asking: "Does it convert?" Experiments and A/B testing replaced judgment. Optimizing for a process replaced craft. The interesting thing is that this cycle keeps happening in the sam

## Launching Features Right on Time: Feature Gating

DevFeed: [Launching Features Right on Time: Feature Gating](<https://devfeed.tech/articles/launching-features-right-on-time-feature-gating-81351.md>)

Original publisher: [Read original article](<https://stack.convex.dev/feature-gating>)

Author: Stack

Published: 2022-11-21T16:39:00Z

Content type: tutorial

Language: en

Sources: [Stack](<https://devfeed.tech/sources/stack.md>)

Topics: [feature flags](<https://devfeed.tech/topics/feature-flags.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [Media Queries](<https://devfeed.tech/topics/media-queries.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [async](<https://devfeed.tech/tags/async.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cache-invalidation](<https://devfeed.tech/tags/cache-invalidation.md>), [feature-flagging](<https://devfeed.tech/tags/feature-flagging.md>), [fullstack](<https://devfeed.tech/tags/fullstack.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [react](<https://devfeed.tech/tags/react.md>), [reactivity](<https://devfeed.tech/tags/reactivity.md>)

### AI overview

This tutorial shows how to build a basic feature gate in Convex using reactive queries, allowing a feature to be enabled or disabled without redeploying and updating clients without reloading. It also discusses default values, testing, ownership, documentation, flag removal, and capabilities available in dedicated feature-flag services.

### Source excerpt

Today we're going to talk about how to flip features on and off remotely using a clever use of the reactive nature of Convex queries.

## 5 reasons why you shouldn't buy incident.io

DevFeed: [5 reasons why you shouldn't buy incident.io](<https://devfeed.tech/articles/5-reasons-why-you-shouldn-t-buy-incident-io-11568.md>)

Original publisher: [Read original article](<https://incident.io/blog/5-reasons-why-you-shouldnt-buy-incident-io>)

Author: Chris Evans

Published: 2022-09-08T00:00:00Z

Content type: opinion

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident management](<https://devfeed.tech/topics/incident-management.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>)

Tags: [complex](<https://devfeed.tech/tags/complex.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [customer-support](<https://devfeed.tech/tags/customer-support.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [get-involved](<https://devfeed.tech/tags/get-involved.md>), [impact](<https://devfeed.tech/tags/impact.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [intersection](<https://devfeed.tech/tags/intersection.md>), [outage](<https://devfeed.tech/tags/outage.md>), [platform](<https://devfeed.tech/tags/platform.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [product](<https://devfeed.tech/tags/product.md>), [regulation](<https://devfeed.tech/tags/regulation.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [reliability-engineering](<https://devfeed.tech/tags/reliability-engineering.md>), [service](<https://devfeed.tech/tags/service.md>), [shouldn-t](<https://devfeed.tech/tags/shouldn-t.md>), [site](<https://devfeed.tech/tags/site.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>)

### AI overview

The excerpt argues that incident.io may not suit organizations seeking a tool built only for SRE or engineering teams. The company frames incidents as cross-functional: engineers repair services, while support, executives and compliance teams may also need to respond and contribute to learning afterward. It says incident.io makes product trade-offs for organizations that value this broader collaboration, and presents the fit guidance as approximate rather than a set of strict rules. The excerpt ends before the full set of five reasons is given.

### Source excerpt

Not many companies will tell you exactly why you shouldn't use their product, but doing so can save everyone a lot of time and effort. So here you go, a short-cut to finding out whether we're the right tool for you.

## An Open Letter To The Go Team About Try

DevFeed: [An Open Letter To The Go Team About Try](<https://devfeed.tech/articles/an-open-letter-to-the-go-team-about-try-22146.md>)

Original publisher: [Read original article](<https://www.ardanlabs.com/blog/2019/07/an-open-letter-to-the-go-team-about-try.html>)

Published: 2019-07-01T00:00:00Z

Content type: opinion

Language: en

Sources: [William Kennedy](<https://devfeed.tech/sources/william-kennedy.md>)

Topics: [Error Handling](<https://devfeed.tech/topics/error-handling.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>)

Tags: [2018](<https://devfeed.tech/tags/2018.md>), [ardan-labs](<https://devfeed.tech/tags/ardan-labs.md>), [blog](<https://devfeed.tech/tags/blog.md>), [error-handling](<https://devfeed.tech/tags/error-handling.md>), [go](<https://devfeed.tech/tags/go.md>), [go-programming](<https://devfeed.tech/tags/go-programming.md>), [golang](<https://devfeed.tech/tags/golang.md>), [programming](<https://devfeed.tech/tags/programming.md>)

### AI overview

The author argues that survey and Go 2 proposal data do not establish broad support for adding `try` as a second error-handling mechanism. They note error handling ranked fifth among developers' biggest challenges at 5% in the 2018 survey, and suggest proposal submissions may overrepresent people who want changes. The excerpt also reports that checks are less common in code closer to `main` and more common higher in the stack, citing Rob Pike and Marcel van Lohuizen. The author accepts that some developers want better error handling but questions whether the evidence supports `try` or whether the proposed design is right.

### Source excerpt

"Once a language gets complex enough, programming in it is more like carving out a subset from an infinite sea of features, most of which we'll never learn. Once a language feels infinite, the costs of adding further features to it are no longer apparent". - [Mark Miller] (https://medium.com/@erights/the-tragedy-of-the-common-lisp-why-large-languages-explode-4e83096239b9) The new try proposal is an addition to the language that introduces a second mechanic to handle errors. It is being introduced in response to data gathered from the 2018 Go Survey and a review of proposals that were submitted during the Go 2 proposal process. The conclusion the Go team made from these data gathering exercises was that Go developers wanted better error handling.

## Every Feature Is Considered Harmful

DevFeed: [Every Feature Is Considered Harmful](<https://devfeed.tech/articles/every-feature-is-considered-harmful-30325.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/every-feature-considered-harmful>)

Published: 2017-12-05T13:26:01Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>)

Tags: [addition](<https://devfeed.tech/tags/addition.md>), [b2b](<https://devfeed.tech/tags/b2b.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [development](<https://devfeed.tech/tags/development.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [domain](<https://devfeed.tech/tags/domain.md>), [feature](<https://devfeed.tech/tags/feature.md>), [features](<https://devfeed.tech/tags/features.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [focus](<https://devfeed.tech/tags/focus.md>), [functional](<https://devfeed.tech/tags/functional.md>), [future](<https://devfeed.tech/tags/future.md>), [growth](<https://devfeed.tech/tags/growth.md>), [hacking](<https://devfeed.tech/tags/hacking.md>), [implement](<https://devfeed.tech/tags/implement.md>), [new-feature](<https://devfeed.tech/tags/new-feature.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

The article argues that each new product feature brings ongoing maintenance and can create functional, UI, quality, technical, documentation, or localization debt, making it difficult to add features without future costs. It suggests that young startups may prioritize growth, while successful products approaching maturity should devote resources to paying down debt; for the author's SaaS B2B context, that point may come after 4-8 years. A focused cleanup period may be warranted after 6-8 years, when technical problems, outdated features, bugs, and performance issues slow development. The author recommends weighing debt whenever adding a feature and says some resources should go toward debt repayment continuously.

### Source excerpt

We tend to believe that every new feature is a good and valuable addition to a product. Quite often, it can be hard to not implement a...

## The fear of shipping

DevFeed: [The fear of shipping](<https://devfeed.tech/articles/the-fear-of-shipping-25376.md>)

Original publisher: [Read original article](<https://smileykeith.com/2012/12/12/the-fear-of-shipping/>)

Author: Keith Smiley

Published: 2012-12-13T01:42:00Z

Content type: opinion

Language: en

Sources: [Keith Smiley](<https://devfeed.tech/sources/keith-smiley.md>)

Topics: [Deployment-Driven Development](<https://devfeed.tech/topics/deployment-driven-development.md>), [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>)

Tags: [feedback](<https://devfeed.tech/tags/feedback.md>), [ios](<https://devfeed.tech/tags/ios.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [os](<https://devfeed.tech/tags/os.md>), [projects](<https://devfeed.tech/tags/projects.md>), [shipping](<https://devfeed.tech/tags/shipping.md>)

### AI overview

The writer holds back at least a dozen potentially shippable projects, often adding features, because they fear an unfinished product will damage their first impression in the indie developer community. They recognize that a perfect first major application is unrealistic and are beginning to see releasing even unpolished OS X utilities they made for themselves as a way to build toward future work. They also consider using feedback to decide whether a project merits further effort.

### Source excerpt

Something I've become very aware of lately is how difficult it is for me to ship. I have at least a dozen unfinished projects that I could probably ship, yet I find any excuse to hold them back. I could say forget it and ship it. Then depending on the amount of feedback I received, decide whether or not it was worth putting more time into. I often fall victim to "just one more feature here" or "oh it would be great if I added this first." When I should have just shipped. After nearly convincing myself to do this, what is holding me back? The fear of ruining my first impressions. Up to this point my programming career, especially in public, has been pretty sparse. I've made a few websites, and I shipped an internal enterprise iOS app, but that doesn't count for much. So as far as most people know I sit at home on my thumbs 24/7 occasionally tweeting about Objective-C frameworks. I want to be perceived well in the community, I respect a lot of indie iOS and OS X developers and the last thing I want is attention for an unfinished or unpolished product. I am starting to realize that this is unrealistic. I would love my first major application to be perfect but that's just not feasible. I hope to get there in the future, but I am very close to accepting that getting there requires stepping stones. For me, those stepping stones might be some useless OS X utilities that I've made for myself and now want to share with the world. No matter how unpolished.