<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Asesh</title>
    <description>The latest articles on DEV Community by Asesh (@abasu).</description>
    <link>https://dev.to/abasu</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3952011%2Fb9e59d9b-5d87-4d0b-b12a-58b2cf4196b2.png</url>
      <title>DEV Community: Asesh</title>
      <link>https://dev.to/abasu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/abasu"/>
    <language>en</language>
    <item>
      <title>Incentives Write the Code</title>
      <dc:creator>Asesh</dc:creator>
      <pubDate>Sat, 21 Nov 2026 12:30:00 +0000</pubDate>
      <link>https://dev.to/abasu/incentives-write-the-code-2m3f</link>
      <guid>https://dev.to/abasu/incentives-write-the-code-2m3f</guid>
      <description>&lt;p&gt;In 1999, Eric Raymond collected his essay &lt;em&gt;The Cathedral and the Bazaar&lt;/em&gt; into a book. It asked how software gets written: by a small group of wizards working behind closed doors, or by a loud crowd building in public and letting anyone poke at the result. Raymond argued that the bazaar tended to win, because many eyes make bugs shallow.&lt;/p&gt;

&lt;p&gt;This series is about a different question. Not how code gets written, but what gets paid for. Same two shapes, a cathedral and a bazaar, but now we are looking at the balance sheet behind each one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two teams, one difference
&lt;/h2&gt;

&lt;p&gt;Picture two teams of equally good engineers. Same degrees, same years of experience, same taste for clean abstractions. One team ships a thing you can read, fork, and run on your own machine. The other ships a thing you rent.&lt;/p&gt;

&lt;p&gt;Nothing about the engineers explains that. If you swapped the teams overnight, each would probably build what the other had been building, because the product is not shaped by what the engineers can do. &lt;u&gt;It is shaped by what the organisation around them is rewarded for doing.&lt;/u&gt;&lt;/p&gt;

&lt;p&gt;That is the thesis of this article: &lt;strong&gt;the difference between a proprietary lab and an open-source lab is not talent or skill. It is what each one is rewarded for, and that shows up in the code.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I do not mean this as an accusation. Nobody at a subscription company sat down and decided to make your life harder. Incentives work more quietly than that. They decide which tickets get prioritised, which pull requests get merged, which features get a launch post, and which bugs quietly age out in a backlog. Over a few years, those small decisions add up to an architecture.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the proprietary lab is paid for
&lt;/h2&gt;

&lt;p&gt;A proprietary software company is, at the level of its balance sheet, paid for three things: &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;retention&lt;/li&gt;
&lt;li&gt;recurring revenue, and&lt;/li&gt;
&lt;li&gt;keeping you inside the product.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The unit that matters is rarely the sale- it's the renewal. &lt;br&gt;
A customer who pays once is a transaction; a customer who pays every month is an asset, and the company's valuation is largely a bet on how long that asset lasts. &lt;br&gt;
Every roadmap meeting, or, whatever it is called, ends up asking some version of one question: does this make people more likely to stay?&lt;/p&gt;

&lt;p&gt;So every feature is graded on whether it keeps you subscribed. This is not always a bad thing. Oftentimes, the answer is a good one: make the product faster, make it more reliable, make it do the thing the customer cares about. A product people love is the best retention strategy there is, ideally.&lt;/p&gt;

&lt;p&gt;But the grading rubric leaks into the design in ways that are easy to miss:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Integrations that only go one way.&lt;/strong&gt; Importing your data from a competitor is a priority. Exporting it to one is not.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Proprietary formats.&lt;/strong&gt; Not necessarily out of malice. A custom format is simply the cheapest and fastest way to support the features the product has. &lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Features that raise switching costs.&lt;/strong&gt; Templates, history, shared workspaces, and automations are useful. They are also the things that make leaving feel like moving house.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Closed extension points.&lt;/strong&gt; If the platform controls the plugin store, it controls what the product can become.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this requires a villain. It only requires a quarterly target and an engineer who wants to hit it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the open-source lab is paid for
&lt;/h2&gt;

&lt;p&gt;The open-source lab is paid in a different currency: reuse. Being depended on. Being the thing that other people reach for when they need that problem solved.&lt;/p&gt;

&lt;p&gt;A library with a million downstream users has influence, a reputation, and often a career-shaped halo around its maintainers. The reward is leverage: your work multiplies because other people build on it. That pushes the code in a specific direction. Open projects tend to favour stable interfaces, documented behaviour, portable formats, and extension points, because those are the things that make something easy to depend on.&lt;/p&gt;

&lt;p&gt;There is a second reality that deserves honesty: a great many open-source maintainers are paid nothing at all. &lt;u&gt;They work evenings and weekends, around day jobs, and they are rewarded mostly in gratitude and issue reports.&lt;/u&gt; That is its own distortion. &lt;strong&gt;Unglamorous tasks such as security audits, accessibility, documentation, and long-term maintenance are exactly the ones that go underfunded.&lt;/strong&gt;&lt;br&gt;
So the open lab is not a utopia. It is a different set of pressures, with different failure modes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conway's Law, updated
&lt;/h2&gt;

&lt;p&gt;In 1967, Melvin Conway observed that organisations which design systems are constrained to produce designs that copy their own communication structure. Think of it like this: if you have four teams building a compiler, you will get a four-pass compiler.&lt;/p&gt;

&lt;p&gt;It is one of the more durable ideas in software, and it still hold up to this day. It just needs a small update, because the org chart behind a modern product is only half the story. The other half is the incentive chart.&lt;/p&gt;

&lt;p&gt;Behind the proprietary lab, the incentive chart is a cap table and a quarterly target. There are investors who want growth, a board that wants a trajectory, and a finance team that models churn to the decimal. The code reflects that. It is cohesive, because one organisation owns every decision. It is also shaped around the metrics that organisation answers to.&lt;/p&gt;

&lt;p&gt;Behind the open lab, the picture is a loose federation of maintainers, many with day jobs, a handful of corporate sponsors, and a contributor base that comes and goes. The code reflects that too. &lt;u&gt;It tends to be modular, because modules are how a federation divides work.&lt;/u&gt; It tends to be &lt;u&gt;configurable&lt;/u&gt;, because nobody can force a single vision on everyone. And it can be rough at the seams, because nobody is paid to sand them.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;When you look at a codebase, you are looking at a fossil record of the organisation that produced it, and of what that organisation was paid to care about.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Where the incentives agree
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;It would make an easier statement to say the two labs are opposites. They are not.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Nobody wants broken software. A proprietary company that ships constant crashes loses customers. An open project that ships constant crashes loses users, contributors, and its reputation. Both sides want the thing to work, both sides want security holes closed, and both sides want fast performance.&lt;/p&gt;

