If you speak french, have a go at this test which is quite insightful :
http://www.testdenormalite.com/Toufik123456
If you speak french, have a go at this test which is quite insightful :
http://www.testdenormalite.com/Toufik123456
Go to Google, type Failure and then click the "I feel lucky" button. No, really Google stocks deserve their price :)
I read this on a website recently, I found it quite clever, it's an except from the famous Paolo Coelho:
c'est pourquoi il est tellement important de laisser certaines choses disparaitre. De s'en libérer. De s'en défaire. Il faut comprendre que personne ne joue avec des cartes truquées, parfois on gagne, et parfois on perd. N'attendez pas que l'on vous rende quelque chose
"That's why it's so important to let some things disappear. To part with it. One must understand that nobody plays with rigged card, sometimes we win, sometimes we win. Don't wait to be given anything back..."
I read the following guidelines that a developer posted on some forum, I find it quite sound so here is the excerpt:
This is my guideline. You may follow them or follow another methodology
for reaching your goals.
One of the best ways to begin is to pick up an introductory book on
.NET, I like the o'reilly series. After that, maybe pick up the .NET
Cookbook or C# Cookbook as it has a ton of examples for common problems
that beginners have. Once you are done with that, you should no longer
be a beginner in .NET.
Read books like Applied Microsoft .NET Framework Programming by Jeffrey
Richter to gain some more knowledge about the framework and then start
reading a lot of MSDN articles and programming small hobby projects.
You can also look at the different start-up projects that are included
or documented for .NET
You should be an intermediate now and you should then start building
your skill level by taking on challenges, working in a .NET position
with some company or just participate in discussions or
start/participate in projects on sourceforge.net
Soon, you will realize that programming is just a tool to construct
software buildings and what you need are good design for those software
buildings. Then start reading on Design Patterns and about software
engineering. You need to look at different software methodologies like
Test Driven Development, Xtreme Programming, RUP, etc. be able to
design elegant solutions and handle any feature creep-ups in your
software building. Learn about new techniques, read about different
languages. Try to understand what features they offer and try to
associate why it is better or worse than what you already have in your
toolkit.
I hope this helps.
Sincerely,
Bobby
| Novembre 2009 | ||||||||||
| L | M | M | J | V | S | D | ||||
| 1 | ||||||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 | ||||
| 9 | 10 | 11 | 12 | 13 | 14 | 15 | ||||
| 16 | 17 | 18 | 19 | 20 | 21 | 22 | ||||
| 23 | 24 | 25 | 26 | 27 | 28 | 29 | ||||
| 30 | ||||||||||
|
||||||||||
Comments