Skip to main content

What happened to sharing work with other developers?

There was a time when you could create something interesting and post it to a forum with programmers and actually get people interested in what you have. These days it seems short of being blessed (exactly by whom, only god knows) on HackerNews there is little chance you can get anyone's attention.

It is difficult to say precisely what the issue is because it seems multifaceted. It appears a combination of the rise of GateKeepers, perhaps cynicism inspired by the rise of GateKeepers and just a general overload of information has coalesced into a very difficult situation for those of us still daring to create without a VC backed turbo to charge forward with.

Over the past 5-8 yrs I have become quite dishearten by this loss of a genuinely curios developer community, or maybe I am just an old (36) fart who's been left behind.

Even tenure in certain communities doesn't count for anything anymore. I have been a member of HackerNews for 8.5 yrs and have only had 3 or 4 of my postings ever make it to the front page. HackerNews claims to have an "algortihm" for their stuff, I call bullshit on that.

I yearn for the days when all one needed to do was something like this or this or this in order to build credibility...ok maybe I really am an old fart, have yet to make it to digg.

I believe it is not just a matter of a different time but rather a real change in the nature of collaboration/interaction channels. When I used to post to a site like CodeProject I didn't need to know people who could somehow make or break the discovery of my contribution, people simply discovered your work and voted it up or down based on whether it was good or not. Today you can setup a GitHub repo but unless you're part of some clique, serendipitous discovery is almost impossible. GitHub,HackNews, ProductHunt, TechCrunch..etc, these are all GateKeeper entities masquerading as open discovery platforms. All of these platforms function based on social graphs (implicit and explicit), unless you have the right cachet within some circles you're out of luck.

Even with the "open" platforms and products that appear to thrive organically, when you take a closer look you see that there are often puppeteers behind the scene pulling strings.

Anyway, this is a rant, more might come. I'll now post this to HackerNews and watch it get thoroughly ignored :)


Popular posts from this blog

Managing configurations with object graphs

This post is basically a pitch I send to folks whom I think will be interested in a modern approach to configuration management. I am posting it here so I can refer people to it without sending them a long email.

One of the features of the Solvent (formerly HiveMind) platform is a smart object technology that solves the problem of dealing with hierarchical configuration information often represented in formats Like YAML,JSON, Java Properties,XML...etc

The smart object technology allows developers/users to directly construct object graphs of any complexity. Once you have the actual object graph you can reverse the process back to representation in any one of the formats mentioned above.

I have setup a demo instance for trying it out @

Login with login info I sent you.

Be nice, you have full system access :)

To see an example representing the AWS IP list (

Navigate to: /com/crudzilla/betaApp/we…

Your code is not a project

Language matters, just as saying the wrong word to the wrong person can leave you with one less front tooth, so too can the incorrect use of language in general create a cascade of confusion that pervades an entire industry.

One of my pet peeves about the use of language in the software arena is the use of the word "Project". This usage as far as I know goes back to IDEs grouping software artifacts as projects. The notion of a project as the top level organizing construct for software projects (see what I did there?) is now a de facto standard. One problem with this is that it is a complete misuse of the notion of a project. A project is not a thing, it is a process! A project has (or at least should have) a well defined start and end.

As a process, by its very nature, its essence is vague. So when something whose essence is precise (software) is called a project it leaves the reader wondering exactly what is being described. Whenever I come across a documentation describing…