&lt;p&gt;This is why, on a quiet day, the two kinds of software can look the same from the outside. The incentives are aligned on quality, and they stay aligned for as long as quality is the cheapest way to get what each side wants.&lt;/p&gt;

&lt;p&gt;The interesting question is what happens when they stop being aligned.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where they split hard
&lt;/h2&gt;

&lt;p&gt;The split shows up at the boundaries, in the places where what is good for the user and what is good for the balance sheet pull apart.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Portability.&lt;/strong&gt; A user benefits from being able to leave. A subscription business benefits from you not leaving. An open project, whose success is measured by adoption rather than retention, has little reason to trap you and every reason to let you take your data to wherever you want.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pricing and packaging.&lt;/strong&gt; A proprietary product has a reason to hold back features for higher tiers. An open project has a different tension: features that matter to commercial users but cost real effort to build. Here the incentives do not split so much as get complicated, and I will come back to that in Article 2.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Longevity.&lt;/strong&gt; A proprietary product lives as long as it is profitable, or as long as the company that owns it stays interested. An open project lives as long as someone is willing to keep going, and when they stop, someone else is allowed to pick it up. That one difference is large enough that Article 3 is built on it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Direction.&lt;/strong&gt; A proprietary roadmap is steered by whatever maximises revenue. An open roadmap is steered by whoever shows up. Neither is guaranteed to be steered by what you, the user, actually need.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These are not moral differences. They are the predictable output of two different payment structures.&lt;/p&gt;

&lt;h2&gt;
  
  
  The sentence the series rests on
&lt;/h2&gt;

&lt;p&gt;Here it is, in one line:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Proprietary labs optimise for the moat. Open labs optimise for the leverage.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A moat is a defence. It is anything that makes it hard for a customer to leave or a competitor to catch up. Proprietary formats, accumulated data, network effects, and workflows built into your daily routine are all moat. A company with a deep moat can charge steadily, plan years ahead, and survive mistakes.&lt;/p&gt;

&lt;p&gt;Leverage is multiplication. It is anything that lets a small amount of work produce a large amount of effect. A library that thousands of products depend on, a protocol that every system speaks, and a tool that teaches people a skill they take elsewhere are all leverage. A project with strong leverage grows by being useful to people who never have to ask permission.&lt;/p&gt;

&lt;p&gt;Both are rational strategies. Both can produce excellent software. They simply produce different software, because they are solving different problems. One is asking, how do we make sure this customer stays? The other is asking, how do we make sure this thing is worth using everywhere?&lt;/p&gt;

&lt;h2&gt;
  
  
  One caution before moving on
&lt;/h2&gt;

&lt;p&gt;It is tempting to read this as a story about good and bad. Please do not. The incentive framing is useful precisely because it removes the need for villains and heroes. A proprietary engineer building a beautiful, locked-in product is doing a good job at the thing they are paid for. An open-source maintainer building a rough but portable tool is doing a good job at the thing they are rewarded for. Both are rational. Both are doing what the structure around them asks.&lt;/p&gt;

&lt;p&gt;The practical consequence is that you can predict a lot about a piece of software without ever reading its code. Ask who pays for it, what they are paid for, and what would happen to that payment if you left. The answers will tell you most of what the architecture will eventually show you.&lt;/p&gt;

&lt;p&gt;In the first series, in &lt;em&gt;Open Source Is How Small Teams Build Big Things&lt;/em&gt;, I argued - A small team cannot out-spend a corporation, but it can choose which incentives it builds on top of. &lt;br&gt;
The open ecosystem is where the leverage lives, and a small team that learns to use it gets to punch well above its size.&lt;/p&gt;




&lt;h2&gt;
  
  
  What comes next
&lt;/h2&gt;

&lt;p&gt;If open labs are optimising for leverage, a reasonable follow-up question is: what exactly is being leveraged?&lt;/p&gt;

&lt;p&gt;The answer is not code in the abstract. It is something more specific, and more like a public road than a gift: inspection, repairability, and shared foundations that nearly every product, including the proprietary ones, quietly stands on. That is the subject of Article 2.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>opensource</category>
      <category>softwaredevelopment</category>
      <category>development</category>
    </item>
    <item>
      <title>The Hidden Cost of Context Switching</title>
      <dc:creator>Asesh</dc:creator>
      <pubDate>Thu, 28 May 2026 18:30:00 +0000</pubDate>
      <link>https://dev.to/abasu/the-hidden-cost-of-context-switching-g6l</link>
      <guid>https://dev.to/abasu/the-hidden-cost-of-context-switching-g6l</guid>
      <description>&lt;p&gt;For a long time, I thought productivity was about effort.&lt;/p&gt;

&lt;p&gt;Work harder.&lt;/p&gt;

&lt;p&gt;Focus more.&lt;/p&gt;

&lt;p&gt;Stay disciplined.&lt;/p&gt;

&lt;p&gt;Manage time better.&lt;/p&gt;

&lt;p&gt;Most productivity advice is built around some version of this idea.&lt;/p&gt;

&lt;p&gt;Then I noticed something strange.&lt;/p&gt;

&lt;p&gt;Some days I could spend ten hours at a desk and accomplish almost nothing.&lt;/p&gt;

&lt;p&gt;Other days I could spend three hours working and make more progress than I had all week.&lt;/p&gt;

&lt;p&gt;The difference wasn't effort.&lt;/p&gt;

&lt;p&gt;The difference was context.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Most Expensive Thing Is Not Time
&lt;/h2&gt;

&lt;p&gt;Ask people what their most limited resource is and most will answer:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Time.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;But for knowledge workers, engineers, researchers, writers, and designers, I think the scarcer resource is often something else.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Mental state.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The ability to hold a problem in your head.&lt;/p&gt;

&lt;p&gt;The ability to remember why a decision was made.&lt;/p&gt;

&lt;p&gt;The ability to see connections between ideas.&lt;/p&gt;

&lt;p&gt;The ability to continue a train of thought without interruption.&lt;/p&gt;

&lt;p&gt;That's the state where meaningful work happens.&lt;/p&gt;

&lt;p&gt;And it's surprisingly fragile.&lt;/p&gt;




&lt;h2&gt;
  
  
  Every Context Switch Has a Cost
&lt;/h2&gt;

&lt;p&gt;Imagine you're debugging a difficult issue.&lt;/p&gt;

