blocks|key|2274866|text|并发/并行编程和多线程，特别是在内存模型和内存一致性方面。我认为，当我们进入一个多核/多cpu硬件的世界时，每个程序员都应该意识到这个领域的考虑因素。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2274867|为此，我可能会更多地使用互联网研究；但在一所好的大学里，校园内的入门读物可能是一个很好的开始。|2274868|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|$]]

Concurrent/Parallel programming and multi-threading, especially with respect to memory models and memory coherency.. I think every programmer should be aware of the considerations in this arena as we move into a world of multi-core/multi-cpu hardware.

For this I would probably using Internet research most heavily; but an on-campus primer at a good university could be a good way to start off.

blocks|key|907025|text|我来自基于MS的开发人员世界，下面是我对此的看法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907026|更多关于云计算(各种API等)的新概念。因为这个行业已经下注了一段时间了。|ordered-list-item|907027|更多关于LinQ+for+.net框架的信息|907028|分布式数据库|907029|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|M|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|N|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|O|8|@]|9|@]|A|$]]]|J|$]]

I am from MS based developer world, so here is my take on this

<ol>
<li>More about new concepts in Cloud Computing (various API etc.). as the industry is betting on it for sometime.</li>
<li>More about LinQ for .net framework</li>
<li>Distributed databases</li>
</ol>

blocks|key|906050|text|并行计算--学习它的最简单和最好的方法|type|unstyled|depth|inlineStyleRanges|entityRanges|data|906051|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|$]]

Parallel computing- the easiest and best way to learn it

blocks|key|2274899|text|面向对象的设计模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2274900|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|2274951|text|以下是我一直在向那些没有得到足够的CS培训的初级开发人员解释的三个问题。所有这些东西通常都是炒作，而不是实质，或者可以相当容易地被拿起来。但如果你不知道这三个，你会造成很大的伤害：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2274952|算法分析，包括大O符号。|ordered-list-item|offset|length|2274953|衔接性和联轴器的不同级别。|2274954|Amdahl定律，以及它如何与优化相关。|2274955|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Big_O_notation|1|http://en.wikipedia.org/wiki/Cohesion_(computer_science)|2|http://en.wikipedia.org/wiki/Coupling_(computer_science))|3|http://en.wikipedia.org/wiki/Amdahl's_law^0|0|7|4|0|0|0|3|1|4|3|2|0|0|8|3|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@$E|10|F|11|1|12]]|A|$]]|$1|G|3|H|5|D|7|13|8|@]|9|@$E|14|F|15|1|16]|$E|17|F|18|1|19]]|A|$]]|$1|I|3|J|5|D|7|1A|8|@]|9|@$E|1B|F|1C|1|1D]]|A|$]]|$1|K|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]|S|$5|N|O|P|A|$Q|T]]|U|$5|N|O|P|A|$Q|V]]|W|$5|N|O|P|A|$Q|X]]]]

Here are the three that I'm always finding myself explaining to junior developers who didn't get enough CS training. All that other stuff is generally more hype than substance, or can be fairly easily picked up. But if you don't know these three, you can do a great deal of damage:

<ol>
<li>Algorithm analysis, including <a href="http://en.wikipedia.org/wiki/Big_O_notation" rel="nofollow noreferrer">Big O
Notation</a>. </li>
<li>The various levels of
<a href="http://en.wikipedia.org/wiki/Cohesion_(computer_science)" rel="nofollow noreferrer">cohesion</a> and <a href="http://en.wikipedia.org/wiki/Coupling_(computer_science)" rel="nofollow noreferrer">coupling</a>.</li>
<li><a href="http://en.wikipedia.org/wiki/Amdahl&#39;s_law" rel="nofollow noreferrer">Amdahl's Law</a>, and how it pertains to optimizations.</li>
</ol>

