Showing posts with label Joke. Show all posts
Showing posts with label Joke. Show all posts

Monday, June 30, 2008

Where to go?

Where to go?

It is hard now, our economy is diminishing, contracts are few and far between giving a feast or famine future and local prospects just don't recognize an entrepreneurial spirit.

I have been contracting as a web designer, since early 2000 and have been reassessing and shifting to freelance photography and even to shooting video trying to build my skills in a diversified manner that marks me as "indispensable" to future patrons. But the truth is, I am just a clone of all the other "hopefuls" that are doing the exact same thing.

The reality is, while knowledge of computers and enthusiasm for writing and creating videos are fun to do. They tend to leave one standing beside themselves.

While I have had dreams of working for Google and Apple, even to the extent of bettering my odds by actively promoting Google's technology with the gPhone and proudly attended the Apple's Developers Conference. Not a single offer has come to my table. Oh I get recruiters calling me to no end, promising me the moon and all the cheese it is made of but as the date progresses I am just another name and number for their little black book and I don't even know how many stars they give me.

So, I stick to my freelancer ways, insisting to contract out my professional services as opposed to delude myself into thinking that a job will really give me security, not that I believe that any corporation could truly provide anything more stable than I could.

True to my nature I find it hard to work for people than to work with them for a mutual business advantage. To be an employee seems to be a joke, not because I am adverse to working as a team or to work for a greater common goal of fiscal success, far from it. The frustrations of dealing with the politics of nepotism and playing favorites to under-qualified "buddies" of the manager is a constant theme of working a regular job, with regular people as opposed to an interesting gig that will allow for more dynamic possibilities.

All things being equal, I must confess hindsight being 20/20 I do not feel that my focus in freelancing endeavors are a waste of time or my resources. To be honest, I don't think I would of been introduced to the variety of opportunities (even if those opportunities did not land anything or go the direction I had hoped for). But that is just me.

So, would I ever consider conventional employment? Well, as strange as this may sound I do not see the distinction between a full time job or a contract that requires my full time attentions. The legal world seems to create a artificial circumstance for a full-time employee, a W2 employee seems to be more controlled and dummied down control of creativity and time (punch in the time clock, do work, clock out for lunch, eat lunch, clock back in for lunch, do more work, clock out).

As a contractor you have more control over this time to use it creatively and more efficiently and here in lies the problem as described to me by the CEO of Javaground:

I was interviewing with the CEO who explicitly told me that he would never consider incorporating me into his company as a contractor for the main reason that he could not have complete control over me. As an employee he could better have control over me and my loyalties would be more to his company and not my own consultancy.

I protested and told him that as a consultant, contractor he would have access to my entire professional network and as far as my loyalties to his company, Non Disclosure Agreements would legally prohibit me from playing the field and compromising secrets of his company. He still wanted me to be a regular employee, he still wanted that illusionary control over my time and loyalties. To my perception as a contractor/consultant the demand on my time and the loyalties to my new patron would be no different than being a regular full time employee.

My rational words fell on deaf ears, he didn't care, he wanted an employee and I wanted a business partner and I politely disengaged from further negotiations on the subject and consequently did not receive an offer to work for his company.


It would of been a cool company to work for, but in retrospect I am glad he never followed up with me. In my eyes if he was honestly that adamant over the semantics of my professional relation to him and his company then we probably would not of been able to work well with each other in the first place.

So, Where to go? Is probably not the right question to ask, more to the point should be the question Whom do I ally myself with?

Sunday, February 24, 2008

Wife v1.0

Girlfriend 6.0 vs. Wife 1.0
Comparative Trial

Last year a friend of mine upgraded from GirlFriend 6.0 to Wife 1.0 and found that it's a memory hog leaving very little system resources available for other applications. He is now noticing that Wife 1.0 is also spawning Child Processes which are further consuming valuable resources. No mention of this particular phenomena was included in the product brochure or the documentation, though other users have informed him that this is to be expected due to the nature of the application.

Not only that, Wife 1.0 installs itself such that it is always launched at system initialization, where it can monitor all other system activity. He's finding that some applications such as PokerNight 10.3, BeerBash 2.5, and PubNight 7.0 are no longer able to run in the system at all, crashing the system when selected (even though they always worked fine before). During installation, Wife 1.0 provides no option as to the installation of undesired Plug-Ins such as MotherInLaw 55.8 and BrotherInLaw Beta release. Also, system performance seems to diminish with each passing day.
Some features he'd like to see in the upcoming wife 2.0.

  1. a "Don't remind me again" button
  2. a Minimize button
  3. An install shield feature that allows Wife 2.0 be installed with the option to uninstall at any time without the loss of cache and other system resources
  4. An option to run the network driver in promiscuous mode which would allow the system's hardware probe feature to be much more useful.

I myself decided to avoid the headaches associated with Wife 1.0 by sticking with Girlfriend 7.0. Even here, however, I found many problems. Apparently you cannot install Girlfriend 7.0 on top of Girlfriend 6.0. You must uninstall Girlfriend 6.0 first. Other users say this is a long standing bug that I should have known about. Apparently the versions of Girlfriend have conficts over shared use of the I/O port. You think they would have fixed such a stupid bug by now. To make matters worse, The uninstall program for Girlfriend 6.0 doesn't work very well leaving undesirable traces of the application in the system. Another thing -- all versions of Girlfriend continually popup little annoying messages about the advantages of upgrading to Wife 1.0.


Bug Warning

Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then Mistress 1.1 will refuse to install, claiming insufficient resources.

Bug work-arounds:
To avoid this bug, try installing Mistress 1.1 on a different system and never run any file transfer applications such as Laplink 6.0. Also, beware of similar shareware applications that have been known to carry viruses that may affect Wife 1.0. Another solution would be to run Mistress 1.1 via a UseNet provider under an anonymous name. Here again, beware of the viruses which can accidently be downloaded from the UseNet.


Tech Support Suggestions

These are very common problem men complain about, but is mostly due to a primary misconception. Many people upgrade from Girlfriend 6.0 to Wife 1.0 with the idea that Wife 1.0 is merely a Utilities & Entertainment program. Wife 1.0 is indeed an operating system and designed by its creator to run everything.

It is unlikely you would be able to purge Wife 1.0 and still convert back to Girlfriend 6.0. Hidden operating files within your system would cause Girlfriend 6.0 to emulate Wife 1.0 so nothing is gained. It is impossible to uninstall, delete, or purge the program files from the system once installed. You cannot go back to Girlfriend 6.0 because Wife 1.0 is not designed to do this.

Some have tried to install Girlfriend 7.0 or Wife 2.0 but end up with more problems than the original system. Look in your manual under "Warnings - Alimony/Child support". I recommend you keep Wife 1.0 and deal with the situation.


I suggest installing background application program C:\YES DEAR to alleviate software augmentation. Having installed Wife 1.0 myself, I might also suggest you read the entire section regarding General Partnership Faults (GPFs). You must assume all responsibility for faults and problems that might occur, regardless of their cause. The best course of action will be to enter the command C:\APOLOGIZE. In any case avoid excessive use of C:\YES DEAR because ultimately you may have to give the APOLOGIZE command before the operating system will return to normal. The system will run smoothly as long as you take the blame for all the GPFs.

Wife 1.0 is a great program, but very high-maintenance. Consider buying additional software to improve the performance of Wife 1.0. I recommend Flowers 3.1 and Diamonds 2K. Do not, under any circumstances, install Secretary with Short Skirt 3.3. This is not a supported application for Wife 1.0 and is likely to cause irreversible damage to the operating system.

Best of Luck,
Tech Support