Thursday, March 26, 2015

More Frustrating than the Chicken and Egg Problem....

So you've been brainstorming for the past five hours and you've finally come up with the next billion dollar idea. It's a platform that lets buyers and sellers talk to each other and transact business while you take a cut of every penny that passes. You're going to make billions, right? Of course!

You start canvasing your area talking to buyers, introducing them to this revolutionary idea of yours, but one question keeps popping up: How many sellers are there on your platform? You pause. You realize that a change of strategy is in order - get sellers then come back and get the interested buyers.

You head out the next day, this time hunting for sellers. You get some meetings and each time at the end of your fancy presentation you get the question: How many buyers are there on your platform?

You, my friend, have a classic case of common "chicken and egg" syndrome.

This, no doubt, is frustrating and you are, in fact, tasked with finding very creative ways to overcome this problem. However, what if I told you that there's something worse than this? What if I told you that there's something more frustrating than spending months setting up meetings, tweaking the product, getting the word out and polishing pitches only to end up sitting late at night propping your jaw trying to figure out how to get sellers and buyers to drink from your milk saucer?

What if I told you that there is a situation in which you create the "perfect product" that escapes the clutches of ye old chicken and egg and is aimed squarely at a unidirectional audience that loves it but simply won't try it because it's a new product that nobody's tried before?

There is a name for this type of situation. I call it the "You Go First" situation - that's where several potential clients are standing in a circle around your product; all of them waiting for the other to try it first meanwhile you just sit there cueing them on to "step right up" while they all stand there stroking their chins; it's like you're the only guy at a kissing party and the girls all want to kiss you but they're each waiting for someone else to make the first move because nobody want to appear to be the thirstiest of thirsties. You know what happens in that scenario? The parents come home and break up the party before any lip locking gratification can be had - everybody misses out because nobody wanted to be the one to make that bold move. Who knows where the evening cold have gone? I digress...

It's amazing - you come to a client that loves you and your product. They believe that the idea is novel, and it's the shot in the arm that the industry needs. It will cost them $0 to try and involve very  minute changes (if any) to their business process while maximizing profits and saving them tens or hundreds of thousands of dollars in the process... but they're skeptical to try it because nobody else has tried it yet.

That, my friends, is the state of the soil that we entrepreneurs are attempting to till to plant the seeds of innovation here in T&T. That's one of the reasons why great products (especially technology products) aimed at a T&T audience seldom succeed.

You think it's because most ideas are crap? No! Well, some of them are, but the point is that some of the great ideas, the really good ones are left out in freezing limbo until the money in their veins dries up and the entrepreneur has no choice but to move on and either a.) get a job and become another working stiff or b.) hunker down and set up camp somewhere else.

Is the situation unique to T&T? Of course not. I'm pretty sure this exists in other places as well, but does that mean it's acceptable?

As for what can be done about the situation, I'm fresh out of ideas. All I can suggest is prayer and patience. Every business owner has the right to accept or not accept any business proposition no matter how good it may appear to be. Here's hoping that this generation will see the last of this type of thinking.

Tuesday, March 17, 2015


So this is where we've gotten to, huh? A teaser, for a teaser for a poster that will probably tease a teaser for the first official trailer.

Back in my day the official trailer served as the teaser for the movie. I wonder what happened?

Friday, February 20, 2015

Yes It's Still Coming...

Those of you in my other social circles would have seen me tease a bit of big news a couple weeks back and promised to reveal the big surprise shortly after.
Admittedly it's taking just a tiny bit longer than expected, but I want to make sure all the nails are flush, screws are tight, I's are dotted and T's crossed before I yank the veil off. Trust me, it's that big a deal, both for me and for the latest iteration of my pet project - Linq.

Stay tuned to the blog this coming week to see what's happening.

Friday, January 16, 2015

Only Fools Rush In

Image of Java, er, Old Faithful
I fear I may be getting old. There was once a time when I rushed for the latest technology stack being touted as the "hip new way of doing x, y and z" and scoffed at the older "dinosaur" programmers who were reluctant to try out this new hotness that's being lauded by Reddit users and is steadily gaining traction on Github.

Four years have passed, and upon reflecting on my habits for selecting technologies for projects as of late, it would seem that I, too, have joined the dinosaur herd... but is that necessarily a bad thing?

I mean, sure, this new framework or tool has a flashy new website with parallel scrolling and SVG animation out the wazoo, but does it mean that it's time to flee from my resting place on the rock of surety and hop and skip on the ever changing, ever shifting (and ever deprecating) sands of "the new hotness?"

The obvious answer would be yes and no - yes, because in this line of work you need to keep that skill base very up to date, and no because nothing is worse than setting your heart on a way forward with a framework only for it to get uppity and start meandering down a winding road of deprecations, refactorings and (sometimes) outright revamps and you find yourself pushing back deadlines as you scramble to re-learn the damn thing because v2.0 took v1.9's APIs out into the back yard and put two to the back of its head.

My point is don't rush for the new technology/framework/stack as soon as you hear about it. If it's still in version 0.x.x it's probably best to keep away from it until it matures a little bit more. Basing any of your production applications on a technology this early in development is making ample room for headaches later down when updates are due. No one is saying to avoid new tech completely though - download it to your sandbox and build a few small apps; it won't hurt. You might even be able to contribute code to the project in the process.

At the time of writing NodeJS is currently at version 0.10.35. Will I select it as the foundation for  my next official project? No. I will, however use it and the (very awesome) Gulp plugin to compile my Less CSS files, minify my Javascript and other small things. And yes, I've only just started using build tools over the last week or so. For my next major project I would much rather rely on the stability and "boringness" of Java. I can bet my bottom dollar that there's a library to perform almost any task and a documented solution to any problem I might encounter during development. The framework launched about a year ago is not as likely to afford me this comfort. Sure Java might not be a sexy as [insert new-fangled language here] but it sure is faithful and, most importantly, predictable - attributes that make it my primary choice for major application development.

It might seem obvious, but don't use early stage technologies heavily in production. Stick to something that's a lot more mature and stable to avoid surprises and headaches come update time.