blocks|key|750741|text|NP完备。具体来说，如何检测一个问题是否是NP-完全，以及如何建立一个问题的近似解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|750742|我认为这很重要，因为您不希望开发人员试图通过获得最佳解决方案来解决NP-完全问题，除非问题的搜索空间非常小，在这种情况下，蛮力是可以接受的。然而，随着搜索空间的增加，解决问题所需的时间呈指数增长。|750743|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/NP-complete|1|http://en.wikipedia.org/wiki/List_of_NP-complete_problems^0|0|4|0|0|X|7|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

<a href="http://en.wikipedia.org/wiki/NP-complete" rel="nofollow noreferrer">NP Completeness</a>. Specifically, how to detect if a problem is NP-Complete, and how to build an approximate solution to the problem.

I see this as important because you don't want a developer to try and solve an <a href="http://en.wikipedia.org/wiki/List_of_NP-complete_problems" rel="nofollow noreferrer">NP-complete problem</a> by getting the optimum solution, unless the problem's search space is very small, in which case brute force is acceptable. However, as the search space increases, the time required to solve the problem increases exponentially.

blocks|key|2274995|text|开发人员应该了解SQL开发的基本知识，以及他们的决策如何影响数据库性能。编写查询是一回事，写查询、理解解释计划和根据输出做出设计决策是另一回事。我认为一个关于PL/SQL开发和数据库性能的好的课程将是非常有益的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2274996|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|$]]

Developers should know the basics in SQL development and how their decisions impact database performance. It is one thing to write a query it is another thing to write a query, understand the explain plan and make design decisions based off that output. I think a good course on PL/SQL development and database performance would be very beneficial.

blocks|key|2275026|text|安全！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2275027|太多的程序员只是构建了一些东西，认为在完成程序的“主”部分之后，他们可以添加安全性作为后置。了解更多关于如何保护应用程序、如何设计软件以确保安全、如何进行入侵检测等方面的知识，总是会使您受益。|2275028|高级数据库开发|2275029|数据仓库(MDX、OLAP查询、星型模式、事实表等)、高级性能调优、高级模式和查询模式等总是有用的。|2275030|entityMap^0|0|3|0|0|0|7|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|U|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|M|$]]

Security!

Far too many programmers just build something and think they can add security as an afterthought after finishing the "main" part of the program. You could always benefit from knowing more about how to secure your app, how to design software to be secure from the get-go, how to do intrusion detection, etc.

Advanced Database Development

Things like data warehousing (MDX, OLAP queries, star schemas, fact tables, etc), advanced performance tuning, advanced schema and query patterns, and the like are always useful.

blocks|key|2275051|text|我想“高级”对于每个人来说都是不同的，但我建议大多数体面的开发人员(也就是那些不需要被告知NP完整性或设计模式的开发人员)可以从以下方面获益：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2275052|多线程技术超越了“锁定”以及何时应用它们。|unordered-list-item|2275053|深入培训，学习并使自己习惯于工具链中的巧妙特性(IDE/文本编辑器、调试器、分析器、shell)。|2275054|一些密码学理论和实际经验，与不同的共同缺陷的安全方案，人们创造。|2275055|如果他们针对一个数据库进行编程，学习他们的数据库的内部结构以及高级的查询组合和调优技术。|2275056|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

I guess "advanced" is different for everyone, but I'd suggest the following as being things that most decent developers (i.e. ones that don't need to be told about NP-completeness or design patterns) could gain from:

<ul>
<li>Multithreading techniques that go
beyond "lock" and when to apply them.</li>
<li>In-depth training to learn and
habitualize themselves with clever
features in their toolchain (IDE/text
editor, debugger, profiler, shell.)</li>
<li>Some cryptography theory and hands-on experience with different common flaws in security schemes that people create.</li>
<li>If they program against a database, learn the internals of their database and advanced
query composition and tuning techniques.</li>
</ul>

blocks|key|2275074|text|调试|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2275075|戴维·J·阿根的调试是一本关于这个主题的好书。当您处理多线程程序、崩溃、无法工作的算法时，调试可能非常复杂。等等，如果大家都擅长调试，那会更好。|2275076|entityMap|0|LINK|mutability|MUTABLE|url|http://www.debuggingrules.com/^0|0|2|0|0|A|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