&lt;p&gt;You've already:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;read the logs&lt;/li&gt;
&lt;li&gt;inspected the code&lt;/li&gt;
&lt;li&gt;traced the requests&lt;/li&gt;
&lt;li&gt;formed a hypothesis&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You're finally starting to see the shape of the problem.&lt;/p&gt;

&lt;p&gt;Then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a Slack notification arrives&lt;/li&gt;
&lt;li&gt;someone schedules a meeting&lt;/li&gt;
&lt;li&gt;an email requires attention&lt;/li&gt;
&lt;li&gt;a different task becomes urgent&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The interruption itself might only take two minutes.&lt;/p&gt;

&lt;p&gt;The real cost is what disappears.&lt;/p&gt;

&lt;p&gt;The mental model.&lt;/p&gt;

&lt;p&gt;The momentum.&lt;/p&gt;

&lt;p&gt;The partially constructed map inside your head.&lt;/p&gt;

&lt;p&gt;The next time you return to the task, you don't continue where you left off.&lt;/p&gt;

&lt;p&gt;You rebuild.&lt;/p&gt;




&lt;h2&gt;
  
  
  Software Often Creates The Problem It Tries To Solve
&lt;/h2&gt;

&lt;p&gt;One thing that surprised me after building products for years is how much software exists primarily because other software creates friction.&lt;/p&gt;

&lt;p&gt;A note-taking application exists because memory is limited.&lt;/p&gt;

&lt;p&gt;A task manager exists because priorities change.&lt;/p&gt;

&lt;p&gt;A research assistant exists because information is fragmented.&lt;/p&gt;

&lt;p&gt;Many tools are not solving fundamental problems.&lt;/p&gt;

&lt;p&gt;They're solving problems created by context switching.&lt;/p&gt;

&lt;p&gt;The modern workflow often looks like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Article
    ↓
Bookmark
    ↓
Notes
    ↓
Task Manager
    ↓
Email
    ↓
Chat
    ↓
Calendar
    ↓
Back To Article
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Every transition introduces friction.&lt;/p&gt;

&lt;p&gt;Every transition requires reconstruction.&lt;/p&gt;

&lt;p&gt;Every transition burns attention.&lt;/p&gt;




&lt;h2&gt;
  
  
  Information Is Cheap. Context Is Expensive.
&lt;/h2&gt;

&lt;p&gt;This realization changed how I think about software.&lt;/p&gt;

&lt;p&gt;For years, software focused on helping us collect more information.&lt;/p&gt;

&lt;p&gt;More notes.&lt;/p&gt;

&lt;p&gt;More bookmarks.&lt;/p&gt;

&lt;p&gt;More documents.&lt;/p&gt;

&lt;p&gt;More tabs.&lt;/p&gt;

&lt;p&gt;More databases.&lt;/p&gt;

&lt;p&gt;More content.&lt;/p&gt;

&lt;p&gt;But information was never the bottleneck.&lt;/p&gt;

&lt;p&gt;The internet solved information scarcity years ago.&lt;/p&gt;

&lt;p&gt;The bottleneck became context.&lt;/p&gt;

&lt;p&gt;Knowing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;why something mattered&lt;/li&gt;
&lt;li&gt;where it came from&lt;/li&gt;
&lt;li&gt;how it connects to other ideas&lt;/li&gt;
&lt;li&gt;what you were trying to accomplish&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's the expensive part.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Best Tools Protect Mental State
&lt;/h2&gt;

&lt;p&gt;This is why some software feels unusually good to use.&lt;/p&gt;

&lt;p&gt;Not because it has more features.&lt;/p&gt;

&lt;p&gt;Because it preserves context.&lt;/p&gt;

&lt;p&gt;Good software reduces the number of mental transitions required to complete a task.&lt;/p&gt;

&lt;p&gt;It keeps related information together.&lt;/p&gt;

&lt;p&gt;It remembers things on your behalf.&lt;/p&gt;

&lt;p&gt;It removes unnecessary decisions.&lt;/p&gt;

&lt;p&gt;It minimizes the number of times you have to rebuild your mental model.&lt;/p&gt;

&lt;p&gt;The best tools don't merely store information.&lt;/p&gt;

&lt;p&gt;They protect attention.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why This Matters More Than Ever
&lt;/h2&gt;

&lt;p&gt;Ironically, technology has made context switching easier than ever.&lt;/p&gt;

&lt;p&gt;Notifications.&lt;/p&gt;

&lt;p&gt;Messaging platforms.&lt;/p&gt;

&lt;p&gt;Infinite feeds.&lt;/p&gt;

&lt;p&gt;Multiple devices.&lt;/p&gt;

&lt;p&gt;AI assistants.&lt;/p&gt;

&lt;p&gt;Constant connectivity.&lt;/p&gt;

&lt;p&gt;The modern worker can access more information than any generation before them.&lt;/p&gt;

&lt;p&gt;And yet many people feel perpetually interrupted.&lt;/p&gt;

&lt;p&gt;Not because they lack tools.&lt;/p&gt;

&lt;p&gt;Because every tool is competing for the same cognitive resource.&lt;/p&gt;

&lt;p&gt;Attention.&lt;/p&gt;




&lt;h2&gt;
  
  
  What This Means For Builders
&lt;/h2&gt;

&lt;p&gt;The first time I understood this, I stopped thinking about software as information storage.&lt;/p&gt;

&lt;p&gt;I started thinking about it as context preservation.&lt;/p&gt;

&lt;p&gt;A note is not valuable because it stores text.&lt;/p&gt;

&lt;p&gt;It's valuable because it preserves a thought.&lt;/p&gt;

&lt;p&gt;A bookmark is not valuable because it stores a URL.&lt;/p&gt;

&lt;p&gt;It's valuable because it preserves intent.&lt;/p&gt;

&lt;p&gt;A research tool is not valuable because it retrieves information.&lt;/p&gt;

&lt;p&gt;It's valuable because it preserves the path that led to a conclusion.&lt;/p&gt;

&lt;p&gt;The hidden cost of context switching is not the interruption itself.&lt;/p&gt;

&lt;p&gt;It's the reconstruction that follows.&lt;/p&gt;

&lt;p&gt;And increasingly, the most valuable software is not helping people find more information.&lt;/p&gt;

&lt;p&gt;It's helping them lose less context.&lt;/p&gt;

&lt;p&gt;Because in the end, meaningful work rarely happens when we're collecting information.&lt;/p&gt;

&lt;p&gt;It happens when we're able to stay with a thought long enough for it to become something useful.&lt;/p&gt;

