Jacks_LINQ

To catch you up to speed since the last post... I got a job working as a C#.Net dev for Sterling Tech Solutions. At first I was wondering if I was a good fit for the job. We where talking about building an enterprise level application and structure. Which is something I have never done before. As time went by, I was surprised to see I was already partly in the mindset to deal with such a large scale application. I could not of headed it up by my self, but I am at least satisfied that my years of self-teaching have been pushing me in the right direction.

The main point of interest though, is that my previous experience has proven useful in day to day experience. Case and point: LINQ. Since picking up on Ruby/Rails and Python/App Engine, I have gotten to know Active Record very well. I was quite surprised to find that they put it into .Net. It really did not seem like it was something they could just easily pop in. To me, Active Record seems so dynamic and flexible while C# is compiled and I think of it as a static language. The really hard part is when I realized that the class that holds the results of the Active Record query are generic. Therefore, they have a lot of overhead. When using C# I am always worried about things being streamlined and efficient. As I talked it out with the lead dev, it made since. I am writing for flexibility on the enterprise level now. Not for speed on the single client level. This is new to me. I gotta get used to it.