How can I test my knowledge of .NET?
Many topics in programming and computer science are complex, and as a result, it is difficult to understand if you get an idea right after just reading about it. Some programmers' training material includes introspection pretty well; a good example of this is the Little Semaphore Book .
I would like a few ways to test my knowledge of the .NET runtime: BCL and C #, and WPF. I especially would like to understand how to store and search the data structures are working in .NET is somehow similar to the STL ( deque
, vector
, map
etc.). Ideally, this would be like stuff in a semaphore book, where relevant stuff is presented along with self-testing.
Suggestions?
source to share
What makes up a test might be the most ambiguous part of this question. As I understand it, the test itself can be any of the following:
1) The definition of regurgitation is when someone says different definitions but does not understand any relationship that may exist.
2) Rewrite the definition using specific nomenclature to try to demonstrate understanding of the concepts.
3) Teach someone else the concept from scratch. In this case, problems may arise with the translation of the material, as well as with what methods will be preferable.
4) Give an example using a specific concept. This can be tricky as some of the places that define things also provide trivial examples.
5) Question "Tell me about a place ..." to ask how something will be used.
The third is what I've used a lot to describe where someone really understands the concept.
source to share
You can take some practice tests for MCSD. This will give you a good idea of where to start. Most of the practice tests will link to various books where the answer will be found.
http://www.measureup.com/catalog/exam.aspx?vid=5&cid=MCSD&tid=25
- a list of some practice tests.
I don't know where exactly you might have tested some of the new technologies.
source to share
This is a problem with any text. If you care about this, you have several options: find texts with sets of problems, or try using them yourself. I am working on Project Euler stuff in Common Lisp, Python and Ruby; I find myself writing notes for myself because I think the problem helps with good cue ball too.
source to share
There is a world of difference between how to get an idea and how to understand it. "sorting" means you get the terminology, you recognize the problem, but you probably couldn't sit down and code a solution or explain it to someone else. My personal experience is that if I'm honest with myself, I know which side of the fence my understanding sinks to.
- If you are not sure whether you fully understand something, you are not
- If you can't explain it to someone else, you probably won't. If you can explain it to someone, what are you doing.
Much of my progression in self-study (which will always be a big part of this profession) creeps into my head that learning subjects at a "peculiar" level doesn't really benefit me at all, and taught myself not to be satisfied with it. When you really learn something, you own it. Until.
At the risk of being uber-geeky, a great coined word for this.
source to share