Can you please comment?
Sure, spend the next week read all the links and links and links of links I linked :)
He is talking about programming paradigms, a particular way to design and write programs , a particular way to speak/think about and solve problems
Its like eating a cow (or eating a horse), the goal is food in your employers belly, but how you go about it depends on how you think (what is humane? which cuts are kosher? ... ), what kind of hardware you have ( stone , steel, electric,... ), taste preference (steak? hamburger? sausage? bbq? ... ) ... some programming languages come with a really sharp and shiny meat slicer, while others only allow chainsaws
Its like fighting, or mixed martial arts, there is long range, short range, standup, takedown, ground, clinch, grappling, ... your might be a ground submission expert, but your opponent won't let you go to ground, keeps you standing ... you can win a lot of fights with just a ground game , but its best to have a plan/skills/vocabulary/technique for fighting at all ranges/stages -- even if your current opponent limits your choices
In all three cases, practice by solving real problems yields best results, allows you to adapt to any challenge .... but it's not like I consider myself there :)
Programming is far more than the mechanics of language acquisition. It is about reading problem statements, extracting the important concepts. It is about figuring out what is really wanted. It is about exploring examples to strengthen your intuitive understanding of the problem. It is about organizing knowledge and it is about knowing what you don’t know yet. It is about filling those last few gaps. It is about making sure that you know how and why your code works, and that you and your readers will do so in the future. In short, it is really about solving problems systematically.
In reply to Re^3: To be Good at PERL
by Anonymous Monk
in thread To be Good at PERL
by ostra
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |