I used to a firm advocate of “learning for yourself”. By which I mean, I spent most of my time learning through trial and error. For example, If I didn’t know why a bake was turning out correctly. I would adjust what I know, do some reading and apply it. If that didn’t work, then repeat. Pre 2017 I rarely asked questions to others or strangers pertaining to technical problems, because I thought I should be able to figure it out on my own. I had even been told to “figure it out” when I did ask, which lead me down a path like that. Ultimately I was able to figure out most of my problems, but as I’m getting older I’m starting to realize something. Why on earth did I do that? these problems I was having weren’t new, and people much smarter than me had already solved simple issues (such as baking errors, and etc) many times over. Why didn’t i just ask? Why didn’t i just look for a course for that specific subject? I’m finding, more recently, that my time is an extra valuable resource, and as life’s demands start to pile up, just figuring out, isn’t an efficient option any more.
When someone asks me an easily searchable question, I like to answer specifically what they asked, and give them a link to a source where they can read more. I have no problems with that. And if the problem gets more specific, and is within my skill set I’ll attempt to answer fully, to my complete capabilities. I think the only caveat to that, is putting in some effort. If you’ve tried something, and it didn’t work, thats fine. I’ll help. Atlas you tried. My father always told me, Dont ever ask a question you dont already have an answer to. I like to apply that to 3D .
What are your thoughts on this? I’d like to hear some differing opinions. or maybe some different interpretations of this.
Replies
Overtime however, and the more you understand about 3D knowledge, I feel constantly asking for help actually becomes a hindrance. There really are a lot of tutorials out there that all you have to do is spend a few minutes reading and it will answer all your questions. Or just go through the polycount wiki and all the topics are there with similar questions answered. But again, this is because I've been doing 3D art now for 6-7 years, so I don't have much patience anymore to wait for answers and just want to get my work done on time.
I think i see where you're coming from, albeit I think its still really important to ask. I'd rather not re invent the wheel if I dont have to. What do you think? or am I mis interpreting you here.
Of course, it's always depends on the situation. I did ask my first tech question in what was almost a year recently, but that's because the topic I had felt way too serious to leave it up to chance.
i remember the time when i was starting out and a lot of things were unclear because you just don't know the name of the thing you are looking for and have a lot of gaps for basic things, so if i can help out and it takes me 10min to make some screenshots and give a short explanation, or look up a specific link and post it, no problem
asking questions myself is a different matter
after a certain time working in the field you most likely have heard all the terms and know how most things work, even if you haven't done them yet yourself. Most of the time its easier to just google the topic and look up an article/video about the topic
Ultimately, I think it's okay to ask questions (especially troubleshooting), as long as you're also doing your part to give back to others. Things like giving pointers for student work and answering questions for others that maybe took some time for you yourself, to master.
Then I take in whatever info I found and start playing around with it myself. It might be slower than just getting an answer right away, but I learn best by doing. Plus it gives me experience in doing whatever this new thing might be, so next time I use it, I at least know a little about it. My point of view for learning all this stuff in 3d, is that someone can give an answer, but only if they fully understand the question being asked. And that's the rub- the person asking might not know they're asking the wrong question, or doesn't give enough info to properly answer the question for one reason or another.
Now when you're in a studio using proprietary tools that have a lot of tribal knowledge behind them and little to no documentation, you're better off just asking because you can't google the answer and there are deadlines to consider. When you are also confronted with a more advanced problem that isn't as well documented, asking might not hurt either because in this case asking can help contribute to the pool of community knowledge. An example I can think of here on Polycount is when DOTA2 came out, vertical gradients in your textures were all the rage and there wasn't a whole lot of knowledge of how to pull it off. So people asked questions and the community where able to come up with a bunch of solutions, some of which are still viable today and can be found on the wiki.
I highly recommend reading through this, it's for programming but it can easily be applied to art: How to Ask Questions the Smart Way
Anyway sharing plays a vital part why I've remained an active forum contributor over the years coupled alongside a personal sense of satisfaction when my comment/s happens to help or point someone in the right direction.