blocks|key|4938648|text|源代码控制和测试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4938649|首先让他们开始签出代码和编写单元测试，了解它是关于什么，然后从那里开始。|4938650|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|$]]

source control and testing

Get them started with checking out code and writing unit tests first, learn what its about, and then go from there.

blocks|key|1178757|text|是的，这是一个主观的问题。我们已经做了几次暑期和在校期间的实习，也雇佣了CS的应届毕业生。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1178758|如果我们从一个学生开始，他知道：|1178759|1178760|a+OOP-ish+language+(Java、C#、VB.NET、C%2B%2B)|unordered-list-item|1178761|How+to+up+a+compiler/debugger|1178762|How+to+work+OOP|1178763|1178764|1178765|(如何启动源代码控制与源代码控制|1178766|1178767|然后，给定一个具有先决条件的已定义问题域(例如，对于最近的实习生，问题域是“使用自描述条形码将自动生成的注释元数据添加到TIFF文件”)，因此学生需要知道|1178768|1178769|如何生成和解析XMP|1178770|如何将元数据读/写到TIFF(我们有相应的工具)|1178771|如何从条形码读取scanner|1178772|Write单元测试|1178773|1178774|我们在一周内看到了进展，在一个月内看到了演示代码。这一切都在意料之中。我主要让他自己工作，但我介入并纠正了他的一些风格和编码实践。|1178775|其中重要的部分是目标是如何设定和实现的。我把重要的部分弄得一清二楚(即需求)，而把不太重要的部分留给他设计。毕竟，谁想一直按数字作画呢？在设定目标时，我通常会尝试遵循明智的指导方针。一个好的目标是|1178776|1178777|Specific|1178778|Measurable|1178779|Avhievable|1178780|Realistic|1178781|Timely|1178782|1178783|项目有一个良好的反馈循环来进行沟通是非常重要的。在这方面我们有些欠缺。|1178784|entityMap^0|0|0|0|0|0|1|1|1|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1N|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1P|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|1Q|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|1R|8|@]|9|@]|A|$]]|$1|L|3|-4|5|G|7|1S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|G|7|1T|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1U|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1W|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|T|3|U|5|G|7|1Y|8|@]|9|@]|A|$]]|$1|V|3|W|5|G|7|1Z|8|@]|9|@]|A|$]]|$1|X|3|Y|5|G|7|20|8|@]|9|@]|A|$]]|$1|Z|3|10|5|G|7|21|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|23|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|24|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|25|8|@]|9|@]|A|$]]|$1|17|3|18|5|G|7|26|8|@]|9|@]|A|$]]|$1|19|3|1A|5|G|7|27|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|G|7|28|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|G|7|29|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|G|7|2A|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2C|8|@]|9|@]|A|$]]|$1|1K|3|-4|5|6|7|2D|8|@]|9|@]|A|$]]]|1L|$]]

Yeah, that's a subjective question. We have done several summer and during-school internships as well as hired recent grads in CS.

If we start with a student who knows:

<ul>
<li>An OOP-ish language (Java, C#, VB.NET, C++)</li>
<li>How to fire up a compiler/debugger</li>
<li>How to work with our Source Code Control</li>
</ul>

Then given a defined problem domain with prerequisites (for example, for a recent intern, the problem domain was "adding autogenerated annotation metadata to TIFF files using self-describing barcodes"), the student needed to therefore know

<ul>
<li>How to generate and parse XMP</li>
<li>How to read/write metadata into TIFFs (we have tools for that)</li>
<li>How to read from a barcode scanner</li>
<li>Write unit tests</li>
</ul>

We saw progress in a week and saw demo code in a month. This was all within expectation. I mostly let him work on his own, but stepped in and course corrected some of his style and coding practice.

The important part of this is how goals were set and met. I made the important parts crystal clear (ie, requirements) and left the less important parts up to his design. After all, who wants to do paint by number all the time? For setting goals, I try in general to follow the SMART guidelines. A good goal is

<ul>
<li>Specific</li>
<li>Measurable</li>
<li>Avhievable</li>
<li>Realistic</li>
<li>Timely</li>
</ul>

It's very important that the project has a good feedback loop for communication. We were somewhat wanting in this regard.

blocks|key|1153675|text|不要假设任何事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1153676|我在没有源代码控制的情况下完成了大学生活。测试是使用调试器单步执行代码。任何作业都不需要书面工作。|1153677|这三件事对于生产级代码至关重要。|1153678|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|$]]