Debugging 

<a href="http://www.debuggingrules.com/" rel="nofollow noreferrer">Debugging by David J. Agans</a> is a good book on the topic. Debugging can be very complex when you deal with multi threaded programs, crashes, algorithms that doesn't work. etc. Everybody would be better off being good at debugging.

blocks|key|906143|text|我是个喜欢读书的人，所以我不会真的为指导而烦恼。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|906144|不一定是按照这个顺序，而取决于你已经知道的|906145|OO编程|unordered-list-item|906146|功能程序设计|906147|数据结构和算法|906148|并行处理|906149|基于集合的逻辑(本质上是sql背后的理论以及如何应用它)|906150|构建解析器(我只把它放在这里，因为它实际上出现在我工作的地方)|906151|软件开发方法|906152|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|X|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|Y|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Z|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|10|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|11|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|12|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|T|$]]

I'm a book person, so I wouldn't really bother with instruction.

Not necessarily in this order, and depending on what you know already

<ul>
<li>OO Programming</li>
<li>Functional Programming</li>
<li>Data structures and algorithms</li>
<li>Parallel processing</li>
<li>Set based logic (essentially the theory behind sql and how to apply it)</li>
<li>Building parsers (I only put this, because it actually came up where I work)</li>
<li>Software development methodolgoies</li>
</ul>

blocks|key|2275154|text|我上的最好的课程之一是一门技术写作课程。在我的职业生涯中，这对我很有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2275155|此外:主题可能并不重要--组织对它感兴趣并为此付费，而开发人员希望去做，这是一个比任何一个特定主题都更好的成功/改进的指标。|2275156|我也不认为这个话题有多重要。Dev组织在一个项目中处理太多的事情，以至于培训，然后在工作中执行/试用和错误总是会给你带来更好的视角--即使尝试/使用新东西的尝试失败了。这一经验可能对后续项目有更多帮助。|2275157|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|$]]

One of the best courses I took was a technical writing course. It has served me well in my career. 

Additionally: it probably does not matter WHAT the topic is - the fact that the organization is interested in it and is paying for it and the developers want to go and do go, is a better indicator of success/improvement than any one particular topic. 

I also don't think it matters that much what the topic is. Dev organizations deal with so many things during a project that training and then on the job implementation/trial and error will always get you some better perspective - even if the attempts to try out/use the new stuff fail. That experience will probably help more on the subsequent projects.

blocks|key|907163|text|我更愿意接受培训吗？我希望有大量的公司时间专门用于自我培训。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907164|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|$]]

How would I prefer to acquire the training? I'd love to have a substantial amount of company time dedicated to self-training.

blocks|key|750959|text|我会投票给现实世界的战斗故事。让其他组织的开发人员介绍他们的成功和失败。不要将演示文稿限制在您正在使用的技术上。对于一个非常复杂的项目，这必然会涉及到你甚至没有考虑过的“高级”主题。现实世界的成功(和失败)有很多要教。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|750960|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'd vote for real-world battle stories. Have developers from other organizations present their successes and failures. Don't limit the presentations to technologies you're using. With a significantly complex project, this is bound to cut into 'advanced' topics you haven't even considered. Real-world successes (and failures) have a lot to teach.

blocks|key|750982|text|国际化问题，特别是因为它听起来似乎不是一个高级的话题。但它是。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|750983|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|$]]

Internationalization issues, especially since it sounds like it would not be an advanced topic. But it is.

blocks|key|751001|text|我要报道新技术和新趋势。我正在研究/提高我的技能的一些新技术包括：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|751002|微软.NET框架v3.0/v3.5/v4.0|unordered-list-item|751003|云计算框架(亚马逊EC2、Windows服务、GoGrid等)|751004|设计模式|751005|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|M|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|N|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|O|8|@]|9|@]|A|$]]]|J|$]]

I'd cover new technologies and trends. Some of the new technologies I'm researching/enhancing my skills with include:

