Indie App Devs #14
Weekly tips for indie app developers.
Hello! 👋
Indie App Devs newsletter is back after a few weeks off!
In today’s post, Damjan Dabo talks about why 2026 is a turning point for software developers and shares his thoughts.
In the first issue a few months ago, Damjan shared What your app’s MVP needs to have? If you missed it click HERE to read it.
Sponsor 🤝
Struggling to Market Your iOS or Android App? Try Affiliate Marketing
Growing a mobile app is hard — especially when ads are expensive and user acquisition doesn’t convert because attribution breaks with in-app purchases and subscriptions.
Insert Affiliate lets iOS and Android apps grow through performance-based affiliate marketing that actually works with in-app purchases.
Track referrals, attribute subscriptions, and reward creators and partners using a lightweight SDK built for modern mobile apps.
No web hacks. No broken attribution. A realistic way for indie devs and small teams to grow.
AI Won’t Replace You. Ignoring It Might.
At the beginning of 2026, many developers feel uneasy.
You can hear it in conversations, see it in comments, and feel it in the tone. When AI comes up, reactions often fall into the same patterns: sarcasm, dismissal, or quiet avoidance. Not because developers do not understand what is happening, but because they do.
AI-assisted development, especially agentic coding, does not just introduce new tools. It challenges how developers think about their value, their status, and their long-term relevance.
That anxiety is understandable. But pretending nothing is changing is not a strategy.
The Anxiety Nobody Wants to Admit
Most developers are not afraid that AI will suddenly take their job tomorrow.
They are afraid of something more subtle:
becoming less important
losing the edge that made them valuable
watching expectations rise faster than they can adapt
For a long time, being a strong developer meant being very good at writing code. That skill still matters. But it is no longer the only thing that matters.
AI forces an uncomfortable question:
If code becomes easier to produce, where does my value come from?
2026 Is a Turning Point, Not a Hype Cycle
We have seen hype cycles before. This feels different.
Agentic coding is not just better autocomplete. Modern tools can:
explore large codebases
reason across files and modules
refactor with real context
generate meaningful tests
assist with maintenance and documentation
The result is not a small productivity boost. It is a structural shift.
Developers who use agentic workflows effectively are already significantly more productive than those who do not. In startups and small teams, this gap is immediately visible. In larger organizations, it compounds quietly over time.
This is no longer optional if you care about effectiveness.
What Agentic Coding Actually Is (and What It Isn’t)
Agentic coding is best understood as delegation, not automation.
Think of agents as assistants:
one helps with implementation
one helps with refactoring
one writes or extends tests
one reviews code and suggests improvements
one handles repetitive maintenance tasks
What they do not do is take responsibility.
The human developer still:
defines the problem
makes architectural decisions
sets constraints
reviews everything
owns the final result
Using AI does not remove responsibility. It concentrates on it.
The Real Risk Isn’t Bad AI Code, It’s Avoidance
A common fear is that AI will introduce low-quality or insecure code.
That can happen. But it is not the biggest risk.
The bigger risk is avoiding AI entirely or letting its use happen in an unstructured, unreviewed way.
That leads to:
inconsistent usage across teams
fear-driven decisions
fragmented workflows
lost productivity
falling behind competitors who already adapted
Avoiding AI does not preserve quality. It preserves comfort.
Why T-Shaped Developers Win in an Agentic World
As implementation becomes cheaper, context becomes more valuable.
T-shaped developers combine:
depth in one or two areas
broad understanding of systems, architecture, security, and product goals
Agentic coding amplifies this. It rewards developers who can:
see the bigger picture
make tradeoffs
connect technical decisions to business outcomes
review and guide execution effectively
Deep specialists will always matter, especially in low-level or highly complex domains. But most companies are not building compilers, kernels, or cryptographic primitives. They are building business software, mobile apps, dashboards, APIs, and internal tools.
In those environments, judgment beats extreme perfectionism.
Unlocking Builders Beats Perfect Craftsmanship
Historically, so-called idea people were limited. Ideas without execution rarely went anywhere.
Agentic coding changes this balance slightly.
Execution still matters. Quality still matters. But the cost of execution is lower. That increases the value of people who can unlock execution, including themselves.
Someone like Steve Jobs was not writing production code. His impact came from vision, taste, prioritization, and the ability to guide great engineers toward the right problems.
This does not make craftsmanship irrelevant. It reframes value.
Agentic coding rewards developers who can move between ideas and execution, not those who stay rigidly in one lane.
Indie Development: A Practical Path to Becoming T-Shaped
One of the fastest ways to build these skills is indie development.
In many companies:
you get tasks, not problems
architecture is already decided
product strategy happens elsewhere
marketing and distribution are invisible
As an indie developer, you cannot avoid these things.
You have to:
scope features
design UX
make performance compromises
think about users
care about shipping and feedback
Agentic coding makes this even more powerful by lowering the cost of experimentation. You can learn faster, iterate more, and focus on decisions instead of boilerplate.
This is not about quitting your job. It is about expanding your skill surface.
What If Your Company Is Slow or Restrictive?
Many developers work in environments where AI tools are restricted or forbidden.
That includes:
banks
fintech
large enterprises
government and public sector organizations
regulated industries in general
The reasons vary: security concerns, compliance requirements, slow internal processes, or simple organizational inertia.
That is understandable. But it is not a reason to stop learning.
Even if you cannot use agentic coding at work today, you can still:
experiment on side projects
build small apps
explore workflows in safe environments
learn how these tools behave in practice
Your long-term value should not depend entirely on your employer’s current policies.
Your career is longer than any single company.
Staying on Top of Change: Why Tech X Matters
Learning in 2026 is continuous.
Tech X plays a role similar to what Tech Twitter once did. It is where ideas, workflows, experiments, and honest takes appear early, long before they show up in conferences or official blog posts.
It is especially valuable for:
agentic coding workflows
indie development insights
tooling discoveries
real-world lessons from people actually shipping products
You do not need to post constantly. Simply observing and staying exposed helps build intuition over time.
If you are interested specifically in indie development in the agentic coding era, you can follow me on X.
Proximity to change matters more than perfectly planned learning.
How to Start Without Overwhelming Yourself
You do not need to master agentic coding overnight.
Start small:
experiment on side projects
use agents for exploration, not blind production
review everything
stay curious, not defensive
Focus on becoming a better:
decision-maker
reviewer
system thinker
That is where long-term value is shifting.
Final Thought
AI is not replacing developers.
But it is changing what makes developers valuable.
Those who adapt become more autonomous, more effective, and more resilient. Those who avoid the shift may not lose their jobs immediately, but they will slowly lose leverage.
We are not adopting AI to write more code faster.
We are adopting it to think better, build better, and deliver better without compromising quality or responsibility.
Want to learn more?
If this topic resonates with you and you want to keep learning by following Damjan on X & LinkedIn.
If you're curious what he's building, check out his apps and projects here.