|
MRLacey wrote: To be a good developer requires experience.
To be a great artist, one studies the previous masters of art.
Why don't software developers study previous masters? Instead, we learn the same mistakes over again.
Gary
|
|
|
|
|
I found this to be a very big weakness with the formal education that I got. There was very little dissection of previous well written works.
John
|
|
|
|
|
I agree. The 500K+ lines of MFC code I have written since I have started working in 1997 are what I consider my biggest asset as a programmer.
John
|
|
|
|
|
I bet, common sense make you better developer!
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief and You/codeProject$$>
|
|
|
|
|
Alas, there's no such thing as common sense. - It just isn't common!
|
|
|
|
|
in my experience common sense in this field is, more often than not, dead wrong.
|
|
|
|
|
mean! ?
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief and You/codeProject$$>
|
|
|
|
|
Common sense is pre-optimisation. A normalised database is common sense. Post-optimisation you rarely have a normalised database.
regards,
Paul Watson
Ireland & South Africa
Fernando A. Gomez F. wrote: At least he achieved immortality for a few years.
|
|
|
|
|
|
Yes, mean and meaning:
Common sense is a naughty term - one is supposed to 'naturally have it' - and to assume one does.
As such it invites unthinking consent in stead of critical analysis. it is designed to attract voters:
"common sense solutions" based on 'obvious' but often very shaky arguments.
cheers,
koos
|
|
|
|
|
koos4ever wrote: ommon sense is a naughty term - one is supposed to 'naturally have it' - and to assume one does.
thats the reason one become great programmer after that
|
|
|
|
|
That said, you need someone to point out your mistakes. IMO every coder should have a mentor (I wish I had one, but the CP collective served me well in the start ).
|
|
|
|
|
I second you !
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief and You/codeProject$$>
|
|
|
|
|
Indeed Leppie. Couldn't agree more.
|
|
|
|
|
I agree with you completely Leppie. Everyone should have a mentor. I myself never had one, and had to learn from my mistakes the hard way... Lots of buggy code
But, I have found that going back over the years, and studying ones own code a year or two after you initially wrote it, one can learn a lot from the mistakes you made back then. How does the saying go...
"Hindsight is always 20/20"
Never more true than in software development
|
|
|
|
|
leppie wrote: You can only learn from mistakes
... but it is much less painful to learn from mistakes of others
|
|
|
|
|
I 've been taken a formal training for a project, but most part of time that 's not good enoght. I realiced that is necesary a strong hability to investigate.
I am agree 100% sometimes is better self taught than take a formal training but all depends the project's size and the complex.
|
|
|
|
|
...in my opinion, would be ideal. I think, in general, it is always good to have the formal background, which should give you at the very least, an additional viewpoint on how things are done. On the other hand, those that are self-taught tend to have the motivation to keep acquiring more and more knowledge / experience to topics of their interest (which they may eventually work with in formal employment). That's not to say that you can't do well with just one, or just the other, but I think it would be in one's interest to at least have some of both.
|
|
|
|
|
The trainer can only introduce the subject matter by explaining it to the trainee. It is upto the trainee to listen, learn-n-digest besides explorating the topic in depth.
There is a vernacular saying here in India which goes like "One can only help deskinning a banana and best feed one. The actual responsibility of chewing, swallowing it or spitting it lies with the person who is consuming the same. "
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson
|
|
|
|
|
There's a similar, shorter saying here in the west: "You can lead a horse to water but you can't make it drink".
"The pursuit of excellence is less profitable than the pursuit of bigness, but it can be more satisfying."
- David Ogilvy
|
|
|
|
|
if you have to teach yourself how to program, you will come across and solve most of the problems yourself and in future it will be a piece of cake to code
if you have to rely on someone else to teach you then you miss the whole point. no one can teach you how to think like a programmer or how to make good code
|
|
|
|
|
I thought that was "You can lead your boss to data, but you can't make him think."
Bob Emmett
|
|
|
|
|
Bob Emmett wrote: you can't make him think
That is a salient feature of any boss right?
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson
|
|
|
|
|
Bob Emmett wrote: "You can lead your boss to data, but you can't make him think."
Developer Fantasies
|
|
|
|
|
Right. That makes sense. I'm not sure whether or not you're agreeing or disagreeing with my post, though (I would guess that you're agreeing with the formal education part, since you say that it's up to the trainee to listen -- i.e. listen to professors while in the process of being formally educated).
|
|
|
|