<ul>
<li>Microsoft .NET Framework v3.0/v3.5/v4.0</li>
<li>Cloud Computing Frameworks (Amazon EC2, Windows Azure Services, GoGrid, etc.)</li>
<li>Design Patterns</li>
</ul>

blocks|key|906222|text|去堆栈溢出DevDays|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|906223|和ACCU会议|906224|朗读|906225|敏捷软件开发、原则、模式和实践(Robert+C.+Martin)|unordered-list-item|906226|清洁守则(Robert+C.+Martin)|906227|务实的程序员(安德鲁·亨特和戴维·托马斯)|906228|entityMap|0|LINK|mutability|MUTABLE|url|http://www.joelonsoftware.com/items/2009/05/12.html|1|http://accu.org/index.php/conferences^0|1|B|0|0|1|6|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|F|3|G|5|6|7|16|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|17|8|@]|9|@]|C|$]]|$1|K|3|L|5|J|7|18|8|@]|9|@]|C|$]]|$1|M|3|N|5|J|7|19|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]|W|$5|R|S|T|C|$U|X]]]]

Go to the <a href="http://www.joelonsoftware.com/items/2009/05/12.html" rel="nofollow noreferrer">Stack Overflow DevDays</a>

and the <a href="http://accu.org/index.php/conferences" rel="nofollow noreferrer">ACCU conferences</a> 

<hr>

Read 

<ul>
<li>Agile Software Development, Principles, Patterns, and Practices (Robert C. Martin)</li>
<li>Clean Code (Robert C. Martin)</li>
<li>The Pragmatic Programmer (Andrew Hunt&amp;David Thomas)</li>
</ul>

blocks|key|2275318|text|可访问性|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2275319|它被许多组织忽略了，但简单的事实是，有大量的人视力低下或没有视力、色盲或其他差异，这会使浏览网页成为一种非常令人沮丧的体验。如果每个人都有一点培训，我们可能会得到一些基于网络的UI，更多的包容性。|2275320|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|$]]

Accessibility

It's ignored by so many organizations but the simple fact of the matter is that there are a huge number of people with low or no vision, color blindness, or other differences that can make navigating the web a very frustrating experience. If everybody had at least a little bit of training in it, we might get some web based UIs that are a little more inclusive.

blocks|key|751106|text|不幸的是，对于大多数开发人员来说，沟通技巧似乎属于“高级主题”部分(当然，目前的公司除外)。获得这一技能的最佳方法是:练习。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|751107|拿起耳机，和别人交谈，而不是在旁边的桌子上给对方发电子邮件或电子邮件。|unordered-list-item|751108|拿起电话，与客户交谈，而不是把电子邮件扔过篱笆。|751109|在会议上提问，而不是坐在你的笔记本电脑屏幕后面twittering。|751110|积极参加非技术会议。|751111|在公共场合展示一些东西。|751112|大多数项目不会因为技术原因而失败。他们失败是因为他们不能创建一个团队。沟通对于团队动力是至关重要的。|751113|它也不会伤害你的事业。|751114|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|U|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|W|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|X|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Y|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Z|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|R|$]]

Unfortunately communication skills seem to fall under the "advanced topics" section for most developers (present company excluded, of course). 
Best way to acquire this skill: practice.

<ul>
<li>Take of the headphones, and talk to
someone instead of IM'ing or emailing
the guy at the next desk.</li>
<li>Pick up the phone and talk to a
client instead of lobbing an email
over the fence.</li>
<li>Ask questions at a conference instead of sitting behind your laptop
screen twittering.</li>
<li>Actively participate in a non-technical meeting at work.</li>
<li>Present something in public.</li>
</ul>

Most projects do not fail because of technical reasons. They fail because they could not create a team. Communication is vital to team dynamics. 

It will not harm your career either.