</description>
      <category>career</category>
      <category>developers</category>
      <category>mentalhealth</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Most Software Is Workflow Design</title>
      <dc:creator>Asesh</dc:creator>
      <pubDate>Wed, 27 May 2026 18:30:00 +0000</pubDate>
      <link>https://dev.to/abasu/most-software-is-workflow-design-4lac</link>
      <guid>https://dev.to/abasu/most-software-is-workflow-design-4lac</guid>
      <description>&lt;p&gt;One of the biggest mistakes I made early in my career was believing that software products were primarily collections of features.&lt;/p&gt;

&lt;p&gt;This application has authentication.&lt;/p&gt;

&lt;p&gt;That application has dashboards.&lt;/p&gt;

&lt;p&gt;This one has AI.&lt;/p&gt;

&lt;p&gt;That one has collaboration.&lt;/p&gt;

&lt;p&gt;The assumption was simple:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Better technology creates better software.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Over time, I realized something uncomfortable.&lt;/p&gt;

&lt;p&gt;Most users don't care about the technology.&lt;/p&gt;

&lt;p&gt;Most users barely care about the features.&lt;/p&gt;

&lt;p&gt;What they care about is getting something done.&lt;/p&gt;

&lt;p&gt;And that's when I started seeing software differently.&lt;/p&gt;

&lt;p&gt;Not as collections of features.&lt;/p&gt;

&lt;p&gt;But as collections of workflows.&lt;/p&gt;




&lt;h2&gt;
  
  
  The User Is Trying To Do Something
&lt;/h2&gt;

&lt;p&gt;Nobody wakes up in the morning thinking:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;I need a note-taking application.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;They're thinking:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;I need to remember something.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Nobody wants a project management platform.&lt;/p&gt;

&lt;p&gt;They want a project to move forward.&lt;/p&gt;

&lt;p&gt;Nobody wants a CRM.&lt;/p&gt;

&lt;p&gt;They want customers.&lt;/p&gt;

&lt;p&gt;Nobody wants an AI assistant.&lt;/p&gt;

&lt;p&gt;They want answers.&lt;/p&gt;

&lt;p&gt;The software is simply a vehicle.&lt;/p&gt;

&lt;p&gt;The workflow is the destination.&lt;/p&gt;




&lt;h2&gt;
  
  
  Features Are Usually The Wrong Unit Of Measurement
&lt;/h2&gt;

&lt;p&gt;When software teams discuss products internally, conversations often sound like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Add a dashboard&lt;/li&gt;
&lt;li&gt;Add AI&lt;/li&gt;
&lt;li&gt;Add notifications&lt;/li&gt;
&lt;li&gt;Add integrations&lt;/li&gt;
&lt;li&gt;Add reporting&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But users rarely experience software as a list of features.&lt;/p&gt;

&lt;p&gt;They experience it as a sequence of actions.&lt;/p&gt;

&lt;p&gt;Consider a note-taking application.&lt;/p&gt;

&lt;p&gt;A product team may describe it as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;rich text editing&lt;/li&gt;
&lt;li&gt;tagging&lt;/li&gt;
&lt;li&gt;folders&lt;/li&gt;
&lt;li&gt;search&lt;/li&gt;
&lt;li&gt;synchronization&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A user experiences it as:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Capture
    ↓
Organize
    ↓
Find Later
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The workflow is what matters.&lt;/p&gt;

&lt;p&gt;The features only exist to support it.&lt;/p&gt;




&lt;h2&gt;
  
  
  Good Software Removes Steps
&lt;/h2&gt;

&lt;p&gt;Once I started thinking in workflows, something else became obvious.&lt;/p&gt;

&lt;p&gt;Many products compete on features.&lt;/p&gt;

&lt;p&gt;The best products compete on friction.&lt;/p&gt;

&lt;p&gt;The question stopped being:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What can we add?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And became:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What can we remove?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Every extra click.&lt;/p&gt;

&lt;p&gt;Every extra form.&lt;/p&gt;

&lt;p&gt;Every unnecessary screen.&lt;/p&gt;

&lt;p&gt;Every context switch.&lt;/p&gt;

&lt;p&gt;Every manual step.&lt;/p&gt;

&lt;p&gt;All of it accumulates.&lt;/p&gt;

&lt;p&gt;Users don't usually describe this as friction.&lt;/p&gt;

&lt;p&gt;They describe it as:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;This feels annoying.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Or:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;This feels complicated.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Or:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;This feels slow.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;What they're actually describing is workflow debt.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Best Products Usually Look Simple
&lt;/h2&gt;

&lt;p&gt;This is why some products appear deceptively basic.&lt;/p&gt;

&lt;p&gt;Instagram wasn't successful because it had hundreds of features.&lt;/p&gt;

&lt;p&gt;Its core workflow was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Capture → Filter → Share&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Uber wasn't successful because of map technology.&lt;/p&gt;

&lt;p&gt;Its core workflow was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Request → Ride → Pay&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;GitHub wasn't successful because it invented version control.&lt;/p&gt;

&lt;p&gt;Its core workflow was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Push → Review → Merge&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The technology matters.&lt;/p&gt;

&lt;p&gt;But users remember the workflow.&lt;/p&gt;




&lt;h2&gt;
  
  
  Most Product Ideas Are Workflow Gaps
&lt;/h2&gt;

&lt;p&gt;This realization changed how I evaluate software ideas.&lt;/p&gt;

&lt;p&gt;I used to look for missing technologies.&lt;/p&gt;

&lt;p&gt;Now I look for broken workflows.&lt;/p&gt;

&lt;p&gt;When people complain:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;I have to copy this from one system into another.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Or:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;I keep losing track of this information.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Or:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;I spend an hour doing the same thing every week.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Those aren't feature requests.&lt;/p&gt;

&lt;p&gt;Those are workflow failures.&lt;/p&gt;

&lt;p&gt;And workflow failures are often where product opportunities hide.&lt;/p&gt;

&lt;p&gt;Many successful products are not technological breakthroughs.&lt;/p&gt;

&lt;p&gt;They're workflow repairs.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Small Teams Keep Winning
&lt;/h2&gt;

&lt;p&gt;This connects directly to something I wrote about in &lt;strong&gt;Open Source Is How Small Teams Build Big Things&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Most primitives already exist.&lt;/p&gt;

&lt;p&gt;Databases exist.&lt;/p&gt;

&lt;p&gt;Authentication exists.&lt;/p&gt;

&lt;p&gt;Search exists.&lt;/p&gt;

&lt;p&gt;Payments exist.&lt;/p&gt;

&lt;p&gt;AI exists.&lt;/p&gt;

&lt;p&gt;Cloud infrastructure exists.&lt;/p&gt;