Don't assume anything.

I made it through college without source control. Testing was stepping through the code with the debugger. No paperwork was needed for any assignment.

These 3 things are vital for production-grade code.

blocks|key|1172562|text|这只是我的想法和经验：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1172563|门托。指派一位资深或首席程序员来指导他们。并不是每个人都适合这样的任务，一个好的导师会起到作用。我们为每个新程序员指派了一位导师--不管他们已经写了多长时间的代码--只是为了让新员工熟悉我们的系统。|1172564|从小事做起。根据你的组织/团队等的配置，让新毕业生开始一些小的维护项目，由导师审查他们的代码并指导他们。|1172565|让他们在你的商店工作的开发环境中接受培训-希望他们对一些语言有所了解，但他们的大部分开发经验都是在学校项目中进行的-而不是完全可靠的生产代码。他们需要一个坚实的基础才能在你使用的环境中工作。|1172566|代码审查和最佳实践--给他们提供指导，并确保他们坚持下去--如果你没有在内部使用最佳实践，那就开始吧。当涉及到一个大型开发团队时，会产生巨大的差异。经常审查代码-这不一定是一大群开发人员在会议上-一对一的审查，非正式的检查，等等工作奇迹。|1172567|建立一个合作的环境-允许开发人员交流、交谈和集思广益-给他们机会讨论可能与手头的代码无关的想法和想法-他们将比立方体农场中的植物更依赖彼此，生产质量将更高。允许他们阅读与他们的手艺相关的博客和网站，比如这一个，编码恐怖，黑客新闻等。支持他们参加本地用户组和开发人员会议。|1172568|多产？这取决于个人-一些应届毕业生永远不会成为高效的程序员，而可能是高效的分析师或经理-一些人将成为一台代码机，但很快就会炮制出1000行维护噩梦代码，其中20行就足够了。我要说的是，一个刚走出校门的程序员应该在6到8个月内就能提高工作效率--这就是说，你的员工中的普通程序员能够为你的产品接受新项目，设计和实现它，并能够处理任何所需的维护任务。获得生产所需的经验需要时间-只有在生产环境中实际开发才能获得这种经验。|1172569|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

Just my thoughts and experiences:

Mentor. Assign a senior or lead programmer to mentor them. Not everyone is geared for this sort of assignment and a good mentor makes a difference. We have a mentor assigned to every new programmer - regardless of how long they have been coding - just to get the new employee familiar with our systems.

Start small. Depending on how your organization / team / etc is configured have the new grad start on some small maintenance projects, with a mentor reviewing their code and guiding them. 

Get them training in the development environment your shop works in - expect that they will know a little about a few languages but that most of their development experience will be with school projects - not exactly solid production code. They will need a solid base to work from in the environment you use.

Code review and best practices - give them guidelines and make sure that they stick to them - if you are not using best practices internally, then start. Makes a huge difference when a large development group is involved. Review code frequently - this does not have to be a large group of developers in a meeting - one on one reviews, informal inspections, etc work wonders.

Develop an environment of cooperation - allow developers to mingle and talk and brainstorm - give them the opportunity to discuss ideas and thoughts that might not be related to the code at hand - they will rely on each other more then plants in the cube farm and production will higher quality. Allow them to read blogs and sites related to their craft - sights such as this one, coding horror, hacker news, etc. Support them going to local user groups and developer conferences.