blocks|key|2275393|text|我完全同意配饰。我被要求调查它的网站在工作中，有一个真正缺乏良好的知识，在这个问题上，不仅缺乏CSS标准，以帮助屏幕阅读器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2275394|然而，我的答案是GUI设计--这是一件很难做到的事情。有太多可怕的应用，只要花点时间去遵循人机交互(+HCI+)的建议/设计就可以避免。以Google/Apple为灵感，在制作GUI时--而不是通常被推开的数百个按钮/标签组合。|2275395|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 totally agree on Accessabiitly. I was asked to look into it for the website at work and there is a real lack of good knowledge on the subject, not only a lack of CSS standards to aid in the likes of screen readers.

However my answer goes to GUI design - its quite a difficult thing to get right. There's too many awful applications out there that could be prevented just by taking the time to follow HCI (Human Computer Interaction) advice/designs. Take Google/Apple for inspiration when making a GUI - not your typical hundreds of buttons/labels combo that too often gets pushed out.

blocks|key|2275438|text|好吧，如果你在这里，我希望到现在为止你已经掌握了基本知识：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2275439|OOP最佳实践|unordered-list-item|2275440|设计模式|2275441|应用程序安全性|2275442|数据库安全/查询/模式|2275443|最值得注意的是，开发人员应该努力学习多种编程语言和学科，以便在多个方向上扩展他们的技能集。他们不需要成为这些其他技能的专家，但至少对与他们的核心学科的整合有一个非常敏锐的理解。从长远来看，这将使他们成为更好的开发人员，并使他们能够使用所有可用的工具来创建能够超越单一语言限制的应用程序。|2275444|除了编程特定的主题之外，您还应该学习如何在敏捷、XP或其他基于团队的方法下工作，以便在团队环境中工作更成功。|2275445|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|V|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|W|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|P|$]]

Well if you're here I would hope by now you have the basics down:

<ul>
<li>OOP Best practices</li>
<li>Design patterns</li>
<li>Application Security</li>
<li>Database Security/Queries/Schemas</li>
</ul>

Most notably developers should strive to learn multiple programming languages and disciplines, in order for their skill set to be expanded in more than one direction. They don't need to become experts in these other skills but at least have a very acute understanding of integration with their central discipline. This will make them much better developers in the long run, and also let them gain the ability to use all tools at their disposal to create applications that can transcend the limitations of a singular language.

Outside of programming specific topics, you should also learn how to work under Agile, XP, or other team based methodologies in order to be more successful while working in a team environment.

blocks|key|751230|text|我认为，高级程序员应该知道如何让你的雇主给你时间和金钱，以获得培训，在尽可能多的高级编程主题，你可以吃在一年。我还没进步呢。:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|751231|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 an advanced programmer should know how to get your employer to give you the time &amp; money to acquire training on as many advanced programming topics that you can eat in a year. I'm not advanced yet. :)

blocks|key|907325|text|重构技术(这也意味着学习编写良好的单元/功能测试集)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|907326|知道如何重构是保持代码整洁的最好方法--当你第一次正确的时候(尤其是在新的设计中)，这是很少见的。|907327|然而，许多重构都需要一组合适的测试来检查重构没有添加意外行为。|907328|entityMap^0|E|D|0|0|1D|0|0|V|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

Refactoring techniques (which implies also learning to write a good set of unit/functional tests).

Knowing how to refactor is the best way to keep code clean -- it is rare when you get it right the first time (especially in new designs).

A number of refactorings, however, require a decent set of tests to check that the refactoring did not add unexpected behavior.

blocks|key|2275571|text|我建议在学院/大学开设人工智能课程。大多数东西都很有趣，很容易掌握(至少是基本的)，解决问题的方法通常都是有创意的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2275572|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'd suggest an Artificial Intelligence class at a college/university. Most of the stuff is fun, easy to grasp (the basics at least), and the solutions to problems are usually creative.

blocks|key|751364|text|自动化测试:单元测试、功能集成测试、非功能测试。|type|unordered-list-item|depth|inlineStyleRanges|entityRanges|data|751365|编译器细节(在某些平台上比其他平台更相关)：编译器是如何在X语言中实现某些公共结构的？在字节码解释平台上，JIT编译是如何工作的？什么是JIT编译的(例如，可以编译虚拟调用吗？)|751366|基本网络安全|751367|常见的设计习惯用语来自其他问题领域，而不是您目前正在处理的问题领域。|751368|unstyled|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|I|7|O|8|@]|9|@]|A|$]]]|J|$]]

