Michaeljon Miller - All Comments

re: IEEE Spectrum article on Green Energy

tonyr — Mon, 14 Dec 2009 21:09:43 GMT

"helping other countries come par with our lifestyle. It’s only fair, and it’s only a start."

this sentence is the key to all of this, earth does not scale well. Darn..

re: Learning as a family trait

Anne Stanton — Tue, 17 Nov 2009 13:07:05 GMT

I so agree!

My mom recently passed away and someone mentioned that they were surprised that she received her college degree in 1945. She also went back after years and received her masters and doctorate. I never say her without a book in her hands and her passion has been shared with all of us.

People don't die when what they talk carries on and is shared with those they loved and those that those loved love.

For U.S only?

Michael Aulia — Tue, 07 Jul 2009 10:04:56 GMT

Is this for U.S only? Can't seem to enter my Australian PostCode

re: Announcing Microsoft Hohm

Someone — Thu, 25 Jun 2009 05:57:30 GMT

I don't know where my home falls, because the only thing the site wants is my e-mail address. You should go back to working on CRM.

re: It’s getting warmer in Bellevue?

Michael Höhne — Wed, 26 Nov 2008 11:48:42 GMT

Great story and I hope that many others will follow your example. Even if it takes more than 10 years to pay back, it does pay pack, and you are helping the environment by saving energy.

re: It’s getting warmer in Bellevue?

crmblog — Tue, 25 Nov 2008 22:44:12 GMT

Do you have a fixer up house? If so check the paint on the outside of the house. The fixer up I bought hadn't been painted in 40 years! And that speeds up the decay of the siding.

re: It’s getting warmer in Bellevue?

David Smith — Mon, 24 Nov 2008 18:12:44 GMT

New windows are definitely a long-term investment - if you find other places around the house to get a faster ROI you can get a bigger bang-for-buck window-wise by caulking and adding heavy blinds or quilted curtains - open them when the sun is warming the room, close them as soon at it starts to get dark. Must faster return, and you can wait until you get a killer deal to invest in the long run.

re: I've decided that I finally really give up on stored procedures

MJ Miller — Mon, 30 Jun 2008 22:55:16 GMT

We're talking about different things I think. I agree that sprocs are just another language to use, albeit one with a very different build / test process.

The problem I run into is dealing with many databases, all serving the same multi-tenant application, but with tenant-specific data. In this case, think hundreds of tenants, you need to visit every database to update a given sproc if / when there's a bug found. Sure, it's easy to write an automated script to do this, and I'd recommend using one even for a single database, but it really isn't something that screams "great engineering practice". You wouldn't have 100 copies of an assembly on a machine, one for each customer, would you?

re: I've decided that I finally really give up on stored procedures

Steve Jones — Mon, 30 Jun 2008 22:03:43 GMT

I'm not sure I agree. A stored procedure is another function that you call, and it allows you to reuse those components from other applications, or other places in your application, and tune appropriately.

They don't take any longer to build than any other function you add in your application, thought it's a different process you have to get used to.

I'm also not sure how you calling multiple databases means that stored procedures are a problem? If you make two calls from your app, why not call two procedures? If you join together disparate data sources, this can be done in stored procedures.

I'd like to see a followup post on how that works.

I think a number of reasons listed in the link aren't accurate as well. Some are, but my guess is that the writer hasn't used stored procedures properly and then complains that they don't work.

re: I've decided that I finally really give up on stored procedures

MJ Miller — Mon, 30 Jun 2008 19:43:43 GMT

That would be great if it really worked without jumping through a ton of hoops. The problem is that the proc wants to run in the "proc" database despite the context ("data" database) and the four-part calling convention. I'm open to suggestions and ideas if anyone wants to convince me to come back to the dark side :)