Productive? That depends on the individual - some new graduates will never be productive coders but might be productive analysts or managers - some will be code machines out of the gate but will quickly churn out 1000 lines of maintenance nightmare code where 20 would suffice. I would say a fresh programmer out of school should be productive in 6 to 8 months - this is to say up to speed with you average programmers on staff, able to take a new project for your product, design and implement it, and able to handle any maintenance task required. It takes time to get the experience required to be productive - experience that can only come from actually developing in a production environment.

blocks|key|1178736|text|首先:如果你是一名应届毕业生或熟练的开发人员--你总能获得新的经验。因此，开发人员应该随时准备学习。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1178737|对于这个问题:如果你的开发团队实践了测试驱动的开发，第一件事应该是向他展示如何编写测试，以及测试如何有用。|1178738|当然，大一新生应该能够使用版本控制，所以如果他真的没有版本控制的技能，那么应该对此做一个简短的介绍。|1178739|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|$]]

First: If you are a fresh graduate or a skilled developer - you always can gain new experience. So developers should be ready to always learn.

For the question: If your dev-team Practices Test-Driven-Development the first thing should be to show him how to write tests and how it can be useful.

Naturally the freshman should be able to use version-control, so if he relly has no skills at version-control a short introduction for this should be made.

blocks|key|1178861|text|以下是我发现对应届毕业生和有经验的新员工很重要的几件事：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1178862|1178863|积极主动地将他们纳入企业文化，不要假设他们会适应自己的|unordered-list-item|1178864|将他们纳入会议，即使他们只是为了在适当的时候让他们在会议中互动|1178865|在驳回他们的想法时要小心我见过这样的情况会阻止人们在以后的道路上提到好的想法|1178866|1178867|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

Here are a few things I've found to be important for recent grads as well as new hires that have experience:

<ul>
<li>be proactive about including them in the corporate culture, don't assume they will fit in on their own</li>
<li>include them in meetings even if they are only there to listen</li>
<li>encourage them to interact in meetings when appropriate</li>
<li>be careful when dismissing their ideas as bad I've seen this discourage people from mentioning good ideas later down the road</li>
</ul>

blocks|key|1153794|text|在我的列表中，使用源代码控制将是第一位的，因为很少有学校需要或依赖这一点。真正坐下来解释如何使用你使用的产品，以及为什么它是必要的。然后，至少在第一个月，确保经常检查，以确保他们正在使用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1153795|接下来是基本的数据库技能。我还没有看到任何人走出校门，真正了解如何查询数据库。|1153796|第三是对你的数据库和代码库的介绍，解释事情是如何完成和组织的，以及为什么。|1153797|第四，测试程序和政策，包括如何进行代码审查，单元测试，QA等。测试也不是大多数学生需要担心的事情。|1153798|第五，如果可能的话，指派一位导师，让新人可以向他寻求建议，询问公司的基本情况。你可能还需要有人来教他们职业行为的基础知识。在着装、出勤等方面是可以接受的。|1153799|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Use of source control would be first on my list as very few schools need or rely on this. Really sit down and explain how to use the product you use and why it is necessary. Then for at least the first month, make sure to frequently check to make sure they are using it.

Next would be basic database skills. I've yet to see anyone come out of school really understanding how to query a database.

Third would be an introduction to your database and code base, explaining how things are done and organized and why. 

Fourth, testing procedures and policies including how to do a code review, unit testing, QA etc. Tesing is not something that most students need to worry about either.

Fifth, assign a mentor if at all possible, someone the new person can go to for advice, to ask questions about company basics. You probably need someone to give them the basics of professional behavior as well. What is acceptable in terms of dress, attendance, etc.

What are the key practical concepts that a fresh graduate should be educated with when he starts with his first programming job and how soon should you expect him/her to be productive and actually deliver the code you expect ?

Inducting Fresh Computer Graduates as Programmers

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

当一个应届毕业生开始他的第一个编程工作时，他/她应该接受哪些关键的实用概念的教育?你应该期望他/她多长时间才能提高工作效率并真正交付你期望的代码？

问计算机应届毕业生入职为程序员
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问计算机应届毕业生入职为程序员EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问计算机应届毕业生入职为程序员
EN