Anyways, about year ago I was working on moving some parts of our deployment scripts to PowerShell. One of the things that was on the to-do list was parsing and building hashes out of .ini style files. It was not uncommon to find these files used for persisting configuration information and also for automation so, I assumed we would have a built-in cmdlet to cover this kind of a file. We do not have it.
It is a little disappointing but, since the structure of the file is almost static; we can code very easily around it.
I am going to be writing about resolution.
To me the word means, ‘firmness of purpose’. That dogged resolve to see through an issue to the end is something I miss dearly but, I would like to make a very conscious effort towards giving the best I can when working on something.
Being proactive and industrialization of existing solutions are some of the goals I set this year.
When you are working as part of a team that manages a few hundred SQL*Server instances; sometimes, it becomes hard to keep track of all the people who need to be notified when you plan for database migrations and such. Also, if there is an issue that needs their input ($’s); we do not want to send it to the wrong person now, would we. Maintaining the information in excel sheets is good but, wouldn’t it be nice to have the information available on the DB itself? We can get all the information in one shot and send out e-mails to the concerned (correct) individuals.
The WordPress.com stats helper monkeys prepared a 2012 annual report for this blog. Here’s an excerpt: The new Boeing 787 Dreamliner can carry about 250 passengers. This blog was viewed about 1,800 times in 2012. If it were a Dreamliner,…