[throwaway277432]

I contributed well-researched answers already when I was ostensibly a very junior dev, and even before that during my CS studies. Stuff you can lookup or simply try out is doable, of course questions where you need experience aren't a good fit.

When I was in high school I read the docs, and learned C++ from books and MSDN. Granted my access to the internet was rather limited back then, but it also never crossed my mind to bother people for things I could easily lookup myself.

Growing up in a RTFM, "search the forum first before asking" environment is seen as toxic today, but it really helps keeping certain behavior in check thats a drag on society as a whole.

One of the best mentors/bosses I ever had never answered coding questions directly, but always in the form of a question so I could look it up and learn for myself.

I try to do the same with my junior devs today, unless there's time constraints or they're under stress, I try to let them figure out the final answer themselves.

[8n4vidtmkvmk]

I find there's a time and a place for RTFM, and it's usually not at the start of the project when you know the least. When you're just starting, you just want to get something working. Being spoon-fed some answers to get past a few hurdles is rather nice. But then there comes a point where you have to stop and be like "Okay, what the heck is this actually doing? How does it work?".

I just hit that point with some TensorFlow stuff because I started hitting the limits of what ChatGPT could answer successfully, and I think that's fine. But maybe good that I couldn't get everything out of it or it may have delayed my learning further yet. Which I guess reinforces your point.