---
title: "Discussion on \"Is AI making software engineering boring & us lazier?\" | Hashnode"
description: "Discussion on \"Is AI making software engineering boring & us lazier?\". Before AI—or I could say before the big boom of Claude’s Opus 4.5—programming was pretty much the same as it had always been. People wrote their own code, collaborated on PR reviews, chatted, etc. Peo"
url: "https://hashnode.com/posts/is-ai-making-software-engineering-boring-us-lazier/6afbc043292c87a8735c39bf"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Is AI making software engineering boring & us lazier?](https://sethphat.dev/is-ai-making-software-engineering-boring-us-lazier?utm_source=hashnode&utm_medium=feed)

Before AI—or I could say before the big boom of Claude’s Opus 4.5—programming was pretty much the same as it had always been. People wrote their own code, collaborated on PR reviews, chatted, etc. Peo

11h ago · 5 min read · sethphat.dev  
Read the article

## Written by

[Seth Chen](https://hashnode.com/@sethphat)

@sethphat · Desire Grand Prix

  
[View profile](https://hashnode.com/@sethphat)

Seth Phat Geek Blog

develops awesome software, contributes to OSS, writes tech tips, and loves Vietnamese milk coffee!

## Responses 5

Markdown supported · ⌘↵ to post

[Ki Taits](https://hashnode.com/@taitski)

[6h ago](https://hashnode.com/posts/is-ai-making-software-engineering-boring-us-lazier/6afbc043292c87a8735c39bf/comment/6afc09d67e230c4b865f9452)

The mismatch you mention is so real: generated comments that run on forever, then variable names so short you can't tell what they do. I don't mind a first draft from a model, but I rewrite the names and comments before I commit so I can still find my way around later.

[Seth Chen](https://hashnode.com/@sethphat)

[3h ago](https://hashnode.com/posts/is-ai-making-software-engineering-boring-us-lazier/6afbc043292c87a8735c39bf/comment/6afc09d67e230c4b865f9452#reply-6afc3ab7e43409abca720633)

That’s great work & thoughtful of you. The more we think about the people who’ll deal with our code later, the more effort we put into making it readable. Time is not a strict requirement nowadays, but super high quality is.

Let’s keep that up 💪

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[8h ago](https://hashnode.com/posts/is-ai-making-software-engineering-boring-us-lazier/6afbc043292c87a8735c39bf/comment/6afbedcb99aa86bffb9a8266)

The review rule is the part I will keep. If I cannot explain what the generated code does, I do not really own it, and I will be the one debugging it later. I also liked the split you use: write the backend yourself to stay sharp, and let AI help on the frontend only after a real review and testing. That keeps the skill and the speed in the right places.

[Seth Chen](https://hashnode.com/@sethphat)

[7h ago](https://hashnode.com/posts/is-ai-making-software-engineering-boring-us-lazier/6afbc043292c87a8735c39bf/comment/6afbedcb99aa86bffb9a8266#reply-6afbf62e4db83d21a3f88e87)

Thanks!

In this AI age, getting too comfortable & lazy will get us nowhere. Staying sharp, keeping up the practice, and learning will always take us somewhere good. I don’t think it’s much different from the pre-AI days, but the pressure is definitely higher.

[delta executor](https://hashnode.com/@deltaexploitts)

[3h ago](https://hashnode.com/posts/is-ai-making-software-engineering-boring-us-lazier/6afbc043292c87a8735c39bf/comment/6afc3a26bcf778d06664d0e3)

The discrepancy you point out is really evident: produced comments that never end, followed by variable names that are so brief that it is impossible to understand their purpose. A model's first draft does not bother me, but I change the names and remarks before committing so I can still figure things out later.
