blocks|key|1252883|text|许多新的程序员仍然在非常低的抽象层次上工作，学习这个行业。这是每个人都必须经历的事情。可以说，“向上移动堆栈”需要一段时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1252884|一旦程序员意识到他们大部分时间都在解决其他人已经解决过的问题，并且目标是实现“商业价值”，那么他们就可以真正欣赏一个好的库所带来的价值。|1252885|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

A lot of new programmers are still working at a very low level of abstraction, learning the trade. That's something everyone has to go through. It takes a while to "move up the stack" so to speak.

Once programmers realise that they spend most of the time solving the same problems as someone else already did, and the goal is to realise "business value", then they can really appreciate the value a good library brings.

blocks|key|1252327|text|当你还在学习一门新语言的细节时，还必须学习如何使用第三方库，这看起来可能是一项太多的工作。此外，库的文档往往很糟糕--或者至少其文档对于新手(Er)程序员来说是完全不透明的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1252328|因此，面对解决问题X的尝试，说“使用库”听起来很像“解决问题Y然后解决问题x”。|1252329|(而且，他们的教授告诉他们不要这样做。在没有学习C%2B%2B的情况下，我成功地完成了我的本科生学习。天哪，我的面条煮熟了。)|1252330|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

When you're still learning the ins and outs of a new language, also having to learn how to use a 3rd party library can look like too much work. Also, libraries tend to be badly documented - or at least have documentation that seems totally opaque to a new(er) programmer.

So, faced with trying to solve problem X, saying "use a library" can sound a lot like "solve problem Y THEN problem x".

(Also, their professors told them not to. I managed to get all the way though my undergrad in C++ without learning the STL existed. Boy, did THAT cook my noodle.)

blocks|key|1252125|text|几乎总是因为他们的教授告诉他们他们不能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1252126|有时只是因为他们想自己学习，但我想说这种情况很少见。|1252127|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Almost always it's because their professor has told them that they can't.

Sometimes it's just because they want to learn it themselves, but I'd say that's rare.

blocks|key|1466882|text|这是学习曲线。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1466883|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

blocks|key|1467804|text|我记得我避开了几个库，仅仅是因为我想看看我是否可以创建自己的算法。我不想放弃，让别人为我做这项工作，而是想从我的错误中学习。一旦我想出了一个令我满意的解决方案，我就研究了一下这些库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467805|所以对我来说，它只是想看看我是否能做到。|1467806|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I remember shying away from several libraries simply because I wanted to see if I could create my own algorithm. I didn't want to just give up and let someone do the work for me but rather I wanted to learn from my mistakes. Once I had come up with a solution I was happy with, I looked into the libraries.

So for me it was simply wanting to see if I could do it.

blocks|key|1466951|text|我总是有一种自己动手的冲动，但有时我也能看到自己的局限性。最近刚下载了一个创建PDF文档的库，但这几乎是我唯一记得的时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1466952|至少对我来说，(尝试)自己做事情，是我的学习方式。|1466953|我的印象是，许多新手程序员如果要使用别人的库，就不会认为这是他们自己的工作。|1466954|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I always have this urge to do it myself, but sometimes I can see my own limitations.
Just recently downloaded a library to create PDF documents, but thats pretty much the only time I can remember.

At least for me, (trying to) do things myself, is my way of learning.

My impression is that many newbie programmers wouldn't consider it their own work if they were to use someone elses libraries.

blocks|key|1466994|text|我不认为这是一件坏事。使用库是很棒的；它可以节省时间、精力、bug等。然而，您在这个过程中学到的东西很少，对于新程序员来说，学习就是目标。为了回答这个问题，我认为他们倾向于回避库，仅仅是因为他们不习惯使用它们，也许他们不知道它们的存在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1466995|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I don't think that this is necessarily a bad thing. Using libraries is great; it saves time, effort, bugs, etc. However, you learn very little in the process, and for new programmers, learning is the goal. To answer the question, I think that they tend to shy way from libraries simply because they are not used to using them and perhaps they don't know that they exist.

