←back to thread

118 points soraminazuki | 1 comments | | HN request time: 0.385s | source
Show context
marc_abonce ◴[] No.45080662[source]
The most important advice for people in this situation, from the article:

> I’d say my overarching advice, based on how difficult tech recruitment is right now, is to sadly play along. But — and I cannot stress this enough — make sure you document everything.

> What I mean by that is every single time AI tools cause problems, slow-downs and other disappointing outcomes, document that outcome and who was responsible for that decision. Make sure you document your opposition and professional advice too.

Personally, I would just add a warning to be careful to blame the tool, not the person. Otherwise, you will be seen as the "bad" person in the story even if your report is technically correct.

replies(3): >>45080702 #>>45080794 #>>45080868 #
1. mkagenius ◴[] No.45080702[source]
The question shouldn't be whether we should use it or not but that how can we use it so that we are more productive than before.

In future, there will be some sort of "method" or should I say "art" in how we use the ai tools.

It's very easy (and frustrating) to just say "try again, <error log>" without knowing fully what's going on. The transformation from a coder to a code manager would need some sort of learning to be good at it.