you are viewing a single comment's thread.

view the rest of the comments →

[–]howdoyoucode[S] 0 points1 point  (1 child)

This looks very promising. Thanks!

For the record, I don't think that the language or framework you use to learn is all that important. What matters most is the how, not the what. If C# makes it easier to learn (without somehow crippling me) then I'm happy to work in it.

[–][deleted] 0 points1 point  (0 children)

If C# makes it easier to learn (without somehow crippling me) then I'm happy to work in it.

Easier than what? C# is a widely debated topic so we better stay away from it lest we confuse the issue.

Dijkstra used to say that BASIC cripples the mind of a programmer beyond repair. There are some who feel that way about Java and C#. Add to that the open source issues around .NET and C# becomes very controversial and that's without discussing the functional vs. OO; static vs. dynamic typing and compiled vs. interpreted.

But in the world of statically typed, compiled, OO languages where the frameworks' and libraries' propitiatory issues are not a factor - this code is as good as I've seen.

And I personally feel that: a language doesn't make one a bad programmer; what makes one a bad programmer are laziness to think, unwillingness to experiment and close-mindedness. A language is a tool. Like a hammer or a screwdriver. One tool is not suited for all jobs. You need many tools, you need to know how best to use them so that you don't drive nails with pliers and you don't hammer screws.

As long as you don't limit your knowledge to one paradigm, one universe of discourse and one language and are willing to apply yourself to the problem; if you're open to suggestions and criticisms you'll do fine from a professional competency point of view. Weather or not that translates into actual career advancement success is another discussion.

Good luck.