&lt;p&gt;If those layers already exist, then the question becomes:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What should we build?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Increasingly, the answer is:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Better workflows.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The opportunity is rarely another database.&lt;/p&gt;

&lt;p&gt;The opportunity is usually helping someone move from:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem
    ↓
Solution
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;with less friction than before.&lt;/p&gt;




&lt;h2&gt;
  
  
  What This Means For Builders
&lt;/h2&gt;

&lt;p&gt;The first time I understood this, I stopped looking at software as a collection of features.&lt;/p&gt;

&lt;p&gt;I started looking at it as a sequence of actions.&lt;/p&gt;

&lt;p&gt;A workflow.&lt;/p&gt;

&lt;p&gt;Users don't buy technology.&lt;/p&gt;

&lt;p&gt;They buy outcomes.&lt;/p&gt;

&lt;p&gt;The technology matters because it enables the workflow.&lt;/p&gt;

&lt;p&gt;Not the other way around.&lt;/p&gt;

&lt;p&gt;The best software is often not the software with the most features.&lt;/p&gt;

&lt;p&gt;It's the software that gets out of the way.&lt;/p&gt;

&lt;p&gt;Because in the end, most software is not feature design.&lt;/p&gt;

&lt;p&gt;It's workflow design.&lt;/p&gt;

&lt;p&gt;And the products that win are usually the ones that make progress feel inevitable.&lt;/p&gt;

</description>
      <category>design</category>
      <category>discuss</category>
      <category>product</category>
      <category>ux</category>
    </item>
    <item>
      <title>Why Doesn't Linux Break Every Week?</title>
      <dc:creator>Asesh</dc:creator>
      <pubDate>Tue, 26 May 2026 18:30:00 +0000</pubDate>
      <link>https://dev.to/abasu/why-doesnt-linux-break-every-week-495c</link>
      <guid>https://dev.to/abasu/why-doesnt-linux-break-every-week-495c</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Linux has thousands of contributors.&lt;/p&gt;

&lt;p&gt;Yet some commercial applications with dedicated teams seem to break every other update.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;One of the strangest realizations I had as an engineer was that both of these statements can be true at the same time.&lt;/p&gt;

&lt;p&gt;At first glance, it doesn't make sense.&lt;/p&gt;

&lt;p&gt;Surely a project with thousands of contributors should be chaotic.&lt;/p&gt;

&lt;p&gt;Surely more contributors should mean more bugs.&lt;/p&gt;

&lt;p&gt;Surely a tightly controlled commercial product should be more reliable.&lt;/p&gt;

&lt;p&gt;Yet some of the most dependable software in existence is open source.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Linux&lt;/li&gt;
&lt;li&gt;PostgreSQL&lt;/li&gt;
&lt;li&gt;Git&lt;/li&gt;
&lt;li&gt;Python&lt;/li&gt;
&lt;li&gt;Nginx&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Meanwhile, many commercial products regularly ship regressions, break workflows, remove useful functionality, or introduce bugs into places that previously worked.&lt;/p&gt;

&lt;p&gt;The obvious explanation is:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Open source somehow produces better engineers.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I don't think that's true.&lt;/p&gt;

&lt;p&gt;The real explanation is more interesting.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Myth of More Contributors = More Chaos
&lt;/h2&gt;

&lt;p&gt;Most people imagine open-source development working like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;More Contributors
        ↓
    More Changes
        ↓
     More Bugs
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That sounds reasonable.&lt;/p&gt;

&lt;p&gt;It just isn't how mature projects operate.&lt;/p&gt;

&lt;p&gt;Linux is not a giant shared Google Doc where thousands of people edit whatever they want.&lt;/p&gt;

&lt;p&gt;What Linux actually looks like is closer to:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Contributors
      ↓
 Maintainers
      ↓
Subsystem Review
      ↓
 Integration
      ↓
   Release
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Contributors propose.&lt;/p&gt;

&lt;p&gt;Maintainers decide.&lt;/p&gt;

&lt;p&gt;Networking maintainers review networking changes.&lt;/p&gt;

&lt;p&gt;Filesystem maintainers review filesystem changes.&lt;/p&gt;

&lt;p&gt;Kernel maintainers review kernel changes.&lt;/p&gt;

&lt;p&gt;The number of contributors is enormous.&lt;/p&gt;

&lt;p&gt;The number of people trusted to approve critical changes is much smaller.&lt;/p&gt;

&lt;p&gt;What appears chaotic from the outside is often highly structured on the inside.&lt;/p&gt;




&lt;h2&gt;
  
  
  Stability Is a Feature
&lt;/h2&gt;

&lt;p&gt;The next realization was that infrastructure projects optimize for very different outcomes than most applications.&lt;/p&gt;

&lt;p&gt;Many software companies optimize for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Growth&lt;/li&gt;
&lt;li&gt;Engagement&lt;/li&gt;
&lt;li&gt;New features&lt;/li&gt;
&lt;li&gt;Roadmap velocity&lt;/li&gt;
&lt;li&gt;Quarterly objectives&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Infrastructure projects optimize for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Reliability&lt;/li&gt;
&lt;li&gt;Predictability&lt;/li&gt;
&lt;li&gt;Backwards compatibility&lt;/li&gt;
&lt;li&gt;Trust&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Those are fundamentally different goals.&lt;/p&gt;

&lt;p&gt;A Linux user rarely wakes up hoping their operating system feels completely different today.&lt;/p&gt;

&lt;p&gt;A PostgreSQL user does not want a revolutionary new database experience every month.&lt;/p&gt;

&lt;p&gt;A Git user is not asking for dramatic workflow changes.&lt;/p&gt;

&lt;p&gt;Infrastructure succeeds when it becomes predictable.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The best infrastructure becomes boring.&lt;/p&gt;

&lt;p&gt;And boring software survives.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Success Creates Constraints
&lt;/h2&gt;

&lt;p&gt;Something else happens when software becomes widely adopted.&lt;/p&gt;

&lt;p&gt;Success makes change expensive.&lt;/p&gt;

&lt;p&gt;If a side project breaks an interface:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Ten people may be annoyed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If Linux breaks an interface:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Millions of systems may be affected.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If PostgreSQL breaks compatibility:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Entire businesses may be affected.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If Git changes fundamental behavior:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Development workflows around the world may be disrupted.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Success creates responsibility.&lt;/p&gt;

&lt;p&gt;The more successful a project becomes, the more careful it often becomes.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The more successful a project becomes, the more responsibility it accumulates.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This naturally creates pressure toward stability and backwards compatibility.&lt;/p&gt;

