Blog

  • What Does it Take to Outsource You?

    I was reading CNN’s money site and various other similar news sites, and reading how IBM was failing to sell itself to investors. While investing heavily in India since sales there were up, the article cites how this isn’t enough to help their stock. They aren’t the only companies doing this, so selling services merely on price won’t work very well when the competition is doing the same.

    My Dad in his business refuses to sell on price and makes it to point to be the most expensive distributor in his region. In fact, the more he raises his prices, the more business he gets. You gotta find that sweet spot, and he can attest to earning that price. Lines such as “call my competition on a Sunday, and see who calls you back”, and other sincere pitches backed with a long list of referrals allow him to stand behind his price vs. in front of it.

    So, upon reading that article, and others similar to it (and having the knee jerk reaction of being spooked), I figured it’d be a good time to see what it’d take to outsource myself. I basically outlined some basic Flex programmer qualities I felt prevented me from being outsourced, both on their own and collectively, and justified why people were calling me to come work for their startup or asking my advice on Flex stuff.

    I never published it as a blog entry, though, because I felt it grossly neglected all the things I bring to the table, and showed my skill set in a negative light. This wasn’t my intention, but it was just too hard to change. The silver lining I later found, however, is it was a great exercise in self-assessment.

    You basically look at why a client would hire someone in another country over you based solely on price. What do you have to offer that the person in another country does not? Do those qualities truly set you apart? If so, how long do they last? Could those qualities be adapted by those in other countries that work for less than you do to give them the competitive edge?

    It also shows you what areas you can focus on more and improve, and what areas you can potentially get into, some which are exclusive to locality.

    On the flip-side, I was reading a magazine article over the weekend in some business mag (Business Week or Business 2.0) that countered some of the points the CNN article made. For one thing, the CNN article, referring to India, says:

    …going to where the programmers are…

    Talking about India’s extensive and less expensive talent pool. Yet, the article I read stated issues in that salary rates for Indian employee’s are growing. Indians aren’t stupid, just cheaper. They are realizing they don’t have to work dirt-cheap to be marketable because “they charge less”. I think managers average salaries went up to $32,000. That might not sound like much to those living in San Francisco or New York, but that’s actually not to shabby of a salary in less expensive areas, and I know for a fact you can have a nice flat, your own driver, and maid in India for that much.

    The article also stated the high turnover problem and high competition for good talent. Gee, uh… what country does THAT sound like for Flex, Flash, & ColdFusion developers… America!

    Even if Indian programmers never start charging as much as American ones do, I’m still excited by globalization. I’m competitive and love to win. Competing with programming talent that’s in 300 million Americans is fun, no doubt, but the big leagues for me are the 700 million tech-savvy Indians between the ages of 15 and 35, and Lord knows how many Chinese, Indonesian, etc. The whole world combined? Bring it!

    Even as much as two years ago, I’ve heard of Indian firms charging more than some American firms do for projects. That says volumes. If you’re talent really is that good, and you have the communication network set up that you can facilitate an almost-like-local presence, why NOT charge more?

    I still think they’ll have to charge less, namely because of the time zone gap. One of the main reason I turn down startups, aside from my current gig being really cool, is mainly from the fact that I don’t feel like having to deal with people I can’t talk to. While I do pretty well dealing with my current team of telecommuters, even when one is on the west coast, and me being on the east, it can cause challenges. One thing is a definite; without people at least in the same to 1 off time zone, you won’t get immediate resolution to problems. To some large companies who have projects lasting 2 years, that really isnt’ a big deal, nor event worthy detail to them. The consulting firms who have to deal with it might not care either.

    I sure do. If I’m held responsible, you better be within choking distance if you start smoking crack… or high five distance if you p@wn a problem. But then, it’s not up to me, but rather the clients that hire you to do the work. If they want immediate resolution, they’ll pay for it.

    Anyway, I highly suggest you try it. If you’re not in a country known for being outsourced to, write down things that you think justify why you are not yet outsourced. Hopefully it’s a good self-assessment tool, as well as showcasing potential areas to learn more about, and/or improve upon. The important thing to remember is those qualities are not a definitive list of what really makes you important & valuable to companies, but writing them down certainly helps you add them to your elevator pitch if they are not there already.

  • New Site Design

    I’ve implemented the first stage of my new site design. It will take me another 2 weeks to implement additional navigation, fix some IE specific issues, and optimize the CSS & images. If you have problems (visual or technical), please leave a comment here. I’d love to hear them!

    I’m aware the main navigation links are broken on IE 6 Windows. For you IE Win users, until I have time to fix the transparency issues, here’s the About page and the Search page.

  • Mediatemple Has No Plans for Flex Data Services Hosting

    *** Update 7.14.2006: Got an official update.

    (mt) Media Temple currently has plans for turn-key hosted Flex Data Services solutions. Although we don’t have a confirmed timeline for the rollout of these products please be assured they are in our pipeline and will be prioritized based on customer demand.

    *** Update 7.12.2006: Been shooting emails back and forth with David Feinberg, a Product Manager at Mediatemple. He says they DO have plans, and are working on getting FDS setup. w00t! ***

    I just asked Mediatemple sales and got a response. More specifically:

    …To answer your questions specifically; at this time we don’t have any immediate plans to upgrade. Please check with our site or with me at a later time. …

    Anyone know of any hosting companies that plan on doing Flex Data Services hosting?

  • Flex Chronicles #18: Extending Controls & doLater

    When creating custom components, a lot of times it’s just easier to extend existing controls. For example, creating an auto-complete text field isn’t so hard; if you extend mx.controls.TextInput, the only code you have to write is for handling creation of the popup, and handling keyboard events.

    The problem is validation. It’s an extremely complex process that works in many passes. In Flash MX 2004 and 8, it was constructor, init, createChildren, draw, and size. There were other minor, but integral functions in that process, but basically it comes down to create it, set it’s default properties, and render the mofo. This strong arm approach didn’t scale to Enterprise apps very well.

    Enter the Flex framework. They further fine tuned the invalidation routines. Not only could you defer sizing and drawing to the next redraw event in the Flash Player, but all kinds of properties and styles. If you’re a seasoned Flash Developer, you know if stuff appears “not ready” you just wait a frame… or two. In Flex 1.5, things are no different. Typically, you can use a doLater (or 8) with simpler recursions for a lazy approach, or you can find what properties in particular start the process as most are pretty blatant (anything that calls invalidate).

    I may sound like I’m bashing it, and I am, but it truly is valuable. Drawing once per redraw is better than attempting to draw 300 times a second when you can only draw 30 times a second. This is before refactoring and optimization of course. It’s just it’s extremely confusing the nuances of how those affect those extending the framework classes. You shouldn’t use Composition over Inheritance because you’re afraid of extending a class, instead feeling more secure by wrapping your own proxy methods around it as a safety net.

    As a component developer, you may think you can take advantage of this, and you can. All the plumbing is held mostly in mx.core.UIObject and all his CSS and LayoutManager friends have hooks nicely integreated. The problem is mixing methods that redraw your GUI immediately vs. later. So, if you write methods that draw your GUI, and mix invoking them elsewhere with doLater’s, you can get unexpected results. The reason for this is that doLater’s are added to an array, and dealt with next screen redraw. After they are dealt with, they no longer exist.

    I ran into a situation today where I was calling doLater in a class that extended TextInput, and they’d disappear off into the ether. The reason was, the method I was calling before was setting the “text” property. This is a getter / setter that actually causes invalidation. I’m doing the exact same thing in 2 places; calling a method that causes invalidation and then immediately calling a doLater after it. The only reason the second one fails is because the onEnterFrame spins off into the ether. The cause? Not sure. The first method is called when the internal component fires the enter key presseed event. The latter, broken, method is called in response of a List control being created in a popup being clicked on.

    My guess is, the List emitting an event, and immediately being destroyed via a call from a Delegate scoped function somehow ticks off the internal guts of the UIObject, confusing it’s scope, and thus refusing to deal with the methodTable. Meaning doLaterDispatcher is apparently never fired even though onEnterFrame is happily chugging away, 21 times a second, doing nothing useful, eating CPU cyles.

    My fix? Make all methods excluding the invalidation causing one to use doLater. Since there is no operator, similiar to public and private that goes something like “causesinvalidation”, I’ll just have to be extra mindful when extending controls that if I’m doing something that will cause multiple invalidations, I’ll have to provide a better conduit, such as a funnel method (you wanna redraw, you call me), or some other proxy.

    Bottom line, if you doLater’s are failing to fire, try converting all functions to a doLater and/or indentifying what property you are setting / method you are calling that is causing the invalidation and tread around it.

    …or build your own invalidation. Make a movieclip, make it’s onEnterFrame call your function via closure, and then immediately have it remove itself. This has worked flawlessly since Flash 4.