Changing jobs, willingly or unwillingly, is always an interesting. The best part for me is the huge amount of advice I received on how to make the transition; particularly everyone’s view on what not to do. Here is a few of the best of them including a few of my own:

1. Its ok to leave angry, but not to leave in anger…

I have personally never been a fan of the “Rage Quit”, but for one reason or the other I have contemplated it as we all do from time to time. The question you always have to ask yourself is: “Who are you really hurting?” 9 out of 10 even if the financial repercussions are not a factor you are still hurting your reputation. In IT community that is all you really have when searching for employment. All of the certification, degrees, and experience means nothing if your work reputation is poor. A good reputation can take a long time to build, but a moment to destroy.

2. Give notice

This is a common sense standard practice that holds weight in almost any industry and goes hand in hand with Tip #1. If you are ready for a new job or angry at your current position the two week notice can be the cool down period you need patch the bridge (your current position) before leaving.  If you are not interested in patching the bridge, at least you can fake it. Its better to appear less angry while making the transition in the short term, because that anger will be the last thing managers or HR remember you by, which is usually not a good thing. Not giving notice to spit an employer is like shooting yourself in the foot to get back at your shoe; the sock always pays the price.

3. If possible allow 10 days between jobs.

Now this gem was new to me, but the idea is you give yourself plenty of time to finish any “hanging chads” from the previous job and time to prep and spin up for the new position. 10 days may be to much for you, but allowing at least a weekend or a full business week between transitions should give you time to reset and re-energize. Personally I have never been in a situation where I could take that large of a break, but it must be nice…

4. Observe Everything…

The worst thing you can do is not open your eyes to everything when you start a new position. Observing your co- workers and management with the blinders off will allow you to get a full perspective on the corporate culture objectively. Typically you will find some of the critical preconceptions you may have had about the position and the environment. Additionally your observations of any gaps in process, procedure, or just common sense from an outsider’s perspective can be refreshing for management.

The most important part about any employment transition is to enjoy the ride.

So with yet another year rolling through I have to take a look at the poor set of choices I made for last years resolutions. One obvious one that I missed is “I am going to post once a week.” Well I have implemented this awesome plan on how to make this happen: I am going to post one every two weeks!. Procrastination always makes it better in the short term.

Wish me luck!

With the release of the Exchange 2010 Beta last week the lid is finally off on some of the fun Powershell functionality in new version of EMS. I am parsing through all of my notes to find the the best of the new stuff and I will be sharing some of those post this week.

IRUNDIS is back up and more Powershell is on the way!

Wuff. Another project done, but I still can’t seem to dent my list. We are almost 3 weeks into the new year I have have not stopped moving to Day 1. I am in love with CTP3 right now. I have been following the Windows Powersehll Blog intensely to see what magic they come up next. There are more awesome features in PowerShell v2 than you can shake a stick at and RTM is going to be my own nerd holiday. I have a post of PowerShell modules coming up and I will finally get around to adding those Snippets.

~Bishop

For about a week I have been using the PowerShell v2 CTP3. The PowerShell ISE  is a pretty useful PowerShell scripting environment(and yes I get the redundancy of this statement). Like its predecessors in the CTP line it allows for the creation of multiple run spaces and PSSessions (Going to take a whole post to explain this one), and finally adds context menus and break point creation.  Besides all of the awesome remote execution features there are several subtle features that will save time.

Embedded Help

I did a post a few weeks ago on how to generate a help message when “-?”, “?”, or “-help” is entered when executing a script in PowerShell. I’ve found this method pretty useful unless your try to use it with a param keyword. CTP 3 to the rescue! With PowerShell v2 you can add fully detailed help to any script just like fully functional cmdlets. Here is example:

Code:

    #.Synopsis
    #   Use this to provide a quick description of the script.
    #.Description
    #   Provide a fully detailed description of the script.
    #   Provide a background on how to use the script with its key parameters
    #  
    #.Parameter Parameter 1
    #   Describe this parameter and how it should be used.
    #.Parameter Parameter 2
    #   Describe this parameter and how it should be used.
    #.Example
    #   Provide your usage description.
    #   Provide a full example of the script and how it should be used

Add this snippet and replace the fields with information that is relevant to your script.

Results:

Results of the Get-Help

Out-GridView

Considering that I have spent about 100% of my powershell scripting over the past coupleof weeks creating reports for various Exchange related stats, I can say I hate looking at CSV files. Once again PowerShell v2 to the rescue! The Out-GridView cmdlet produces a sortable filterable table output for object. As with all of the other “Out-” cmdlets you can supply the objects through the pipe or direct to the cmdlet through the “-input” parameter. The GUI table that is produced allows you to apply additional filters to the ouput which provides for even more control.  Here is quick example:

Code:

PS C:\> Get-Process | Out-GridView

Results:

Out-GridView Example

I am slowly working through the list of new commands in PowerShell v2, so there will be much more to come.

~Bishop

  • Listening to 20′s yazz flute with my wife #
  • Struggling with a “throw”. I won’t have to deal with this in Powershell v2 goes rtm, but until then…. #
  • Reading a powershell manual #
  • Its my one pop indulgence outside of the occasional mid eighties power ballads: http://tinyurl.com/a4radx #
  • Driving through the Seattle snow/rain/mush is so fun… #

Microsoft released Powershell v2 CTP3 today. I just got it installed but I let you know how much fun it is after a few hours.

Download: http://www.microsoft.com/downloads/details.aspx?FamilyID=c913aeab-d7b4-4bb1-a958-ee6d7fe307bc&displaylang=en

I am working on a quick template to build simple object based reports. I have had some time to refine my technique so I should have something solid to post the end of the Christmas break…. Unles….

© 2011 Bishop's PowerShell and More Blog Suffusion theme by Sayontan Sinha