4 ms·
Feedback -- not of the 'comments and criticism' variety. Think of any successful project like a nuclear chain reaction. If you are not familiar with nuclei, so
by drostie 14y ago
Feedback -- not of the 'comments and criticism' variety.
Think of any successful project like a nuclear chain reaction. If you are not familiar with nuclei, some of them are "too heavy" and want to fall apart, spraying neutrons everywhere; they especially do this when they get absorb an extra neutron flying around, but quantum mechanics always gives you a spare neutron eventually.
The system transitions from negative feedback (no chain reaction) to positive feedback (chain reaction) according to a very simple principle: the number of free neutrons that a free neutron creates (call it N) must be more than one. (N=1 is the replacement rate; it's a metastable state of reaction. If you like, the reason why some nuclear reactors have been risky is that horrible accidents kill the safeguards which are simply designed to force N ≤ 1.)
This principle is so fundamental -- it's why there's a 'meme' analogue to the 'genes' in the modern theory of evolution, why countries become bureaucracies, and why nuclear reactors are hard -- that I hope everyone working in startups starts thinking about their products this way. It's not signups which you need to have a successful product. It's that every free customer must convert, on average, greater than or equal to one new free customer. Even if you cannot get all the way to one, you boost your marketing effects by a factor of 1/(1 - N), so if you can increase N from converting 0.25 people per person to 0.30 people per person, it's as good as spending 10% more on marketing.
And it applies, yes, to any open-source project too. The open-source projects which succeed are those which help hackers to help those projects, just like the genes which succeed are the ones which help their species to spread that gene. I'm not even sure that this particular project is open-source. (I believe it falls into a special case where the GPL is used as a closed-source license. That is, GPL requires me to provide a copy of the source code when I distribute the code -- but I do not have the source code, and I cannot coerce the author into giving it to me, so I am not actually free to distribute the binary either until they give me permission to do so one way or another.) The author's claimed reason for not providing a way to "Fork me on GitHub" is, "I have not made a major effort to put its code on any of the open source repositories as it does not currently seem the right thing to do. Just not worth the effort." And that's probably the deepest reason why it's fallen into neglect.
- klibertp 14y agoYes, I found this bit about not setting up a public repository strange, too, but the reason there is no "Fork me on GitHub" seems to be just that the project predates Github by a year :) You're hinting at licensing as (one of) a reason that this project was abandoned, but I think the author just wasn't sure what to do with his code - I think he wanted to get some money out of the project and didn't know or couldn't decide how to do it. If enough users told him they wanted the source, I think he would comply - it's just that there never was enough users (seems so). Your analysis is interesting and a good one (thanks!), but it doesn't answer the more fundamental question: why the project failed to get another user out from every user it already had? That's assuming somebody was actually using ODB - maybe it failed at even lower level: everyone said it's cool and stuff, but nobody really gave it a chance and actually started using it. I'd like to know which one it is and why? If something like this was available for Python (btw: is there something similar?) I think I would use it instead of ipdb without hesitation (assuming that I would know about it). From what the author writes he did his best to inform the Java world about his and his project existence. So why aren't we all using this and similar tools today? I think this can be an interesting case for every developer who wants to change something with his software. This debugger failed; LightTable seems to have a high chance of succeeding - what's the difference between them? (Not having Bret Victor talks as an inspiration seems an obvious one :))