Posts Tagged ‘open source’

Open Source key to defeating Lemon Markets

Sunday, March 16th, 2008

I just sent this to a potential development partner who cold-emailed me about helping out with additional RoR work:

Hi XXXX,

Can you point to me an example of your Ruby on Rails work, including source code + how much time / how much $$ you charged to have it developed.

Thanks,

- Shanti

The problem is, I’m guessing here, 75% or more of dev shops would laugh at you in the face with this kind of request.

Why? Because they are ashamed to actually have other developers look at their code, warts & all.

Blog Comment Autofill

Thursday, January 31st, 2008

My Blog Comment Autofill Greasemonkey script is back.

In its first incarnation, you’d be on Digg, reddit, etc and the script would actually fill in your blog’s URL into the submission field!

Now, I check the meta generator tag, i.e. if you view source on this page you’ll see something like this in the header:

<meta name=”generator” content=”WordPress 2.3.2″ />

Typepad is also supported. Blogger has a bollocks commenting system, so this script will not work with Blogger blogs.

The Open Source Itch

This script was born because it was simply maddening to have to retype my details every time I wanted to post a quick blurb in a blog comment.

That’s why many open source projects start out as hacks and only gradually morph into more sophisticated projects.

The Benefits of Releasing Software as Open Source

Friday, January 4th, 2008

Just came across this post which talks about automating Facebook interaction to perform a request in a Facebook app.

Their ruby code is here (much of it based originally off mine — which is so cool).

For the longest time I didn’t get open source… why anyone would give away their hard-earned time (in the form of code) to everyone else.

It’s not some hippie thing though. The benefits are:

* expands your “street cred” in the community
* allows other people to enhance what you’ve done, and possibly, contribute back to the project
* fosters even more giving back by growing pie — it’s not a zero-sum game, as many would believe

In my case, I’ve almost always already written the software that becomes open source. Without releasing it, the code would simply rot on the vine. Usually within 2-3 hours (though I’m getting better), I can have the code cleaned up, tests added (if applicable) and released as an open source project.

The original Facebook automation article is here: HOW TO: Automate Facebook Interaction using Ruby and WWW::Mechanize.

More recent open source work: Sexy Temp Passwords (rails plugin), Dynamic File Store (rails plugin), and The Hydra Project.


Shanti A. Braford blogs here.

If you really want to know, just read this.



  

Powered by FeedBlitz