lundi 19 mars 2012

jsFiddle and the GitHub integration disappointment

So the first "contentful" post of this blog will be about failure. Not the kind that comes before great achievement (although we never know...), but where the best achievement you can hope for is just acknowledging you need to stop trying.

A few days ago, I discovered jsFiddle, played a bit with it, found it great, got excited, browsed the doc, and found they provided a GitHub integration. I was starting to consider dropping Eclipse and using this new Web EDI, pretty raw but just fitting my needs, for my JavaScript work, hoping that, by some kind of black magic, I could commit my work from there to my GitHub repository and still be able to organize my project the way I wanted.

As it turned out, not only can't I commit anything from jsFiddle to GitHub, but the worst disappointment was to realize that they don't keep their word of adapting your JS project structure through a kind of manifest file. After a few unfortunate tries, I am now convinced you really need to make a silly directory with 4 files immutably named demo.ext. There is no way to follow my code's evolution in jsFiddle but to copy it as it evolves in this demo.js file the way I would in the jsFiddle window, or any other homemade page. So much for added value...

If you happen to nourish the same expectations I had a few hours ago, drop it. So far, jsFiddle just carries out the duties of a JS/CSS sandbox, the way the "W3schools Try it yourself" and a million others already met, with a few handy improvements such as saving your code or loading JS frameworks with a select box instead of a code html tag. Cute but disappointing.

This is a temporary blog

Progress is made out of trial and elimination of error. Even if, unlike me, you don't believe this sentence to be the one and only definition for the word "progress", I think you will agree there are few activities where it is more undeniable than in the developper's one. And the fact is, these last times, I must be progressing a lot, because I'm meeting a lot of errors.

This blog is just what it says it is : a stack on which I will negligently throw my programming experience as I live it, just to not forget it until I find enough time to build a true, beautiful, innovative, responsive, WordPress-powered, show-off portfolio. I am vaguely hoping to achieve a few of these embarrassingly unoriginal goals :
- avoid duplication of the debugging effiort : maybe my struggles with the things I try can save a few guys out there some hours making the same silly mistakes I made ;
- improve my english writing skills : though I would already have absolutely no time to write this in my beloved mother language, I'll spend some extra writing my first blog in English ever.

A few words about me : I am 25 years old, currently working as a Java/J2EE developer and back-office version manager for an outsourcing project in one of the biggest French IT services company, called Sopra Group. I am currently spending what is left of my precious spare-time on a personal project of a Web project management application, using Grails, to meet some work needs today poorly fulfilled by good old Excel spreadsheets, but essentially to discover the framework and the language. From there, I am starting a subproject aiming to build a visual and dynamic team-schedule manager as a jQuery widget, for which I am seriously considering using CoffeeScript.

To put it shortly : this is yet another nerdy blog, but hopefully this one won't last.