Geeks With Blogs
FOXJAZZ developing with .net
I have probably seen and used the word Encapsulation 4 times in my 20 years of programming.
I now know what it is again, after an interview for a c# job. Even though I have used the public, private, and protected key words in classes for as long as c# was invented. 

I can sill remember coming across the string.IndexOf function and thinking, why didn't they call it IndexAt, or FindIn.

Now with all the new items like Lambda and Rx, Linq, map and pmap etc, etc. I think the more choices there is to do 1 or 2 things 10 or 15 differing ways, the more programmers think to stay with what works and try and leverage the new stuff only when it really becomes beneficial.

For many, the new stuff is harder to read, because programmers aren't use to seeing declarative notation.
I mean I have probably used yield break, twice in my project where it may have been possible to use it many more times. Or the using statement ( not the declaration of namespace references) but inline using. I never really saw a big advantage to this, other than confusion. It is another form of local encapsulation (oh there 5 times used in my programming career) but who's counting?  THE COMPUTERS ARE COUNTING!

In business logic most programming is about displaying lists, selecting items in a list, and sending those choices to some other system or database to keep track of those selections. What makes this difficult is how these items relate to one, each other, and to externally listed items.

Well I probably need to go back to school and learn c# certification so I can say I am an expert in c#. Apparently using all aspects of c# (even unsafe code) in my programming life, doesn't make me certified, just certifiable.

This is a good time to sign off:
Posted on Thursday, November 8, 2012 6:04 PM | Back to top

Comments on this post: c# vocabulary

# re: c# vocabulary
Requesting Gravatar...
Using yield can have both memory and response time implications since you don't have to load the whole list into memory at a single time and you don't have to wait until the last item is loaded or calculated before you can start processing the first item.

The using keyword also has substantial memory implications when dealing with IDisposable objects.

Some of the new stuff is important.

Some of the arcane terms from OOD may be irrelevant except for during an interview, but then they are often used to filter out those who know vs those who think they know. Knowing the arcane terminology is often the easiest thing to verify.

Some times the arcane terminology creates and defines a more succinct way of expressing design constraints. It would be much easier to specify that a section is going to be implemented with a static singleton implementing the class factory that will expose the strategy pattern for implementing the various supported file formats.

Without a consistent understanding of the various terms, that one sentence may take 200 words to express clearly with no ambiguity.
Left by Nick Harrison on Nov 13, 2012 10:00 AM

Your comment:
 (will show your gravatar)

Copyright © foxjazz | Powered by: | Join free