<ul>
<li>Automated testing: Unit testing, functional integration testing, non-functional testing</li>
<li>Compiler details (more relevant on some platforms than others): How does the compiler implement certain common constructs in language X? On a byte-code interpreted platform, how does JIT compilation work? What can be JIT-compiled (for example, can virtual calls be JIT compiled?)?</li>
<li>Basic web security</li>
<li>Common design idioms from other problem domains than the one you're working in at the moment.</li>
</ul>

blocks|key|907398|text|搭便车人银河指南。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907399|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|2275690|text|我建议学习有关重构、测试驱动开发和各种单元测试框架(NUnit、Visual、CppUnit等)。我还将学习如何将自动化单元测试集成到您的连续集成构建中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2275691|最终，如果你能证明你的代码做了它声称能做的事情，你就不需要在那里回答为什么或者怎样的问题。如果一个维护人员出现并试图“修复”您的代码，他们会立即知道他们是否破坏了它。围绕需求(用例)编写的测试向维护人员解释您的用户希望它做什么，并提供一个如何调用它的工作示例。将单元测试视为功能文档。|2275692|测试驱动开发(TDD)是一种更新颖的设计方法，从需求开始，在编写代码之前先编写测试。然后编写通过测试所需的足够代码。在编写额外的代码(您可能永远不需要)之前，您必须停止，因为如果您发现确实需要它，您将在稍后重构它。|2275693|让TDD更酷的是，一个糟糕的接口(比如一个有大量依赖项的接口)也很难编写测试。它是如此困难，以至于一个编码器宁愿重构界面，以使它更容易测试。重构简化了代码，消除了不适当的依赖关系，或者将相关的测试组合在一起，从而简化了测试，从而提高了凝聚力。开发人员在编写接口糟糕的模块时立即向开发人员展示，开发人员坚持体系结构，并遵循紧密衔接和松散耦合的原则。良好的界面是自然的结果。作为一种奖励，一旦你通过了所有的测试，你就知道你已经完成了。|2275694|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|$]]

I'd recommend learning about Refactoring, Test Driven Development, and various unit testing frameworks (NUnit, Visual Test, CppUnit, etc.) I'd also learn how to incorporate automated unit testing into your continuous integration builds.

Ultimately if you can prove your code does what it claims it can do, you don't have to be there to answer questions as to why or how. If a maintainer comes along and tries to "fix" your code, they'll know instantly if they broke it. Tests written around the requirements (use cases) explain to the maintainer what your users wanted it to do, and provide a little working example of how to call it. Think of unit tests as functional documentation.

Test Driven Development (TDD) is a more novel design approach that begins with the requirements, where you start by writing a test before you write the code. You then write exactly enough code required to pass the test. You have to stop before you write extra code (that you may never need), because you will refactor it later if you find that you really needed it.

What makes TDD cool is that a bad interface (such as one with lots of dependencies) is also very hard to write tests for. It's so hard that a coder would rather refactor the interface to make it easier to test. And that refactoring simplifies the code, removing inappropriate dependencies, or grouping related tests together to make it easier to test, thus improving cohesion. By making it immediately apparent to the developer when he's writing a badly interfaced module, the developer sticks to the architecture and gravitates to the principles of tight cohesion and loose coupling. Good interfaces are the natural result. And as a bonus, once you pass all your tests, you know you're done.

blocks|key|751400|text|从表面上看，这似乎是一个很容易回答的问题，只需输入您最喜欢的宠物轻蔑地回答其他开发人员不能正确做的事情。但是当我阅读了答案并给出了一些想法时，我意识到我提出的每一个“高级主题”都包含在我的本科计算机科学课程中--20年前。我怀疑OO、安全性、函数式编程等概念在那个时候是否发生了变化。当然工具有，但我认为工具与主题不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|751401|那么，什么是计算机科学中的“高级主题”呢？谁是21世纪的图灵，克努斯，尤尔登？|751402|对于这个问题，我没有一个明确的答案，尽管我希望看到更多关于并行编程的理论方面的工作，这些理论将使工具能够为开发人员抽象出那些杂乱无章的东西。|751403|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|$]]

