Skip to main content

What's Buggin' Me on a Blue-Sky Day

It's a beautiful blue-sky day here in Lancaster, and I have plans to shop at market then head to the gardens to get in a late fall planting.

But I ran into some bugs over the past two days after upgrading every component in my node stack. Of course.

The one thing about open source is that while the source might be open, you really have to pay attention to the discussions and updates--at least in the case of Express.js--to track changes. The primary author is incredibly smart, but he's also highly opinionated about what makes good programming and good programming languages.

It seems as though he's constantly trying to optimize, which is great. But after looking at the migration docs for Express 2.x to 3.x, I'm pretty certain he's not optimizing for the developers who have built dependencies on the earlier versions.

In particular, it appears as though he's ditching partials in favor of includes and mixins. And I'm not going to get into that, but I can see I'm either going to have to stay with the current versions of  all modules I'm using--because each module will likely be improved or adapted to 3.x--or I'm going to have to rip and replace code.

I'm not a great coder. I hate configuring stuff more than once, and am not a real fan of having to worry about the dependencies. This reminds me a bit of Microsoft in the 90's, when it would break APIs in software updates, rendering thousands of applications unusable until a patch came out.

It's different, but the effect is the same.

So this morning I got things running again. I'm not sure where it broke down exactly, but I cleaned some things up and it's fine.

Except that it also made me wonder why I'm bothering at all.

I'm passionate about the work I'm doing, but I'd rather manage developers toward a product vision than develop the product myself, for exactly the reasons you can see above.

I was sick most of the week. Most of the week sported blue-sky days like today, and I missed those mostly, too.
today at 11:20
I'm not going to miss more of today futzing around with the app, and will save it for rainy days and nights.

It's time for me to get back to running something.

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