[ojbyrne]

I have also been developing software for a long time. What I learned at digg is that technical debt matters more, and becomes more of an immediate problem, if you grow insanely. If you have a 100 sympathetic people using your app, it doesn't really matter if there's a few rough edges in it. If you go from 100 sympathetic people to a million or so in six months, you go from "work on it as you can" to "we will be screwed if its not fixed immediately."

Even more so, if you end up being an acquisition target for companies like Google and Yahoo (who want to read your code), then it becomes "this will cost us hundreds of millions of dollars this week if its not fixed now."

[jshen]

This is a bit of a tangent from the original issue which was about the ability of a non programmer to judge programmers. I still hold that the good ones can, and if they cant then how do you propose they pick their technical cofounder?

Regarding technical debt, I think we're conflating a few things under this umbrella. There can be code that is easy to read and maintain, but won't scale to millions of users. Then there is spaghetti code which is brittle, hard to read and modify, but may or may not scale. I think it's ok to have the first before you know if you need to scale.

When you guys got to the point that you realized it needed to scale was it fixed immediately? If not, would it have been that hard to fix it then.

Btw, thank you for talking about this stuff. It's great to hear insights from someone that's been through such things.

[ojbyrne]

One of the things I learned is that readability is a key part of scalability. One or two programmers can figure it out, but when you get to 20 or 30, if the code isn't clear, it costs time and money. Clever hacks need to go by the wayside, in favor of clear code.

As the saying goes "Always assume that the next guy to maintain your code is a psychopath who knows your address."

That is not something I knew in the early days of digg. I know it now.