Well, it doesn't hurt, but good
code comes from 3 things: 1.) mastery of the implementation tools (C, C++, Perl) etc.) 2.) mastery of the operating environment (U*ix, windoze). 3.) understanding of the problem to be solved (a program to help someone do such-and-such). These methodology systems mainly address number 3. Most of the failed code I see is because of numbers one and two.
A reference:
In the beginning... was the command line.
by Neal Stephenson
Of course anyone who was ever proficient
with teco knows this has a lot of truth in it.
GUIs are clumsy, that's the tradeoff for
being accessible to the non-proficient.
And you have to leave the GUI world to gain
true proficiency and control of your machine.
So GUIs are also control mechanisms to keep
users where the GUI maker wants them.
This guy has it right.
I'm 55 , I work in LA. I've been a software
engineer for 20 years, I still code actively,
and I make it my business to learn the necessary
skills. I have no trouble finding work.
The problem is finding an employer who
has a clue. Sometimes you have to go through
quite a few to find one that has a working (not disfunctional) software development situation.
I work with lots of H1B people. They are just like other people I work with. Some are good, some are not. I don't care how many they import, personally, it's no threat to me. I do think they
need better protection.
Slashdot Mirror
What are its weaknesses, that's the question.
Well, it doesn't hurt, but good
code comes from 3 things: 1.) mastery of the implementation tools (C, C++, Perl) etc.) 2.) mastery of the operating environment (U*ix, windoze). 3.) understanding of the problem to be solved (a program to help someone do such-and-such). These methodology systems mainly address number 3. Most of the failed code I see is because of numbers one and two.
A reference: In the beginning ... was the command line.
by Neal Stephenson
Of course anyone who was ever proficient
with teco knows this has a lot of truth in it.
GUIs are clumsy, that's the tradeoff for
being accessible to the non-proficient.
And you have to leave the GUI world to gain
true proficiency and control of your machine.
So GUIs are also control mechanisms to keep
users where the GUI maker wants them.
This guy has it right. I'm 55 , I work in LA. I've been a software engineer for 20 years, I still code actively, and I make it my business to learn the necessary skills. I have no trouble finding work. The problem is finding an employer who has a clue. Sometimes you have to go through quite a few to find one that has a working (not disfunctional) software development situation. I work with lots of H1B people. They are just like other people I work with. Some are good, some are not. I don't care how many they import, personally, it's no threat to me. I do think they need better protection.