Write code. Having written actual code is much more valuable than reading books. It seems it's a problem that programmers can't write code - see here. So in order not to be one of those that can't program, write code.
You can undertake a project of your taste. Since it's now popular, you can create some social tool, like TweetDeck or HootSuite. Or you can create an arbitrary useful software. For the cornet-shop or car-repair garage of a relative of yours, whatever.
Kind of a subjective question... but I would suggest learning popular design patterns. Also find a project for yourself, find something that interests you, or a problem you want to solve. Spend your free time solving that problem or creating something interesting. The best way to learn is application in real world settings.
作为一名学生，我一年前也面临过类似的困境。我选择学习 C++，这是一个很好的决定。 c++ 让你深入了解指针，并了解垃圾收集（java 通常会自动执行）等等。加上具有 java 背景的 c++ 学习并不难。 或者你可以开始一个项目（也许学习 JSP、Servlet、电子商务网站的 Bean），这是另一个很好的选择。
as a student, id faced a similar dilemma a year back.. i opted to learn c++, and its been a good decision. c++ gives you an insight into pointers and you learn about garbage collection (which java normally does automatically), etc.. plus its not hard to learn c++ with a java background.. or you could embark on a project (perhaps learn JSP, servlets, beans for an e-commerce website), which is another excellent option..
发布评论
评论（8）
写代码。编写实际代码比阅读书籍更有价值。看来这是程序员不会写代码的问题 - 请参阅此处。因此，为了不成为不会编程的人之一，就编写代码。
您可以根据自己的喜好进行项目。由于它现在很流行，您可以创建一些社交工具，例如 TweetDeck 或 HootSuite。或者您可以创建任意有用的软件。对于你亲戚的短号店或汽车修理厂，无论如何。
Write code. Having written actual code is much more valuable than reading books. It seems it's a problem that programmers can't write code - see here. So in order not to be one of those that can't program, write code.
You can undertake a project of your taste. Since it's now popular, you can create some social tool, like TweetDeck or HootSuite. Or you can create an arbitrary useful software. For the cornet-shop or car-repair garage of a relative of yours, whatever.
您可以查看我对类似问题的回答 这里
You can look at my response to a similar kind of question here
有点主观的问题......但我建议学习流行的设计模式。还要给自己找一个项目，找到自己感兴趣的事情，或者想要解决的问题。花你的空闲时间解决这个问题或创造一些有趣的东西。最好的学习方法是在现实世界中应用。
Kind of a subjective question... but I would suggest learning popular design patterns. Also find a project for yourself, find something that interests you, or a problem you want to solve. Spend your free time solving that problem or creating something interesting. The best way to learn is application in real world settings.
我会选择：
它将为你下一步想做的任何事情、其他语言或上面建议的 Pangea（DDD、UML 等）提供坚实的基础。
编辑：是的正如另一位指出的那样：编写代码，而且是大量的代码。
I would go for the:
It will give you a solid base for whatever you want to do next, other languages or as Pangea suggest above (DDD, UML etc.)
Edit: and yeah as another points out: write code, and lots of it.
我建议将您所学到的知识付诸实践。为自己创建一个项目。
或者，您可以了解 Enterprise Java 并使用它。
I would suggest to put what you have learned into practice. Create a project for yourself.
Alternatively, you can learn about Enterprise Java and play around with it.
写代码可能是最好的答案。
然而，您必须处理的时间跨度需要提及七周内的七种语言。
http://pragprog.com/titles/btlang/seven-languages-in -七周
Write code is probably the best answer.
However the timespan you have to work with begs a mention of Seven Languages in Seven Weeks.
http://pragprog.com/titles/btlang/seven-languages-in-seven-weeks
作为一名学生，我一年前也面临过类似的困境。我选择学习 C++，这是一个很好的决定。 c++ 让你深入了解指针，并了解垃圾收集（java 通常会自动执行）等等。加上具有 java 背景的 c++ 学习并不难。
或者你可以开始一个项目（也许学习 JSP、Servlet、电子商务网站的 Bean），这是另一个很好的选择。
as a student, id faced a similar dilemma a year back.. i opted to learn c++, and its been a good decision. c++ gives you an insight into pointers and you learn about garbage collection (which java normally does automatically), etc.. plus its not hard to learn c++ with a java background..
or you could embark on a project (perhaps learn JSP, servlets, beans for an e-commerce website), which is another excellent option..
您应该开始学习 Java EE。
JSP、Servlet、Tomcat 是一个好的开始。也许是春天之后。
记住写代码比读代码要多。尝试编辑准备好的示例。
You should start learning Java EE.
JSP, Servelets, Tomcat is a good start. Spring maybe after.
Remember to write code more than you read. Try editing ready examples.