I definitely want to hear Roger Jennings' story! Roger, your turn!!

I've been called out by Shawn Wildermuth to answer a bunch of questions about how I got started in programming, etc. I've done that over here and called out 5 more folks as well.

[A New DevLife Post]

Sorry, this has nothing to do with Entity Framework.

This is about garden slugs! I've been having some problems with the slugs decimating the Romaine in my garden. Since my husband wouldn't let me use any of his fancy beer to lure them away, I used the next trick I learned about - "over ripe" yogurt.

I put it in a small yogurt container, dug a whole in the corner of my garden and placed the container in there so that the top was level with the ground.

Yesterday I went out there and it looked like every slug in Vermont had heard about the awesome yogurt being served up on Moody road. They were coming out of the tall grass surrounding the garden and I think there must have been 50 there.

Whoa - big mistake. Now all of those slugs know about my romaine! I probably should have put that yogurt a bit farther from the garden.  It's similar to when people very cleverly buy those "bag a bugs" to lure Japanese Beetles away from their flowers. But the scent in those sacks is so powerful that it draws Japanese Beetles from far away. We've trained our neighbors not to use them. So far so good this year - the roses are blooming and actually sticking around!

I went out this morning to take a picture of the slugs because it was so bizarre and was surprised to find they were all gone. It was like a big frat party had just dissipated and to add to the image, there were two slugs that were slowly slugging there way away from the yogurt container back into the weeds that surround the garden.

The real goal was that they were supposed to fall in there and drown (I know - murderer! All for a head of lettuce!) but instead they drained the yogurt and headed off. At least the mass of slugs wasn't attacking the lettuce. But I'm sure they'll be back!  EEEEEW.

After appying SP1 on one of my development machines, I got a COM Interop error when opening up SQL Server Management Studio. It took a few minutes to find the correct search terms on the web, but I found the simple fix to the problem pretty quickly. Read more here...

[A new DevLife post]

Apparently not everyone in the world has been conscious that today is Bill Gates last day working full time at Microsoft. My sister thought that the "moving on" story she heard on NPR was an obit... read more

[A New DevLife Post]

I've seen this quote in many of the recent discussions of the evils of Entity Framework.

In the comments to Sebastien Lambla's, blog post, Danny Simmons explains:

The goal is not one model to rule them all. The goal is unifying the way you specify models in many tools to be the same. That way you can leverage your learning across many things. That way if you WANT to reuse some of your model in multiple places you can, but the real thing is that it's absolutely ridiculous that I have to do essentially the same task in completely different ways when I want to build a model for my objects that talk to the database and another model (maybe with different contents but the same idea of a model) for my reporting and another one for whatever else. We're trying to eliminate the differences in experience and learning required for the parts of these tasks that are very much the same.

I thought it was worth surfacing.

The Entity Framework - don't get fooled in what is wrong about it

I guess it's better than calling myself a "self-congratulatory, self-proclaimed, egotistical doofus".

