I'm very open about method and techniques and I have even given away quite a lot of code.
Quite a lot I get asked to share my prized works (the water in WaterWorld, the terrain in my procedural Dragonrage engine) and it's always hard to share the latest and newest thing - it's "my" work let "me" exploit it first... I get asked for the code, not help in making a simular (but different) system, and that makes it a harder pill to swallow.
I'm quite happy to explain how i've done stuff, i'm quite happy to explain methods, but I rarely give code out because people start chopping it, changing it, and asking questions about their integration problems that take hours for me to sort out - or they make no changes at all and expect it to just work in their program, when the visual scale is wrong or it's placed above the camera because they coded it differently to me - in which case explaining the bug to them also involves teaching them the basics of programming, which is too tiresome.
Also if I just give code out you havn't learned anything. I'd rather teach a few how to do something (albeit only my way!) then give everyone a library that they'll take for granted.
On the ocassions when I do post for help here (4-5 times this year) I make sure I then answer at least half a dozen questions from others to pay for that help. However I mostly do my tutoring (and learning) on closed boards nowadays, I just come to Blitz because there's lots of activity which helps pass away some time and provides a good distraction to break up the day.
Quite a lot I get asked to share my prized works (the water in WaterWorld, the terrain in my procedural Dragonrage engine) and it's always hard to share the latest and newest thing - it's "my" work let "me" exploit it first... I get asked for the code, not help in making a simular (but different) system, and that makes it a harder pill to swallow.
I'm quite happy to explain how i've done stuff, i'm quite happy to explain methods, but I rarely give code out because people start chopping it, changing it, and asking questions about their integration problems that take hours for me to sort out - or they make no changes at all and expect it to just work in their program, when the visual scale is wrong or it's placed above the camera because they coded it differently to me - in which case explaining the bug to them also involves teaching them the basics of programming, which is too tiresome.
Also if I just give code out you havn't learned anything. I'd rather teach a few how to do something (albeit only my way!) then give everyone a library that they'll take for granted.
On the ocassions when I do post for help here (4-5 times this year) I make sure I then answer at least half a dozen questions from others to pay for that help. However I mostly do my tutoring (and learning) on closed boards nowadays, I just come to Blitz because there's lots of activity which helps pass away some time and provides a good distraction to break up the day.