For the first time in my career, I'm turning to a professional resume writer. With more than 15 years in the tech industry and at a crossroads in my career, I decided that it was time to treat myself to a little bit of polishing. Because I do not have a traditional CS degree, I thought it necessary to carry all relevant experience on the resume so the format is now a tired one.
A resume review service is included in the signup to the http://www.theladders.com. Granted it is only a review, but it is being reviewed by a professional resume writer. I'm sure that there are additional services that the reviewer offers and I intend to avail myself of those services. How much will it cost for the additional services is floating around in my brain, but I figure with my unscientific supposition that with her touch on the resume would be worth many times that in job opportunities and even salary. I'm sure it will make a difference.
I even have gone as far as holding off applying for some nice jobs in the hopes that my resume receives the polishing it needs. Wish me many happy returns. :)
Monday, June 25, 2007
Friday, June 22, 2007
Having an older sibling..causes stupidity
Have you seen this? http://www.msnbc.msn.com/id/19373032/site/newsweek/
Many write ups of this study assume or imply that the firstborn is smarter than his siblings. One of the reasons I saw was that possibly because the elder tutors the younger and so gets smarter. (I searched my memory banks for references to my elder brother tutoring me and have come up quite empty) Shall I say "Ehhh-no"?
Unfortunately no one considered what the data might really be telling the researchers. The real effect is that having an elder sibling makes you dumber. This study isn't about my parents mistake because they happen to pop me out 2nd instead of first. It's about how my elder sibling's very presence is the cause of my stupidity and the reason my parents thought (think) "my elevator doesn't go all the way to the top".
Hmmm...that should put some new light on this study. :) :)
Enjoy!
Many write ups of this study assume or imply that the firstborn is smarter than his siblings. One of the reasons I saw was that possibly because the elder tutors the younger and so gets smarter. (I searched my memory banks for references to my elder brother tutoring me and have come up quite empty) Shall I say "Ehhh-no"?
Unfortunately no one considered what the data might really be telling the researchers. The real effect is that having an elder sibling makes you dumber. This study isn't about my parents mistake because they happen to pop me out 2nd instead of first. It's about how my elder sibling's very presence is the cause of my stupidity and the reason my parents thought (think) "my elevator doesn't go all the way to the top".
Hmmm...that should put some new light on this study. :) :)
Enjoy!
Wednesday, June 20, 2007
Composite Controls in .NET 2.0
These days I'm playing developer, but have my architecture hat close by in the remote chance that I'll get to try it on just even to see if it still fits.
Current interest is composite controls in ASP.NET for the 2.0 framework. I've written a control that combines a textbox with an imagebutton needed for the application that I'm working on. The idea is the user would type some (or no) text in the textbox and then hit the search button that would do a partial search or bring up a dialog for more search criteria depending on the properties set. The reason I turned this into a control, is that it is used all over the application and you know all about architects and consistency....
In experimenting I've found that it is easier to declare the controls as member variables and then instantiate them in the constructor. As properties are set (from parsing the aspx page) or from setting the properties in the class file, it is easy to set the corresponding property of the member variable. Then when you get to the code for CreateChildControls all you have to do is Controls.Clear() and then add your controls without having to set a bunch of properties.
Every example I've seen so far sets all the properties within the CreateChildControls code and this seems a little to heavy handed to me.
Right now in my mind, I'm not sure if there is a downside to doing it my way. Maybe the only thing I can think of is that it violates the aquire late/release early mantra. I'll have to do some testing before I'm completely satisfied.
Current interest is composite controls in ASP.NET for the 2.0 framework. I've written a control that combines a textbox with an imagebutton needed for the application that I'm working on. The idea is the user would type some (or no) text in the textbox and then hit the search button that would do a partial search or bring up a dialog for more search criteria depending on the properties set. The reason I turned this into a control, is that it is used all over the application and you know all about architects and consistency....
In experimenting I've found that it is easier to declare the controls as member variables and then instantiate them in the constructor. As properties are set (from parsing the aspx page) or from setting the properties in the class file, it is easy to set the corresponding property of the member variable. Then when you get to the code for CreateChildControls all you have to do is Controls.Clear() and then add your controls without having to set a bunch of properties.
Every example I've seen so far sets all the properties within the CreateChildControls code and this seems a little to heavy handed to me.
Right now in my mind, I'm not sure if there is a downside to doing it my way. Maybe the only thing I can think of is that it violates the aquire late/release early mantra. I'll have to do some testing before I'm completely satisfied.
