Quote:
Originally Posted by iMack007
damn!! that was a bit harsh to say the least.
|
I apologize if I sounded harsh. I though I was very friendly, just being honest.
Quote:
Originally Posted by iMack007
In any event, the facts you pointed out remain valid, but surely throwing out such questions in the first place may do what the original poster intended, attract the attention of a developer or someone who DOES know how this can be achieved.
|
I am a developer and have been for a few decades. The one part about reusing redundant code is basically a good idea and is the way we work by using frameworks, APIs, etc. But the part where he says to go into other people's code and remove redundant code goes against everything that's good and right in the world of OOP.
It can't be done the way he's saying and that's my point. It's like a cave man speculating how how to make a space ship go faster. He has no reference so he's just going to say nonsensical things and will be ignored as someone not willing to "learn the language."
We get a lot of this in the software business so we tend to just ignore these people that want to tell us how to do things without knowing anything about them. We usually call those people "managers."
Imagine if you were a medical doctor and someone told you to, "Just make everyone's inside good." Or if you were an airline pilot and your boss told you to, "Just make the plane go faster." Or if you were a general and the president ordered you to, "Just invade that country."
You see? I'm not being mean. I'm just pointing out that if you want to discuss a thing or improve a thing it's good to go do some research first before coming to any conclusions. It's great to think about how things might work, that's how people come up with new ideas, but don't let that stop you from learning how they actually work.
Again if I sounded harsh that was not my intent so I apologize if I offend you.