&lt;p&gt;Not because maintainers hate innovation.&lt;/p&gt;

&lt;p&gt;Because they understand who depends on them.&lt;/p&gt;




&lt;h2&gt;
  
  
  Open Source Has Different Incentives
&lt;/h2&gt;

&lt;p&gt;Many commercial products are evaluated through visible progress.&lt;/p&gt;

&lt;p&gt;New features are visible.&lt;/p&gt;

&lt;p&gt;Redesigns are visible.&lt;/p&gt;

&lt;p&gt;Announcements are visible.&lt;/p&gt;

&lt;p&gt;Reliability is usually invisible.&lt;/p&gt;

&lt;p&gt;Nobody tweets:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;PostgreSQL successfully preserved my data for another year.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Nobody posts:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Git behaved exactly as expected today.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Nobody celebrates:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;My operating system remained predictable.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Yet that's exactly the value these projects provide.&lt;/p&gt;

&lt;p&gt;Infrastructure software wins when nothing surprising happens.&lt;/p&gt;

&lt;p&gt;Its greatest achievement is often being forgotten.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Hidden Advantage
&lt;/h2&gt;

&lt;p&gt;The most surprising realization was that open source is not powerful because anyone can contribute.&lt;/p&gt;

&lt;p&gt;It's powerful because anyone can inspect.&lt;/p&gt;

&lt;p&gt;Bad ideas are visible.&lt;/p&gt;

&lt;p&gt;Design discussions are visible.&lt;/p&gt;

&lt;p&gt;Tradeoffs are visible.&lt;/p&gt;

&lt;p&gt;Mistakes are visible.&lt;/p&gt;

&lt;p&gt;The reasoning behind decisions becomes part of the project itself.&lt;/p&gt;

&lt;p&gt;Over time, mature projects accumulate something even more valuable than code.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Code
+ Design Discussions
+ RFCs
+ Bug Reports
+ Pull Requests
+ Maintainer Reviews
+ Historical Context
--------------------------------
Institutional Memory
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That institutional memory becomes a competitive advantage.&lt;/p&gt;

&lt;p&gt;New contributors don't start from zero.&lt;/p&gt;

&lt;p&gt;They inherit decades of lessons.&lt;/p&gt;

&lt;p&gt;In many cases, the project's greatest asset is not the code.&lt;/p&gt;

&lt;p&gt;It's the knowledge surrounding the code.&lt;/p&gt;




&lt;h2&gt;
  
  
  What This Means for Builders
&lt;/h2&gt;

&lt;p&gt;For a long time, I assumed reliability came from control.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;More&lt;/em&gt;&lt;/strong&gt; management.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;More&lt;/em&gt;&lt;/strong&gt; ownership.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;More&lt;/em&gt;&lt;/strong&gt; restrictions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;More&lt;/em&gt;&lt;/strong&gt; process.&lt;/p&gt;

&lt;p&gt;But some of the most reliable software in existence is built through &lt;strong&gt;collaboration&lt;/strong&gt; rather than &lt;strong&gt;control&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The lesson is not that open source is magically better.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The lesson is that reliability is rarely an accident.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It emerges from &lt;strong&gt;incentives&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;From &lt;strong&gt;review processes&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;From &lt;strong&gt;institutional memory&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;From maintainers who understand the &lt;strong&gt;cost of breaking things&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;And from cultures that treat &lt;strong&gt;stability as a feature&lt;/strong&gt; rather than an afterthought.&lt;/p&gt;

&lt;p&gt;The next time a project with thousands of contributors seems impossibly stable, it's worth remembering:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Linux does not stay reliable despite having thousands of contributors.&lt;/p&gt;

&lt;p&gt;Linux stays reliable &lt;em&gt;because it learned how to manage thousands of contributors without sacrificing the things that matter&lt;/em&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And that might be one of the most impressive engineering achievements in software.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>linux</category>
      <category>opensource</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>The Safety Net Is Always Open Source</title>
      <dc:creator>Asesh</dc:creator>
      <pubDate>Tue, 26 May 2026 10:05:20 +0000</pubDate>
      <link>https://dev.to/abasu/the-safety-net-is-always-open-source-fn1</link>
      <guid>https://dev.to/abasu/the-safety-net-is-always-open-source-fn1</guid>
      <description>&lt;p&gt;One of the most surprising things I've noticed about modern software is that &lt;strong&gt;open source is not always the first choice.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;But it is very often &lt;strong&gt;the last line of defense.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When everything is working, most people don't think about it.&lt;/p&gt;

&lt;p&gt;The SaaS product is convenient.&lt;/p&gt;

&lt;p&gt;The cloud platform is easy.&lt;/p&gt;

&lt;p&gt;The hosted API is reliable.&lt;/p&gt;

&lt;p&gt;The managed service removes operational burden.&lt;/p&gt;

&lt;p&gt;And honestly, that's often the right tradeoff.&lt;/p&gt;

&lt;p&gt;The interesting part happens when something breaks.&lt;/p&gt;

&lt;p&gt;Not necessarily technically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Economically.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Strategically.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Operationally.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That's when you discover where your safety net is.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Pattern Keeps Repeating
&lt;/h2&gt;

&lt;p&gt;A company adopts a SaaS product.&lt;/p&gt;

&lt;p&gt;The team grows around it.&lt;/p&gt;

&lt;p&gt;Workflows become dependent on it.&lt;/p&gt;

&lt;p&gt;Integrations are built.&lt;/p&gt;

&lt;p&gt;Knowledge accumulates.&lt;/p&gt;

&lt;p&gt;Everything works.&lt;/p&gt;

&lt;p&gt;Then something changes.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pricing increases.&lt;/li&gt;
&lt;li&gt;Features move behind higher tiers.&lt;/li&gt;
&lt;li&gt;An API becomes restricted.&lt;/li&gt;
&lt;li&gt;A product changes direction.&lt;/li&gt;
&lt;li&gt;A company gets acquired.&lt;/li&gt;
&lt;li&gt;A service shuts down.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Suddenly a question appears:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;What now?&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And remarkably often, the answer looks familiar.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An open-source alternative.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not because it is better.&lt;/p&gt;

&lt;p&gt;Not because it is prettier.&lt;/p&gt;

&lt;p&gt;Not because it has a larger marketing budget.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Because it is available.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Open Source Is the Place You Can Always Go
&lt;/h2&gt;

&lt;p&gt;That's the subtle advantage of open source.&lt;/p&gt;

&lt;p&gt;It doesn't have to win every comparison.&lt;/p&gt;

