Skip to main content

Blocking Issues

We built Jawaya on Rails. At the time it kind of made sense; Rails is hot, there's a large library of gems to pull from, and Ruby is a relatively easy and forgiving language to learn.

I'm able to pick up just about anything, though I wouldn't call myself a stellar developer by any means. With this I focused on the front-end, and had some local help build out the back end. 

But my help has been part-time, so when I hit a blocking issue, I have to work on something else until that issue gets resolved. More often than not, I set the project aside and work on something else until stuff is resolved. 

Currently I have a problem where the performance is so bad for some reason that it simply isn't worth my time to code against it. 

Now, I could try to become a Rails expert, but there's something about the shorthand that turns me off for some reason. Digging into someone else's code isn't fun either, especially the next time they get into it and see the mess you've made :)

This is the problem of not having a co-founder. It's also the problem of not choosing a platform I'm personally comfortable with. Over the past few months I've learned Node, which allows me to code in JavaScript up and down the stack. When I have an issue, I'm not blocking on anyone else and can solve things pretty quickly.

I don't know what the lesson is here. I don't think Rails was a mistake, per se, and perhaps I should have taken the time to just learn it very well. Or perhaps I should have found a technical co-founder. Or perhaps I shoulda, woulda, coulda. 

Wrapping up the final beta has taken way too long, and partly it's because of me, lack of resources, and lack of availability of my lead guy, who's a great guy and highly competent, just not highly available. 

But if I choose to continue with this, I might do what a lot of people recommend against: rip and replace, and move the entire thing over to Node. Now that we know what the app is, it might make a lot of sense. 

Or it could be incredibly stupid. :)

So how do you deal with blocking issues?

Comments

Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

The Real Jobs Problem

It's the economy, stupid.  Well, yes, it always has been, if you're in the distortion field of politics.  But whose economy? The pundits, the White House, the Republican candidates all miss the mark. They keep talking about debt, taxes, and monetary policy. None of those things tell the real story behind today's economy.  The Old Economy Keynes was right--in the old economy. Economy gets weak, pump some money into the economy through public works projects, which  1) puts people to work, which  2) boosts the economy and  3) generates new tax revenue, while  4) leaving us with another generation of reliable infrastructure to support  5) more growth (for growth's sake, which is another post).  The Beach Ball Imagine a beach ball, partially deflated to represent a recession. Got it? Now imagine the govt pumping that beach ball back up through sensible public investment (which we haven't seen for decades). The New Economy Same beach ball, same pum