blocks|key|1467307|text|对于许多文档不完善的库，这些库要么是松散实现的，要么是不允许您很好地控制包容性和可见性的语言，因此很难猜测应该如何使用该库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467308|在使用了一段时间后，您已经习惯了这些怪癖，或者阅读了其他教会您正确方法的源代码；但在此之前，使用一个组合/设计不佳的库可能会非常恼人。(或者甚至是一个设计良好但文档不是很好的文档)。|1467309|如果你没有这个库的源代码，那就是另一个问题--你无法控制保持你的程序工作的能力。现在这种情况很少见，但在购买库的情况下仍然会发生这种情况。|1467310|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

For many poorly documented libraries that are either implemented loosely or in languages that don't allow you to control containment and visibility very well, it can be quite difficult to guess just how the library is supposed to be used.

After you've used it for a while, you've gotten used to the quirks or read other source code that taught you the right way; but until then it can be pretty irritating to use a poorly put-together/designed library. (or even a well designed one that isn't terribly well documented).

If you don't have the source code to the library, that's another problem--you have no control over the ability to keep your program working. This is much more rare these days, but still happens in the case of a purchased library.

blocks|key|1467879|text|大部分要点都被覆盖了(对我来说，主要的一点是学习曲线)，但我认为还有一个点起到了作用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467880|因为与自己编写相同的功能相比，学习一个库没有那么令人兴奋。|1467881|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Most of the points covered off (for me the main one is the learning curve) but one other I think plays a part:

Because learning about a library is less exciting than coding the same functionality yourself.

blocks|key|1252911|text|更多的库=更少的计费时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1252912|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

More libraries = less billable hours.

blocks|key|1252585|text|我认为需要投入大量的时间来理解这个库的目的-是的，一个学习曲线，但更多的是，新手程序员可能不知道他们需要什么，直到他们有了更多的经验。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1252586|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think there's a lot of time that needs to be invested in understanding the library's purpose - yes, a learning curve, but it's more that newbie programmers probably don't know what they need until they have a lot more experience.

blocks|key|1252949|text|因为这很有趣。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1252950|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

blocks|key|1467181|text|因为作为一名开发人员，成熟的一部分是学习快速识别可以通过库或现有解决方案解决的问题，以及需要个人关注的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467182|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Because part of maturing as a developer is learning to quickly identify problems which can be solved by a library or existing solution and which need personal attention.

blocks|key|1252722|text|我是程序员，不是心理学家！:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1252723|对我来说，这是很久很久以前的事了，但那是因为我想要学习和体验。我不想使用我不理解的东西，所以如果我认为我不理解这个库，并且不能自己编程，我就尽量不使用它。可能也有一点恐惧；编程给你一种控制的感觉，而使用库就像是放弃了这种控制。|1252724|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I'm a programmer, not a psychologist! :)

It was a long, long time ago for me, but it was because I wanted to learn and experience. I didn't want to use something I did not understand, so if I didn't think I understood the library and could program it myself, I tried not to use it. There might have been a bit of fear too; programming gives you a feeling of control, and using a library is like giving away this control.

blocks|key|1252771|text|当您试图学习如何做事情时，任何时候通过调用AwesomeClass.doAwesomeStuff()来“神奇地”完成某件事时，您最终都会放弃一部分控制权。当你是个“新手”，不知道你会放弃什么，也不知道为什么这会让人不安。这是我第一次学习Rails时遇到的主要问题。在没有深入研究大量Rails源代码(我通常没有时间去做)的情况下，我不知道为什么会有这么多东西“工作”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1252772|至少，这是我对它的看法。|1252773|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

When you're trying to learn how to do things, anytime something is accomplished "magically" by calling AwesomeClass.doAwesomeStuff(), you end up giving away a portion of control. When you are "new" and don't know what you're giving away or why it can be unsettling. This was my primary knock against Rails when I was first learning it. So many things just "worked" and I didn't know why without digging through lots of Rails source (which I generally didn't have time to do). 

At least, that's my take on it.

blocks|key|1467940|text|更有经验的开发人员这样做的原因是相同的-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467941|因为学习如何使用库通常与自己编写需要的部分一样困难。至少这样你就可以理解当它没有达到你期望的效果时它是如何工作的。|1467942|有经验的开发人员只是在理解如何使用库方面有经验，所以更有可能考虑它。一个没有经验的开发者这是另一件需要学习的事情...|1467943|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The same reason that more experienced developers do -

Because it can often be as difficult to learn how to use a library as to write the part of it you need yourself. And at least then you can understand how it works when it doesn't do what you expect.

An experienced developer just has experience at understanding how to use libraries so more likely to consider it. An inexperienced developer it's one more thing to learn...

blocks|key|1253949|text|新手的回答是：“我不确定如何使用这些库，甚至不知道如何访问它们或它是如何工作的。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253950|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Answer from a noob - 
"I am not sure how to use the libraries or even how to access them or how it works"

blocks|key|1468076|text|库通常伴随着学习一些API和它的范例的开销。它可以很快变得复杂，我可以很容易地理解初学者会喜欢在他们的舒适区更多的东西。根据我的经验，我发现大多数库和框架似乎在抽象一些繁琐的例程方面做得很好，但是当我需要扩展这个功能，或者以一种非预期的方式使用它时，它可能会很麻烦。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1468077|我认为这是一件“熟能生巧”的事情。|1468078|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Libraries often come with the overhead of learning some API and it's paradigm. It can get complex fairly quickly, and I could easily understand that beginners would prefer something a bit more in their comfort zone. From my experience, I found most libraries &amp; frameworks seem to do a great job abstracting some tedious routine, but when I need to either extend this functionality, or use it in a way that's not intended, it can be a handful.

I think it's one of those things where "practice makes perfect".

blocks|key|1467052|text|我想教授们希望他们坚持基础知识。当我从大学毕业时，我知道C%2B%2B，Java和其他一些语言，但对公司中使用的库和框架一无所知。这就像你知道吗，你写了一个servlet..no。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467053|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think the professors want them to stick to the basics. When I graduated from under-grad school, I knew C++, Java and some other languages but had no clue about libraries and frameworks being used in companies. It was like do you know java..yes..can you write a servlet..no.

blocks|key|1467502|text|对于速度的恶魔，他们很少使用第三方库，而新程序员通常希望压缩他们的代码的每一次速度。我认为如果他们不能控制他们的代码，他们就不能获得他们想要的性能。至少这就是我第一次开始编程时避免使用库的原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467503|我记得我编写我的第一个DAL，避免所有其他免费的库在网络上，因为我想让我的代码以最快的速度执行。后来，我发现通常不是代码，而是数据库。|1467504|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

For speed demons they rarely use 3rd party libraries and new programmers are usually looking to squeeze every once of speed of of their code. I think if they don't have control over their code they can't get the performance that they are looking for. At least thats why i avoided libraries when I first started to program.

I remember programing my first DAL and avoided all the other free libraries out on the web because I wanted my code to perform at top speed. Later, I discovered that usually its not the code thats the bttleneck its actually the database.

blocks|key|1467642|text|一些开源库存在缺陷，或者效率不如其他库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467643|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Some open source libraries are buggy or not as efficient as others.

blocks|key|1468014|text|在我看来，另一个因素是额外的库增加了复杂性。当程序变得更加复杂时，往往会变得更难理解，更难维护，也更令人讨厌。我认为，尤其是让新程序员远离库的是，添加库代码比添加自己的代码增加了更多的复杂性-只是因为理解库是如何工作的仍然是他们无法掌握的。因此，这似乎是一个既有技巧又有心理的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1468015|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my eyes another factor is that additional libraries add complexity. Programs tend to get harder to understand, harder to maintain and buggier when getting more complex. I think what makes especially new programmers shy away from libraries is that adding library code increases complexity more than adding your own code - simply because understanding how the library works is still out of their grasp. So it seems to be a problem of both skill and psychology.

blocks|key|1253361|text|使用库要求您理解库的相对复杂的设计，这是新程序员可能没有掌握的，因为他们所写的都是简单/过程/单一用途的代码。例如，对于经验丰富的程序员来说，像模板方法、观察者和命令这样的标准设计模式似乎很明显，但对于新手来说，这一切似乎都像是魔术和/或不必要的复杂性。对我来说，转折点是当我足够好地理解设计模式并编写一些基本的可重用代码时。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253362|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Using a library requires you to understand the relatively complex design of the library, something that new programmers might not have mastered because all they've ever written is simple/procedural/single-purpose code. For example, to an experienced programmer standard design patterns like template method, observer and command seem pretty obvious, but to a newbie it all just seems like magic and/or unnecessary complexity. For me the turning point was when I got good enough to grok design patterns and write some basic reusable code.

blocks|key|1253432|text|已经有很长一段时间了，但当我从大学毕业时，我对图书馆一无所知。这是在大型机和微型计算机的时代。我们的学校有一台VAX，管理人员对学生入侵系统的行为很偏执，所以我们甚至不允许我们看图书馆的手册。所以，当我刚从大学毕业的时候，我甚至没有想到图书馆是可用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253433|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It's been a long time now, but when I came out of college, I knew nothing of libraries. This was in the days of mainframes and mini-computers. Our college had a VAX and the managers were paranoid about students hacking the system, so didn't allow us to even see the library manuals. So, when I first came out of college, I didn't even think of libraries being available.

blocks|key|1253541|text|我相信新手不想使用新库的原因有很多。但是，如果你有足够的时间，这不是一个很好的机会，向他们展示使用这个库的好处是什么吗？对于与我一起工作的人，我通常会提供一个例子，说明为什么有些东西比他们的方法更好。它帮助他们作为程序员学习和成熟。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253542|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I am sure there are a lot of reasons why the newbie doesn't want to use the new library. But wouldn't this be a good opportunity, if you have enough time, to show them what the advantage of using the library is? With the people I work with, I will usually provide an example of why something is better than their approach. It helps them learn and mature as a programmer.

blocks|key|1253664|text|也许我还是个初学者，有时我仍然避免使用某些库。一些库引入了太多的抽象，迫使你投入更多的精力来绕过它，或者强迫你以某种方式做事情，我认为这是不好的。当我在做Javascript时，我习惯于不依赖于任何库。然而，我确实会从它们中复制和粘贴一些代码，并构造我自己的“迷你”常用函数。我的一个论点是因为一些库引入了太多的“批量”，使得网页加载速度变慢。然而，在做C/C%2B%2B时，我倾向于不怕使用库。但是，当必须在更精简、更小的库和功能几乎相同的大型复杂库之间进行选择时，我会选择前者。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253665|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Maybe I'm still a beginner, I sometimes still avoid using certain libraries. Some libraries introduces too many abstractions, forcing you to put in more effort to get around it or forcing you to do things in a certain way and I think that's bad. When I'm doing Javascript I'm used to not relying on any libraries. I do, however, copy and paste bits and pieces of code from them and construct my own "mini" commonly-used functions. One of my argument is because some libraries introduces too much "bulk" making web pages load slower. However when doing C/C++ I tend to not afraid of using libraries. But still, when having a choice between a leaner, smaller library to a huge complex library that does almost the same thing, I would choose the former.

blocks|key|1468480|text|我不完全是一个新手程序员，但很多时候我喜欢自己先实现一些东西，所以我至少了解它是如何工作的一种方式。然后，当我不得不将它用于客户端工作时，我会继续使用库的实现来完成任何需要做的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1468481|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I'm not entirely a newbie programmer, but a lot of times I like to implement something myself first, so I understand at least one way of how it works. Then when I have to use it for client work I would go ahead and use a library's implementation of whatever needs to be done.

blocks|key|1468549|text|我可能已经足够接近一个新的程序员，可以发表评论了，至少就我个人而言，我不得不说我不喜欢使用库，因为我现在宁愿自己去体验一下。我没有对时间表做任何事情，所以时间不是问题。当我知道我完全理解了一个领域，并且不能从使用别人的代码中获得任何东西时，我就会使用库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1468550|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I'm probably close enough to a new programmer to be able to comment, and personally at least, I have to say I don't like using libraries because I'd rather get the experience doing it myself for now. I'm not doing anything to a schedule, so the time's not a problem. I'll use libraries when I know I understand an area completely, and can't get anything out of using someone else's code.

blocks|key|1468629|text|好吧，作为最“新手”回应的人，我可以回答我的犹豫是什么…我正在努力学习编程的基础知识，所以我觉得即使我“可以”使用一个库，我仍然觉得我需要有一个更好的理解才能潜入其中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1468630|我不确定这是否有意义，但想象一下，一个库is...well...like一个物理库。它充满了信息，任何我想学习的东西都很容易find...right？|1468631|但是，如果你还不知道如何阅读--或者更准确地说--理解你正在阅读的句子，那么图书馆是没有用的。|1468632|我还在学习如何阅读。:-D|1468633|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Well, as perhaps the most 'newbie' person to respond, I can answer what my hesitation is...I'm trying to learn the very basics of programming, and so I feel like even though I "can" use a library, I feel like I need to still have a better understanding before I can even dive into those. 

I'm not sure if that makes sense, but imagine that a library is...well...like a physical library. It is full of information and anything I can want to learn is easy to find...right?

But if you don't yet know how to read-or more accurately-comprehend the sentences you are reading, then a library is useless.

I'm still learning how to read. :-D

blocks|key|1254008|text|一些新手认为，如果他们使用库，他们会错过一些有趣的东西。他们有这种IWIIOMO+(我想自己实现它)综合症。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1254009|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Some newbies feel that if they use libraries they'd be missing on some kind of fun. They have this IWIIOMO (I-want-to-implement-it-on-my-own) syndrome.

blocks|key|1468780|text|我要说的是他们觉得他们有点吓人。如果他们是一门语言的新手，深入研究更多的库可能看起来是贪得无厌。更不用说让环境与库一起工作所涉及的更多步骤。D：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1468781|从我的教育经验来看，(假设这些新手大多是学生)他们真的接触不到他们。|1468782|我肯定没有(在教室里)。:/|1468783|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I'd say they find them sort of intimidating. And if they're new to a language diving into more libraries may seem like bitting off more than they can chew. Not to mention more steps involved in getting the environment to work with the library. D:

And from my education experience, (assuming most of these newbies are students) they really don't get much exposure to them. 

I sure didn't (while in the classroom). :/

blocks|key|1254122|text|信不信由你，当我上大学的时候，我用C%2B%2B创建了自己的库。是的，这是正确的。这是我自己做的。它包含了许多DOS+C%2B%2B不支持或被一些第三方头文件支持的不同类型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1254123|我为什么要这么做？|1254124|我的老师也问了同样的问题，我想告诉他，我想知道基础知识，我想学习基础知识，我想要建立自己的基础。如果我使用其他人的代码，我将无法理解正在发生的事情。怪胎之爱的循环。如果我喜欢更快地输入键盘，或者如果我不想坐上12个小时的习惯，我就不能成为极客。|1254125|他给我留下了深刻的印象，我也印象深刻。我通过做事情来了解事情。这就是我开始自己写作的开始。|1254126|我现在该怎么做？|1254127|好吧，库是很好的。我们必须使用它。然而，一个人一定不能从学龄儿童开始比较和尝试使用。它们对企业有好处，但对个人可能没有好处！|1254128|如果您不了解HTML的基础知识，并且可以在没有编辑器的情况下操作Html标记，您将如何定义它？|1254129|所以我认为库应该是给学习者使用的，我会计算初级程序，不到1-2年的时间来重新面对他们的库，并看到魔力。|1254130|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

Believe it or not, when I was doing college I'd made my own libraries in C++. Yea that is right. I'd made this myself. It had include many different types that DOS C++ did not support or it was supported by some third party Header files.

Why I did?

The same question was asked by my teacher and I'd to tell him that look I want to know the basic, I want to learn the basic, I want to build my ground. If I use someone else code I will not be able to understand the thing going on.. the cycle the love the geeky. I cannot be geeky when I like to type my key board faster or If I don't want to sit for 12 hrs our mores.

He was quite impressed and I was impressed too. I know things by doing it. That was the beginning of when I started writing of my own.

What I do now? 

Well libraries are good. We must used it. However, one must not compare and try to use from the school age. They are good for business but probably not good for individual!

How would you define that if you don't know the basic of HTML and you can manipulate Html tags without some editor?

So I suppose Library should be used for learners, and I will count junior program, less than 1-2 years to re face their through libraries and see the magic.

I've noticed many questions on here from new programmers that can be solved using libraries. When a library is suggested, often times they respond "I don't want to use X library" Is it the learning curve? or ? Just curious!

Why do newbie programmers seem to shy away from libraries?

数据库

Java

我注意到这里有许多新程序员提出的问题，可以用库来解决。当建议使用一个库时，他们经常会回答“我不想使用X库”，这是学习曲线吗？或者？只是好奇而已！

问为什么新手程序员似乎对库避而远之？
EN

回答 32

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么新手程序员似乎对库避而远之？EN

回答 32

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么新手程序员似乎对库避而远之？
EN