Article may be outdated

This article is 8 days old. Some details may have changed since publication.

Hacker News·5 min read·hard

On Being an Engineer in 2026

T
talboren
On Being an Engineer in 2026
✦AI Summary

A software engineer reflects on the changing nature of their profession as AI agents increasingly handle coding, writing, and architectural tasks. The author argues that despite the automation of technical work, human intuition remains a necessary check against 'AI slop'.

Why it matters

This perspective captures the growing anxiety and shifting role of human expertise in an industry rapidly adopting generative AI.

✦Dive DeeperCreate a free account to unlock

We all feel it. Every other week, we lose or delegate another part of our work to agents. It started with giving up on writing code. Then it expanded to pretty much any writing - Slack messages, documents, emails. Since around Opus 4.6, debugging, once an art and something that made us proud, became clicking on the recommended option in Cursor. And with better harnesses, even architecture and high-level thinking started moving to agents.

My day-to-day now mostly consists of making sure my agents aren't blocking other people's agents (which is another topic worth writing about).

This naturally leads us to think that this is it. We, engineers, are doomed.

But before you start thinking, again, about which jobs are "AI-protected", let's take a step back.

Continue reading on Headlinne

Create a free account to read the full article.

Read full article →
technologyculture
✦

Get smarter about the news

Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.

Create free account

Already have an account? Sign in