&lt;p&gt;It only has to remain accessible.&lt;/p&gt;

&lt;p&gt;A proprietary product can become unavailable.&lt;/p&gt;

&lt;p&gt;An API can disappear.&lt;/p&gt;

&lt;p&gt;A pricing model can change.&lt;/p&gt;

&lt;p&gt;A company can pivot.&lt;/p&gt;

&lt;p&gt;An acquisition can alter priorities overnight.&lt;/p&gt;

&lt;p&gt;Open-source software can be abandoned too.&lt;/p&gt;

&lt;p&gt;Maintainers leave.&lt;/p&gt;

&lt;p&gt;Communities shrink.&lt;/p&gt;

&lt;p&gt;Projects stagnate.&lt;/p&gt;

&lt;p&gt;But there is an important difference:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The software remains.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The knowledge remains.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The source remains.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The option remains.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And sometimes that option is all you need.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Escape Hatch Matters More Than People Realize
&lt;/h2&gt;

&lt;p&gt;Most people evaluate software by asking:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How many features does it have?&lt;/li&gt;
&lt;li&gt;How polished is it?&lt;/li&gt;
&lt;li&gt;How easy is it to adopt?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Those are reasonable questions.&lt;/p&gt;

&lt;p&gt;But builders eventually learn to ask another one:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;If I need to leave, can I?&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That question changes everything.&lt;/p&gt;

&lt;p&gt;Can I export my data?&lt;/p&gt;

&lt;p&gt;Can I self-host it?&lt;/p&gt;

&lt;p&gt;Can I repair it?&lt;/p&gt;

&lt;p&gt;Can I extend it?&lt;/p&gt;

&lt;p&gt;Can I continue using it if the company disappears?&lt;/p&gt;

&lt;p&gt;Open source rarely wins because of the first question.&lt;/p&gt;

&lt;p&gt;It often wins because of the second.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Safety Net Beneath Modern Software
&lt;/h2&gt;

&lt;p&gt;You can see this pattern everywhere.&lt;/p&gt;

&lt;p&gt;When cloud costs become unacceptable, teams look toward self-hosted infrastructure.&lt;/p&gt;

&lt;p&gt;When AI API pricing changes, teams investigate local models.&lt;/p&gt;

&lt;p&gt;When a note-taking platform locks down data, users search for export-friendly alternatives.&lt;/p&gt;

&lt;p&gt;When a communication platform experiences outages, people rediscover protocols and systems that existed long before the outage occurred.&lt;/p&gt;

&lt;p&gt;The details change.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The pattern doesn't.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The fallback option is often open source.&lt;/p&gt;

&lt;p&gt;Not because everyone wants to use it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Because everyone wants the option to use it.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Why This Matters for Builders
&lt;/h2&gt;

&lt;p&gt;The first time I realized this, I stopped viewing open source as merely a way to build products.&lt;/p&gt;

&lt;p&gt;I started viewing it as &lt;strong&gt;a form of resilience.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The primary value wasn't always convenience.&lt;/p&gt;

&lt;p&gt;It wasn't always speed.&lt;/p&gt;

&lt;p&gt;It wasn't even always cost.&lt;/p&gt;

&lt;p&gt;The value was knowing there was still somewhere to go if circumstances changed.&lt;/p&gt;

&lt;p&gt;A surprising amount of modern software depends on that assumption.&lt;/p&gt;

&lt;p&gt;Companies build on it.&lt;/p&gt;

&lt;p&gt;Developers build on it.&lt;/p&gt;

&lt;p&gt;Entire industries build on it.&lt;/p&gt;

&lt;p&gt;Most people never notice because the safety net is rarely the star of the show.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;You only notice it when you're falling.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  What This Means for Builders
&lt;/h2&gt;

&lt;p&gt;This doesn't mean every problem should be solved with open source.&lt;/p&gt;

&lt;p&gt;Nor does it mean proprietary software is inherently bad.&lt;/p&gt;

&lt;p&gt;Most teams should choose the tool that best solves their problem.&lt;/p&gt;

&lt;p&gt;The lesson is different.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The lesson is that optionality has value.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A system you can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;inspect&lt;/li&gt;
&lt;li&gt;self-host&lt;/li&gt;
&lt;li&gt;fork&lt;/li&gt;
&lt;li&gt;migrate from&lt;/li&gt;
&lt;li&gt;continue operating&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;gives you choices that closed systems often cannot.&lt;/p&gt;

&lt;p&gt;Those choices become more valuable as your dependency grows.&lt;/p&gt;

&lt;p&gt;The first time I understood that, I stopped thinking about open source as competition for commercial software.&lt;/p&gt;

&lt;p&gt;I started thinking about it as &lt;strong&gt;infrastructure.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not always the fastest path.&lt;/p&gt;

&lt;p&gt;Not always the easiest path.&lt;/p&gt;

&lt;p&gt;But increasingly, &lt;strong&gt;the path that's still there when the others disappear.&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;In **Open Source Is How Small Teams Build Big Things&lt;/em&gt;&lt;em&gt;, I wrote about how open source changed the starting line for software creation.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This realization came later: when the infrastructure underneath modern software shifts, breaks, becomes expensive, or disappears, the safety net is surprisingly often the same place that made small teams possible in the first place.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>cloud</category>
      <category>discuss</category>
      <category>opensource</category>
      <category>saas</category>
    </item>
    <item>
      <title>Open Source Is How Small Teams Build Big Things</title>
      <dc:creator>Asesh</dc:creator>
      <pubDate>Tue, 26 May 2026 09:08:50 +0000</pubDate>
      <link>https://dev.to/abasu/open-source-is-how-small-teams-build-big-things-16oc</link>
      <guid>https://dev.to/abasu/open-source-is-how-small-teams-build-big-things-16oc</guid>
      <description>&lt;p&gt;The first time I realized I could assemble capabilities that once required entire departments, my understanding of software changed completely.&lt;/p&gt;

&lt;p&gt;Before that, I thought software companies built most of their technology themselves.&lt;/p&gt;

&lt;p&gt;Need authentication?&lt;br&gt;
Build authentication.&lt;/p&gt;

&lt;p&gt;Need search?&lt;br&gt;
Build search.&lt;/p&gt;

&lt;p&gt;Need payments?&lt;br&gt;
Build payments.&lt;/p&gt;

&lt;p&gt;That seemed like the natural model.&lt;/p&gt;

&lt;p&gt;But the surprising thing about modern software is how much already exists.&lt;/p&gt;

&lt;p&gt;A typical application today sits on top of operating systems, databases, networking protocols, cryptography libraries, browser engines, package managers, frameworks, cloud platforms, and thousands of open-source projects.&lt;/p&gt;

