People rarely enjoy all aspects of their job equally. This is particularly noticeable with fullstack developers who are expected to be proficient across the entire stack. From transforming Figma mockups into functional UIs to implementing complex architectural services. The range of skills required is… let’s call it extensive.

At some point the industry decided fullstack was the ideal. You should handle everything from pixel-perfect CSS to database optimization because… it’s efficient? More cost-effective?

Outside of solo entrepreneurs I’ve met remarkably few developers who genuinely enjoy both ends of the spectrum equally. Most have clear preferences. They either light up discussing UI interactions or get excited about backend architecture but rarely both.

This preference gap can explain why tools like vibe coding are gaining popularity. These tools reduce the parts of development work people enjoy least while still getting the job done.

You can build great things that feel effortless now. That simplicity exists only because you invested hard effort earlier.

Like grinding through side quests in a game before tackling the main storyline. All that seemingly extra work makes the final boss battle feel surprisingly manageable.

Tech influencers often preach ‘If it’s easy, it’s probably not special.’ But they miss the timeline. What feels easy today only seems that way because you already did the hard work yesterday.

I’ve found AI actually demands a different kind of thinking from me.

When I’m vague, it gives vague results. This forces me to clarify my own thinking and be more precise.

The cognitive work doesn’t disappear, it shifts to higher level of design and critical evaluation.

The challenge is using AI intentionally rather than letting it replace our thinking entirely.

We are entering an era where users no longer navigate the web through links, but through conversations with AI. These systems don’t just point to information, they break it down into bits and pieces that they can then join, personalize and deliver directly to you. Search results, news pages and social feeds are slowly being replaced with AI assistants that process information on our behalf.

Sure there’ll be links, but think of them more as page 2 of Google results. People that want answers want them quick and GenAI delivers right now.

How this will disrupt the ads business, a business where number of eyes is important we don’t know yet. But just think about the effect it has when an AI Assistant searches on your behalf and give you the results you need.

Social media is no longer social, it is just media. We’ve forgotten to remove the “social” part when we talk about it.

We once came to these platforms to see what our friends were up to. Then we returned because we got what they predicted we should like. Now they’re no different than TV streaming or radio except for their more efficient dopamine-triggering mechanisms.

Algorithms are not social.

Throughout my development career I’ve probably been acting like a code chameleon. Join a company, look at PRs and code and try to mirror the style and ask the subtle question of “Which code and PRs should I mimic if I want my submissions to pass quickly?”

This adaptive behavior isn’t just about following rules. It’s about understanding the unwritten language of this new codebase. That teams develop patterns and practices that represent their knowledge.

Current AI coding tools miss this context. They generate functional but generic code drawn from open source repositories, that in isolation are awesome but in relation to existing internal codebases are off.

They write average code for specific environments that don’t want to be average.

Beyond Simple Generation

I believe we’re heading toward a more sophisticated approach with specialized AI agents handling different aspects of development.

Solution Agents that focuses purely on solving the problem, functionally without concern for style or conventions. Adaptation Agent that transform this solution to match the companies specific patterns and practices and possibly a Readability Agent that ensures that this code is comprehensible by humans.

First write the expectations, then generate the code, then create tests, then refine the code. Each step handled by agents optimized for that specific task.

This mirrors how human teams work today. Establish direction, implement solutions, and ensure quality and consistency. The difference is speed and scale.

The Future of Development

The most powerful development environments won’t be those that simply generate code fastest. They’ll be systems that understand your specific codebase deeply and adapt to your team’s unique approach.

When you begin a project, you’ll decide upfront what you want: TypeScript, specific linting rules, run on Cloudflare. But beyond these technical choices, your AI system will learn what makes your codebase unique.

Unlike the patterns found in open source repositories, your AI agents will understand the complete picture of your application. They’ll recognize that teams evolve their own concepts and styles that may not match external patterns.

This is the natural progression from todays word-by-word generation to truly contextual development assistance.

It’s not just about writing code, it is about writing code that belongs.

These last quarters I’ve seen one CEO, CTO or Founder after another saying something to the effect “AI will take your job, adapt or die”.

I used to have a great mp3 collection, you know, back in the days when it was almost considered legal.

It was an amazing feat to keep it up to date in Winamp and later iTunes with correct titles and album art. There came apps that focused solely on this catalogue part using online sources to update the metadata called ID3.

Then came Spotify and changed that completely. That time spent curating was just sunk cost and my well catalogued mp3s are probably on an old dying hard drive somewhere in the house.

This is the reality we must face when it comes to AI and as a developer I see this so vividly.

What used to be “LLMs cannot code” became “LLMs write bad code” and now “LLMs write ok code”.

So we shift focus and find a new weak spot: LLMs cannot fix bugs. Or I cannot understand the code it writes.

But then again, the code I struggle to understand, it can explain to me 99% of the time. The ability to both generate and explain complex code further diminishes our position as keepers of the technical knowledge.

We move the focus to what it cannot do while something else comes along that changes the playing field, a new Spotify emerges and changes it all.

LLMs with the context memory of your complete repository. With the knowledge of every commit and every connected ticket. That can understand the reason behind the change in an iterative fashion. You will not need to understand the code. It will need to understand the code.

You will need to understand what you want to achieve and why. This understanding of purpose becomes our core value proposition as technical professionals.

As AI Agents emerge and become reliable we will prompt it with “increase the convert rate by 10%, these are the amounts of visitors we have, make small changes until you reached your goal or you need my attention, you have one quarter”.

Why is this happening so quickly? There’s an economic incentive at play. Developer salaries, especially in Big Tech, have skyrocketed over the past decade. AI development may be running at a loss now, but it might be following the Starbucks playbook of crowd out competition first, then raise prices. Companies investing billions in AI aren’t doing it for novelty. They’re eyeing the massive labor costs they could eliminate. Right now AI is marketed as an assistant, but the financial motivation to replace rather than augment is powerful.

So where does this leave us as developers? We need to move up the value chain. If algorithms can handle implementation, we must master the intention behind it. This brings us back to first principles thinking.

These are the first principles that we aim at: Why do we build this service? What do the end users aim to solve?

This will be the hardest problem to understand and execute on. If my technical skills are not required as they used to be, what should I focus on instead?

History gives us a clue. In the past, key makers, cobblers and tailors used to be three separate jobs. As the market changed, their crafts were not needed to the same extent, but those who survived saw that with their dexterity they could adapt to new needs.

My view is that multiple technical crafts will join together, and our focus will shift toward the complete value chain rather than isolated implementation details. We’ll need to understand the whole picture to remain relevant.

Those first principles will not be: to write code.

How will we keep brand awareness when we use AI to generate our images?

I see the same style cartoons popping up across business social networks.

People generate fun images to pair with their messages. The visuals look cute but generic, completely out of brand and identical to everyone else’s. You might get some laughs. But nobody remembers which brand posted it.

Is that temporary engagement worth sacrificing your visual identity?

This happens when we become attached to the first thing we see. Then it becomes a struggle to think of other possibilities.

Have an instinct to ship. Not an instinct to polish.

I know it is scary, releasing a product in the wild.

Whatever product that is, piece of music, a service, an idea, make an effort to ship fast to a minimum viable audience.

Viable audience means someone who has a stake or is interested in your product, not your friends or your family.

Shipping means being open to fail. You cannot fail, or succeed without shipping. you just do.

I’m also scared about shipping. Probably or especially when you’ve just built something for yourself.