Sane prompt for u my friend: do not generate tech debt.

Theres vibe coding and there’s ai assisted coding. The former is bullshit and causes more problems than it fixes. The latter is great and you should lean into it. There was a post a few days ago about a rule file for using Claude code effectively. (I never bothered to learn the hn rules on linking so google it up with site:)

You should start building a rule file listing every way it screws up and a) warning it not to b) watching for it. Errors I’ve seen: failure to follow best security practices, failure to plan properly, failure to update variable names, lies, bad tests, stuck in a rut flip flopping between two possible paradigms Get into it, get better at it than your CEO and CTO, save them from the worst of their folly.

And simultaneously start looking for another job because you clearly don’t like them and disagree with their strategy in important ways.

AI assisted coding is the future, but probably not the way they’re doing it. But pain is the best teacher so dive in and feel that pain.

Zooming out the problem is micromanaging vs. let those on the shop floor make decisions. You are being told how to work. If everyone but you agrees maybe it is time to consider a move. Your story paints a worldview you have that will be loved by some companies I think.

If it is CTO only and the engineers all disagree. Maybe worth thinking about how to get that voice heard without ruffling feathers.

Try an evaporating cloud! This is a bit heavy to read but is a good technique to think about. It is so good it might change YOUR mind too about this situation! It looks to get to the facts and once practices is a good tool to use.

https://en.m.wikipedia.org/wiki/Evaporating_cloud

Tldr is they want vibe coding because X and you want not vibe coding because of Y. The assumption is Y = !X but if it isn't there could be a good win win.

> delete entire unit test file & have claude generate a new one

Why not just add new tests or refactor the existing ones? Seems kind of silly.

Aside from that:

  - if you don't like AI tools and can afford to do so, then look for a place that matches how you want to work
  - if you do like AI tools, or are open to learning them, then there isn't an issue (aside from maybe how they're used)

There isn't much more to it: https://blog.kronis.dev/blog/ai-artisans-and-brainrot (bit of a rant of mine on the topic, the tl;dr would be that the cat is out of the bag in regards to these tools and there are both positives and negatives, but they lead to brainrot and degradation of skills the same way how IDEs and StackOverflow did, just a large leap further)

This AI nonsense has infected every company and everybody is an "AI expert". You can't escape it and you'll be at a competitive disadvantage at another employer when starting from scratch. The thing about this AI fad is that nobody has really figured out where the real utility is to be gained and how to reduce costs from that.

Yeah, you should start looking for a new role immediately.

Suggest they C suite be replaced with vibe managing.

Make fun of their outputs

impressive that you're a senior engineer after only 5 years

[dead]