&lt;p&gt;Most of those systems were built by people you'll never meet.&lt;/p&gt;

&lt;p&gt;Yet you inherit them anyway.&lt;/p&gt;

&lt;p&gt;A Flask application, for example, looks deceptively simple.&lt;/p&gt;

&lt;p&gt;But beneath it are layers of work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Linux&lt;/li&gt;
&lt;li&gt;Python&lt;/li&gt;
&lt;li&gt;OpenSSL&lt;/li&gt;
&lt;li&gt;PostgreSQL&lt;/li&gt;
&lt;li&gt;browser engines&lt;/li&gt;
&lt;li&gt;networking protocols&lt;/li&gt;
&lt;li&gt;package managers&lt;/li&gt;
&lt;li&gt;deployment infrastructure&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The visible application is often the smallest part of the system.&lt;/p&gt;

&lt;p&gt;The deeper stack is everything it stands on.&lt;/p&gt;

&lt;p&gt;That realization alone is interesting.&lt;/p&gt;

&lt;p&gt;The next realization is much more important.&lt;/p&gt;

&lt;h2&gt;
  
  
  Open Source Changes the Starting Line
&lt;/h2&gt;

&lt;p&gt;Open source doesn't simply reduce costs.&lt;/p&gt;

&lt;p&gt;It changes where you begin.&lt;/p&gt;

&lt;p&gt;Without open source, a team would spend years building infrastructure before they could start solving their actual problem.&lt;/p&gt;

&lt;p&gt;Before building a product, they would first need:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;authentication&lt;/li&gt;
&lt;li&gt;databases&lt;/li&gt;
&lt;li&gt;search&lt;/li&gt;
&lt;li&gt;queues&lt;/li&gt;
&lt;li&gt;deployment systems&lt;/li&gt;
&lt;li&gt;monitoring&lt;/li&gt;
&lt;li&gt;storage&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The product would become the final step.&lt;/p&gt;

&lt;p&gt;Open source changes that equation.&lt;/p&gt;

&lt;p&gt;Instead of starting from bare metal, modern builders start on top of decades of accumulated engineering work.&lt;/p&gt;

&lt;p&gt;Open source is accumulated engineering time that new builders can immediately access.&lt;/p&gt;

&lt;p&gt;That's what makes it powerful.&lt;/p&gt;

&lt;p&gt;Not that it's free.&lt;/p&gt;

&lt;p&gt;That it compresses years into days.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Real Surprise
&lt;/h2&gt;

&lt;p&gt;The really surprising thing is what follows.&lt;/p&gt;

&lt;p&gt;If databases, authentication, deployment, search, payments, monitoring, AI, and storage already exist...&lt;/p&gt;

&lt;p&gt;then most software companies are no longer building primitives.&lt;/p&gt;

&lt;p&gt;They're building the missing layer between existing capabilities and a user problem.&lt;/p&gt;

&lt;p&gt;That was the realization that changed how I viewed software.&lt;/p&gt;

&lt;p&gt;Modern software development is often less about building technology and more about discovering which layer is still missing.&lt;/p&gt;

&lt;p&gt;A research assistant does not need to invent databases.&lt;/p&gt;

&lt;p&gt;A note-taking application does not need to invent storage engines.&lt;/p&gt;

&lt;p&gt;A deployment platform does not need to invent operating systems.&lt;/p&gt;

&lt;p&gt;The challenge is figuring out how existing capabilities can be combined into something useful.&lt;/p&gt;

&lt;p&gt;The challenge is identifying what users still do not have.&lt;/p&gt;

&lt;p&gt;The challenge is building the missing layer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Small Teams Can Compete
&lt;/h2&gt;

&lt;p&gt;This is why small teams can now build things that once required organizations.&lt;/p&gt;

&lt;p&gt;Not because they can build everything.&lt;/p&gt;

&lt;p&gt;Because they don't have to.&lt;/p&gt;

&lt;p&gt;Instagram did not begin by inventing databases, mobile operating systems, or image processing primitives.&lt;/p&gt;

&lt;p&gt;WhatsApp did not need to recreate the entire telecommunications stack.&lt;/p&gt;

&lt;p&gt;Modern AI startups do not train every model, build every database, and write every framework from scratch.&lt;/p&gt;

&lt;p&gt;They build on existing foundations.&lt;/p&gt;

&lt;p&gt;They focus their effort on the layer that differentiates them.&lt;/p&gt;

&lt;p&gt;The infrastructure already exists.&lt;/p&gt;

&lt;p&gt;The leverage already exists.&lt;/p&gt;

&lt;p&gt;The opportunity is deciding where to apply it.&lt;/p&gt;

&lt;p&gt;Large companies still have advantages.&lt;/p&gt;

&lt;p&gt;They have distribution, capital, brand, and operational scale.&lt;/p&gt;

&lt;p&gt;But many of the historical advantages of large engineering organizations came from controlling infrastructure that smaller teams could not realistically build.&lt;/p&gt;

&lt;p&gt;Open source changed that.&lt;/p&gt;

&lt;p&gt;The cost of creation collapsed.&lt;/p&gt;

&lt;p&gt;The bottleneck shifted.&lt;/p&gt;

&lt;p&gt;Today, the hard part is less often technology.&lt;/p&gt;

&lt;p&gt;The hard part is understanding the problem clearly enough to know what should be built.&lt;/p&gt;

&lt;h2&gt;
  
  
  What This Means for Builders
&lt;/h2&gt;

&lt;p&gt;Open source does not make software easy.&lt;/p&gt;

&lt;p&gt;It changes where effort is spent.&lt;/p&gt;

&lt;p&gt;Instead of rebuilding operating systems, databases, networking stacks, and frameworks, builders can focus on understanding users and solving problems that remain unsolved.&lt;/p&gt;

&lt;p&gt;That is why open source matters.&lt;/p&gt;

&lt;p&gt;Not because it gives everyone the same tools.&lt;/p&gt;

&lt;p&gt;But because it allows more people to start from a much higher baseline.&lt;/p&gt;

&lt;p&gt;The first time I understood that, I stopped looking at software as a collection of technologies.&lt;/p&gt;

&lt;p&gt;I started looking at it as a collection of layers.&lt;br&gt;
Most of those layers already exist.&lt;br&gt;
So, the most valuable work is not creating a new primitive.&lt;br&gt;
It's discovering which layers already exist, and identifying the smallest missing layer between existing capabilities and a real user problem.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>productivity</category>
      <category>softwaredevelopment</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
