我会学习这个C＃吗？!! [英] Will I ever learn this C#?!!

问题描述

我叫Tim，我正在努力学习C＃。我的背景非常小，但是当语言曾经是程序性的时候，我曾经是一个巫师。



我刚开始使用C＃一步一步而且我在第一章8带有值和参考。



我理解价值观和参考资料。我得到了指针（来自C）和ref语句以及所有这些。



我的问题是：经过8章我仍然不能坐下来写任何基本的东西而不是基本的程序。每次我被卡住，书都说：你将在未来的章节中了解这一点......



这种语言何时通常会与人点击？我相当聪明，学习很积极 - 我应该继续学习还是先学习另一种语言？



任何反馈都会令人放心（即使答案是我我不是那么聪明，我永远不会得到它！）



Tim

解决方案

学习的过程必须持续。坏消息是它永远不会结束;（



但是......别担心！到最后阅读这本书。获得实体要好得多。基础知识然后通过幸运的机会开始做程序。



这是一套教程/指南，以加快学习过程的步伐：

< a href =https://msdn.microsoft.com/en-us/library/aa288436%28v=vs.71%29.aspx> C＃教程 [ ^ ]

< a href =https://msdn.microsoft.com/en-us/library/67ef8sbd.aspx> C＃编程指南 [ ^ ]

作为答案1和2的补充。

Quote：

这种语言什么时候通常点击和人一起？

读完书后，重读一定部分，阅读更高级的书，亲自动手至少几个月，理解其他人的代码，使用一些库和架构用于特定目的，实现你之前所做的全部错误......（非详尽的列表）



这不是为了让你失去理智 - 而是向你保证，这需要时间才是正常的。



我认为C＃是一种非常好的语言，它首先要学习：它相当年轻，而且它的设计不是（但是？）带有可疑结构的膨胀;但它几乎包含了现代OOP语言所能提供的任何功能。它编写糟糕的代码并不像其他语言那样有用。它可用于为各种各样的问题开发解决方案。



有一本关于C＃编程的免费PDF书籍，我推荐它不仅可以替代你的其他书籍，特别是因为它的书面介绍明确地解决了你在问题和相关事情中表达的问题：

http://www.introprogramming.info/ [ ^ ]



只要挂在那里，它最终会点击 - 祝你好运！ ：）

我已在评论中回答了问题。正如我所说，我的建议是：成为你学习的大师。如果您觉得某本书不能很好地引导您，请放手，但如果您对此表示怀疑，请立即采取行动。请记住，你不是一位老太太，用另一位老太太从你的邻居那里听到外国政治的版本。相反，你是一名侦探试图从他询问的人那里收集一些真实照片。



有趣的是，我从来没有尝试过任何关于C＃的书籍，因为其他信息已经足够了（不要误会我的意思：书籍非常重要，尤其是基础知识），但是我的同事过去常常带给我一些他们买的书，并问我的想法，我总是至少找到一件 bull ......一些毫无根据的陈述，功能或建议的解释。我想，对印刷文字的尊重是在反应水平上发展的，但这种方面往往被夸大了。



因此，书籍可以是好的与否。但更好的是什么？好吧，原始文档更可靠：

https://msdn.microsoft .com / zh-CN / library / 618ayhy6.aspx [ ^ ]，

https：// msdn .microsoft.com / zh-CN / library / 67ef8sbd.aspx [ ^ ]。



此外，您需要学习平台： https://msdn.microsoft.com/en-us/library/zw4w595w.aspx [ ^ ]。



最终，在C＃和CLR上阅读ECMA标准会很好。您可以轻松找到并下载标准文档。您可以在所有可疑案例中与他们核实，并与编译器和运行时的实际行为进行比较。 实验可以被视为学习的组成部分;只有你不应该依赖你的实验结果;理论上应该理解你的所有结果。



但是 - 太烦人了！ - 即使原始文档缺少一些重要的细节，甚至包含一些非常误导性的页面。通常情况下，这是因为一些微妙的行为很难解释，但事实上页面可能不是由技术的原始创造者写的，而是其他人可能是某些因素。一般来说，MSDN足够可靠。



关于学习技巧，你需要成为主人。如果这本书说某些东西将会出现在未来篇章中，是什么阻止你阅读这个未来篇章，而不是未来，而是现在写一下？是什么阻碍了你从头到尾的第一次近似阅读整本书，以了解它的全部意义？毕竟，这样的书不是一本小说，它不是按顺序只读一次。毕竟，你真的需要建议如何阅读。开发自己的方式。



