This one is just for me, so I don’t forget where I read this article:
This is a really great read on building your own IDataContext.
I’m toying around with the idea of changing it to just saying IUnitOfWork instead, so I can use the idea as a way to wrap LINQ2SQL contexts, as well as NHibernate sessions, etc.
Linq to Sql, Programming Against an Interface and the Repository Pattern
I’ve been plagued with an issue that I have yet to find a solution for.
This is really more for my benefit so I can research this later, but basically when I create classes I tend to decouple them by using interfaces, especially between layers.
The problem is when you use a service layer, such as WCF, that the class that is generated on the client side doesn’t carry the implementations that the server side class has.
Then I found this article which might be my saving grace. It lefts you actually reference the same class on the client side. This might be solution I’m looking for.
Once I get a chance to test this out I’ll post the results with some code.
I just got an email from a friend of mine with this and I couldn’t pass up throwing this on my blog.
Here’s the original article that this came from.
Enjoy!
I just recently got a new phone, a Droid Eris. So far I’m liking it a lot. The keyboard is surprisingly easy to use. I haven’t gotten around to tethereing the phone yet, but thats my next step. Then I’ll be able to use my computer from the road, something the iPhone didn’t offer me, which is why I went with an Android phone. So here’s hoping!
I was just watching a television show that’s a drama about the medical field. The particular episode I was watching perfectly illustrated the reason why Health Care in our country has completely gotten out of control.
The scenario: A patient has lost one of his digits (his thumb to be exact), and requested that the minimal amount of surgery be done on him as to avoid costs from his medical insurance. His insurance only covers 60% of what they deem major surgery. He also indicated that if it was too much he wouldn’t sign the consent forms and would rather not get the surgery at all and just lose his thumb.
The doctor, in response to this patient, decides to get the patient’s consent for the least amount of surgery possible (basically to just attach the skin, but keep in mind this is fictitious), and after getting the consent and putting the patient under he proceeds to fully attach the mans thumb even after being explicitly told not to do so. Now this isn’t what I’m saying the problem is, because I don’t really think a doctor would do this in real life. The problem is what is to come, and shows the mentality that a lot of people with power seem to have.
The hospital ends up getting sued by both the patient and the insurance company, because both parties are unwilling to foot the bill (imagine that), and so the manager of the hospital goes to the doctor to confront him about the consent issue and the surgery.
Here’s the problem: The doctor, at some point, responds, “I wasn’t going to let the guy throw away his thumb just to save a few bucks.”
It may sound reasonable at the front of it, but consider something else. The manager said the cost of the procedure was $80,000. Taking into account for the fact that the patient would be responsible for a minimum of 40% of that amount, you’re talking $32,000. That is not a few bucks.
Now the crux of this whole thing comes falling down. Ultimately who’s responsibility/right is it to decide whether this procedure is done or not? It’s the patient’s. He decided he didn’t want it done; respect the decision. Our mentality about Health Care in this country needs to change from the mentality of this doctor. We need to give respect back to the patients. They have the right to choose. They have the right to negotiate price. They have the right to refuse. They have the right for a second opinion. They have a right to their own opinion.
Ok, we finally have the board. Exhibit A:
I decided to keep the basic layout that I talked about earlier, but my wife wanted to flip it so the people were on the side and the stages were on the top, but none the less, the layout of the board is still the same:
We had our first weekly meeting, where everyone decided the things they needed to get done in the coming week. We also had some discussion about things that we all shared, like doing dishes for example. After we got everything down, this is what the board looks like:
And we also made a “Dailies” chart for Sarah. These are things she has to do every day of the week. She’ll check them off as they complete them, unless they need approval from a parent before hand, in which case the parent does the final sign off.
So, week 1 begins!
Is this hard to understand?
What is the email address on this card?
Maybe this is more understandable?
or I could swap the email and the site, maybe that makes it easier to read.
I’m getting there! This was suggested by Steven, and I think he’s completely correct.
