|
|
|
|
|
by lapcat
380 days ago
|
|
> and just to play devil's advocate Your comment would be improved by simply removing that phrase. It adds nothing and in fact detracts. > just like with open vs. closed offices or remote vs in-person, maybe some people have all the human interaction they want outside of work and don't mind "talking" to some AI as long as it gets shit done in the manner they want. You're presenting a false dichotomy. If someone doesn't enjoying mentoring juniors, that's fine. They shouldn't have to. But why would one have to choose between mentoring juniors or babysitting LLM agents? How about neither? sasmithjr was apparently trying to defend babysitting A.I. by making an analogy with mentoring juniors, whereas I replied by arguing that the two are not alike. Whether or not you enjoy using A.I. is an entirely separate issue, independent of mentoring. |
|
I regret adding that last bit to my comment because my main point (which I clearly messed up emphasizing and communicating) is that I think you’re presenting a false dichotomy in the original comment. Now that work can be done with LLMs asynchronously, it’s possible to both write your own code and guide LLMs as they need it when you have down time. And nothing about that requires stopping other functions of the job like mentoring and teaching juniors, either, so you can still build relationships on the job, too.
If having to attend to an LLM in any way makes the job worse for you, I guess we’ll have to agree to disagree. So far, LLMs feel like one of many other automations that I use frequently and haven’t really changed my satisfaction with my job.