On the surface this seems like an easy question to answer, just enter your favorite pet peeve about what other developers can't do correctly. But when I read through the answers and gave it some thought, I realized that every "advanced topic" brought up was covered in my undergraduate computer science curriculum--20 years ago. And I doubt that OO, security, functional programming, etc. concepts have changed in that time. Sure the tools have, but I argue that tools are different than topics.

So what is an "advanced topic" in computer science? Who is the Turing, Knuth, Yourdon of the 21st century?

I don't have a clear answer to this question, though I'd like to see more work on theories for parallel programming that will enable tools to abstract that messy stuff for developers.

blocks|key|2275750|text|有趣的是，没有人没有提到：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2275751|调试。|unordered-list-item|2275752|您所使用的工具和系统|2275753|以及你正在开发的平台。|2275754|如果你非常了解你的工具，如果你知道如何轻松地调试别人的代码，你就能完成更多的工作，让你的生活变得更容易，那么你的日常开发就更有趣了。|2275755|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

Quite funny that noone hasnt mentioned: 

<ul>
<li>debugging. </li>
<li>tools &amp; ide you work with</li>
<li>and platform you are developing to.</li>
</ul>

Everyday development is much more fun if you know your tools really well and you accomplish more and make your life easier if you know how to debug someone elses code at ease.

blocks|key|906431|text|源控制|type|unstyled|depth|inlineStyleRanges|entityRanges|data|906432|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|906434|text|对于Microsoft+.NET的人|type|unstyled|depth|inlineStyleRanges|entityRanges|data|906435|我认为银光在未来的几年里将是巨大的。|906436|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 the Microsoft .NET folks

I think Silverlight is going to be HUGE for the next few and perhaps many years.

blocks|key|907466|text|有趣的是，我目前的软件工程课程中提到的每一个主题(除了极少数)都涉及到，并行性是一个高级单元。也许知识的广度比我们想象的要有限，而且每个话题的知识深度更有价值。我建议学习一些不规范的东西。我知道我在一家公司实习，提供摄影课程，这与生意无关，但它让人们养成了学习的习惯。再学一次。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907467|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|$]]

Its interesting that each topic suggested (with exception of a very few) have all been covered in my current Software Engineering course, Parallelism was an advanced unit though. Perhaps the width of knowledge out there is more limited than we think, and rather the depth of knowledge available for each topic is of greater value.
I'd suggest learning something out of the norm. I know at a company I was doing an internship at, that made available a photography course, it had nothing to do with the business, but it got people into the habit of learning. Learn how to learn again.

Let's say your company has given you the time &amp; money to acquire training on as many advanced programming topics that you can eat in a year, carte blanche. What would those topics be and how would you prefer to acquire them?

Assumptions:

<ul>
<li>You're still having deliverables to bring into existence, but you're allowed one week per month for the year for this training.</li>
<li>The training can come from anywhere. IE: Classroom, on-site instructor, books, subscriptions, podcasts, etc.</li>
<li>Subject matter can cover any platform, technology, language, DBMS, toolset, etc.</li>
</ul>

What are some advanced software development topics every developer should know?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

假设您的公司为您提供了时间和金钱，您可以在一年内学习尽可能多的高级编程主题的培训。这些主题是什么?你希望如何获得它们？假设：你仍然有可实现的目标，但是在这个培训中，你可以在一年中每月一周。训练可以来自任何地方。课堂、现场指导员、书籍、订阅、播客等.主题可以涵盖任何平台、技术、语言、DBMS、工具集等。

问每个开发人员都应该知道哪些高级软件开发主题？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问每个开发人员都应该知道哪些高级软件开发主题？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问每个开发人员都应该知道哪些高级软件开发主题？
EN