(In case the reference doesn't make sense, Sebastien has since modified his post so that the word "fooled" no longer links to my blog...)

Dinesh uses humor (laced with a little well deserved sarcasm) in response to "the sky is falling because Technology X doesn't fit my way of programming" ....

Design of LINQ to SQL - What was I thinking or was I?

A few months ago I came across this great interview with Jimmy Nilsson where he is talking abot LINQ and Entity Framework. I love what he says about LINQ - that it's a beatiful thing and it's small & compact. And I'd been very curious to know what Jimmy thought of EF since I missed my chance to meet him and ask directly when I went to Stockholm. The most memorable thing he said is that it is "very big". Indeed it is. And of the things he didn't like about SQL, the most critical was the lack of value objects (aka, thanks to Roger, what we know as complex types in EF). With EF it was that it comes so deeply from the data world and the lack of PI. Here he calls IPOCO the "anti-PI". While I don't have time to set EF aside and sit down and really learn about Domain Driven development as  well as the slew of ORMs out there, I do try to grab what I can when I can and I this particular video, with Jimmy's soft-spoken contemplative way of addressing these topics, has definitely stuck in my mind.

In addition, Jimmy talked about Eric Evan's book "Domain Driven Design" and that it "is like poetry". I loved that and immediately went to find some text from it to understand what he meant and I totally agree. It's not like a typical technical book to begin with because it is all concept and written from the heart. It really made me look back at how I was "speaking" when writing my book which is very different than how I write, for example, here in my blog. In the book I am trying to explain technical concepts, how to, how to code, what does this mean, what does that mean, how does this thing work, etc...and it feels much more formal. As I go back and review what I've written, I hope to loosen it up a bit. And eventually, I'll get to read Eric's book for content, not just writing style, but for the time being I need to stay focused...

And in the meantime, I'm really excited that Jimmy & Eric are both part of the advisory group for v2 of Entity Framework.

Anyone who knows me knows that I just LOVE being in the middle of a controversy. Well, that's a lie. I sure know how to pick'em, though, eh?

I have to deal with java and open source people (many who I am friends with, respect and admire) harassing me because I use Microsoft products.

I have to deal with C# developers (many who I am friends with, respect and admire) harassing me because I code with VB mostly.

Now I have to deal with Domain Driven Developers (many who I am friends with, respect and admire) harassing me because I have been busting my ass learning about Entity Framework and trying to share what I know because there are going to be a lot of people who will have to learn how to use it.

So now there's this no-confidence vote to ... I think just counter all of the information about what EF is and can do to vocalize where it's failings are if you have a particular programming style which is not supported in v1 (though are targetted for v2 and important to the EF team) and to take the EF team (which is part of the Data Programmability team, which is part of the SQL Server team) to task for creating a data-centric framework. However, the way the petition is laid out is to list it's failings to be sure that nobody gets "tricked" into using Entity Framework. Not to say the only problems are from the perspective of Domain developers, or nHibernate users or those who need Persistence Ignorance. I struggle with it too, but I just don't have the same needs as those that are listed in the petition.

I was happy to see that the Entity Framework team has responded very quickly. This responsiveness is new for them, and a new part of their recently announced transparent design for v2 which they adopted from the Astoria team.

With the exception of this past Saturday (which I took advantage of by riding my bike 50 miles to our friends' house on the lake), this has been what the forecast has looked like for the past 2 weeks. Unfortunately, this particular view is for the upcoming week.

I tried to sneak in a little ride this afternoon, but got caught in the rain.

Of course, it's not like we're flooded out, so I can't complain. We live up on a hill so we're more susceptible to the lightning than the rain.

I have no idea when this went on to Amazon, but it's there now. I STILL don't have a cover which is frustrating. And Amazon seems to have given me some extra time to finish my book! The "about the author" seems funny to me. I guess since, unlike some people, I don't have 80 books under my belt (LINQ to Dummies is #80 for John), or even one, there's not much to lean on here.

 

I think it's going to be a bit longer than 456 pages, but hell, with that big discount, I better find another day job! I think that will translate to about $1/book that goes towards my royalties! And I doubt that the book will hit Amazon's top 10 list (of all categories) like Bill, Scott & Devin's ASP.NET book which has already been reprinted numerous times!

Working with the online MSDN Library today, I lost the tree view for navigating. I finally found it, can you? Find out for yourself here!

[A New DevLife Post]

In my cycling hey day, there was no mountain road that I wouldn't try to climb. I rode over passes in Colorado, gaps in Vermont, and many routes in the Catskill mountains. While Colorado's climbs are long (15+ miles in many cases with no break) the grades are slight - perhaps 6%. In the northeast the climbs are shorter but incredibly steep - 10-15+ % grades are not uncommon.

But still that was a while ago and I have gotten older, fatter and lazier since then. (And of course spend a lot more time in front of my computer than in those days).

I live right near one of the most challenging climbs in Vermont, the App Gap (aka Appalachian Gap). The summit is 7 miles from my house. Eleven years ago I rode up the other side and still had to take a break near the top.

Whenever I ride in that direction, when I get to Route 17, I always take a right - away from the Gap climb. Last night, I did that once again, but on the way home I figured what the heck, I'll just see how far I can go.

No, I did not make it to the top. The grades get up to 18% and are relentless. I went about 1/2 way and was surprised that I even got that far but  after a 1/2 mile of struggling, when I looked around the curve and saw where I was, I knew that there was another 1/4 mile before it leveled off a bit, so I bailed.

Getting even that far was great for me, but it wasn't from some unknown source of strength because I have only ridden a total of 50 miles this season. It's more from sheer will and also thanks to my past experience of how to climb and how to pace myself. So maybe I'll start working on it. While I'd rather go for a ride where I get a steady workout rather than killing myself and then doing a long scary windy descent, there's nothing like the challenge that says "you cannot do this". The most important thing for me was to realize that it was stupid for me to wait to even try it because I will NEVER feel ready.