开发练习？当然。但是你在每章末尾都有练习部分吗？如果没有，这是错误的教科书，或者根本不是教科书。再拿一个。大不了......只是不要指望完美的一个。有人抱怨书中的质量或教师的教学人才不足。我称之为学生的弱点，或懒惰的借口（但抱怨教师缺乏知识可能是有效的）。只有小孩才需要教师的教学才能;对于老年人来说，能力更重要。大学/普遍水平（甚至在这个年龄之前）的成人学生应该成为学习过程的积极方面。

-SA

My name is Tim and I am trying to learn C#. My background is pretty small but when languages used to be procedural I used to be a wiz.

I am just starting the C# step by step book and I am at chapter 8 with values and references.

I understand values and references. I get pointers (from C) and the ref statement and all that.

My question is: After 8 chapters I still cannot sit down and write anything other than a basic program. Everytime I get stuck the book says, "You will learn about this in a future chapter..."

When does this language usually "click" with people? I am fairly smart and very aggressive with learning - should I continue on or learn a different language first?

Any feedback would be reassuring (even if the answer is that I am not that smart and I will never get it!)

Tim

解决方案

The process of learning have to lasts. The bad news is that it never ends ;(

But... Don't worry! Read the book to the end. It's much, much better to get solid basics then start doing programs by lucky chance.

Here is a set of tutorials/guides to increase the pace of learning process:
C# Tutorials[^]
C# Programming Guide[^]

As an addition to answers 1 and 2.

Quote:

When does this language usually "click" with people?

After finishing reading the book, re-reading certain sections, reading a more advanced book, "getting your hands dirty" for at least several months, understanding other peoples code, using some libraries and architectures for specific purposes, realizing what you've done all wrong before... (non-exhaustive list)

This isn't to demotivate you - rather to assure you that it's perfectly normal that it takes time.

I think C# is a very good language to learn first: It's rather young and its design isn't (yet?) bloated with questionable constructs; but it contains almost any feature one could expect from a modern OOP language. It doesn't lend itself as much as some other languages to writing bad code. It can be used to develop solutions for a very wide spectrum of problems.

There's a free PDF-book on programming in C# which I recommend not only as an alternative to your other books but especially because of its very well written introduction which explicitly addresses the concerns you expressed in your question and related things:
http://www.introprogramming.info/[^]

Just hang in there, it'll click eventually - good luck! :)

I already answered in my comment to the question. As I say, my suggestion is: become a master of your learning. If you feel that some book does not lead you well, let it go, but if you doubt it, take the lead right away. Remember, you are not an old lady listening to the version of foreign politics with open mouse from your neighbor, another old lady. Rather, you are a detective trying to assemble a real picture out of pieces from people he interrogates.

Interestingly, I never tried to bye any book on C# in first place, because other information was enough (don't get me wrong: books are very important, especially on the fundamentals), but my colleagues used to bring me some books they bought and asked me what I think, and I always would found at least one piece of bull… some baseless statements, "explanations" of functionality or recommendations. I guess, the respect to the printed word is developed on the level of reflexes, but this respect is often exaggerated.

So, books can be good or not. But what is better? Well, original documentation is somewhat more reliable:
https://msdn.microsoft.com/en-us/library/618ayhy6.aspx[^],
https://msdn.microsoft.com/en-us/library/67ef8sbd.aspx[^].

Also, you need to learn the platform: https://msdn.microsoft.com/en-us/library/zw4w595w.aspx[^].

Eventually, it will be good to read the ECMA standards on C# and CLR. You can easily find and download the standard documents. You can check with them in all questionable case and compare with actual behavior of the compilers and runtime. Experiments can be considered as the integral part of learning; only you should not rely on the results of your experiments along; all your results should be understood theoretically.

But — o bother! — even the original documentation lacks some important detail and even contain some really misleading pages. Typically, this is because some delicate behavior is hard to explain, but the fact that the pages could be written not by original creator of the technology but other people could be some factor. In general, MSDN is reliable enough.

As to the learning techniques, you need to be the master. If the book says that something will be in "future chapter", what prevents you from reading this "future chapter", not in "future", but write now? What prevents you from reading the whole book in first approximation from the beginning to the end, to get the feeling of what is it all about? After all, such book is not a novel, it is not designed to be read just once in sequential order. After all, do you really need advise on how to read. Develop your own way.

Developing exercises? Of course. But do you have the section with exercises at the end of each chapter? If not, this is wrong textbook, or it is not a textbook at all. Take another one. Big deal… Only don't expect the perfect one. Some complain about the quality of the books or insufficient pedagogical talent in the teacher. I call it weakness of the students, or the excuse for laziness (but the complains about lack of knowledge in teachers can be valid). Pedagogical talent in teacher is only required for little kids; for older people, competence is more important. Adult students of college/universally level (and even before this age) should become the active side of the learning process.

—SA

这篇关于我会学习这个C＃吗？!!的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！