1,997 karma · joined July 18, 2008
Me: http://njclarke.com
My code: http://github.com/norman
My blatherings: http://twitter.com/compay
[ my public key: https://keybase.io/compay; my proof: https://keybase.io/compay/sigs/5ghM6xDeYY3U9odHk-2BOd7DxA9AIP5-QcWBkrTOgSQ ]
Economically Argentina is very tough, but culturally it's a wonderful place, and my personal attachment to it - despite my many complaints - transcends money and perhaps even logic.
Chile is a wonderful country with many things going for it, but it's not like it's paradise, and not everybody wants to live there.
Of course you still need some centralization in order to share work with other people. But the more compelling thing about Github is forking, not centralization. With Git you can easily synchronize commits between multiple remote repositories.
>> No one is taking a tone with you.
> Oh, the irony.
Condescendingly telling someone "nobody is taking a tone with you." That's the irony you're missing.
The OP's complaint was presented in a reasonable tone of voice, was articulate and carefully worded. Now, it may be that he has misunderstood something about Stack Overflow, or that he's looking for something the site doesn't provide. But, the OP does not come off as an idiot or a troll.
Your response to "read the FAQ" treats him as if he were a fool (the exact word you used in another reply). It was also so hastily typed, that you misspelled "ask" as "as" and you obviously cared so little about your writing, that you didn't notice this and go back to redit your comment and fix it.
So to sum up: somebody posts a carefully worded, slightly angry but non-offensive complaint, and you rapidly dash off a short, typo-ridden response telling him to read the FAQ.
In other replies to the same user, you put words in his mouth and beat him up like a straw man. You come off as an angry, petulant, mean-spirited and unreasonable person.
In other words, condescending.
> Read the FAQ.
Your response seems to be a a perfect demonstration of what he's complaining about.
Personally, I'm not going to buy one because of the caché of owning something amazingly innovative, I'm going to buy one because I think it will be useful. I don't own an iPad yet because I was waiting for one with the retina display, and I know a few other people who've done the same. Seems to me Apple gauged the market pretty well with this release.
I do hope, however, that the developers there continue to play a role in the project. Just "dumping" a product into the open source world without continuing to contribute to it can kill a product almost as effectively as shuttering it with no source release.
In my experience a lot of developers solve problems using HTML that could be better solved with CSS and a sprinkling of Javascript, because they don't know the DOM or CSS well enough. I think that's what most often leads to the situation you described.
The point is not to completely avoid using their naming scheme - the point is to avoid unnecessarily depending on it throughout all your HTML files, when you can easily isolate the dependency to a single Less file.
If you're using something like Less or SCSS, there is almost no need at all to depend on the class names, you can use them or not use them as you see fit. We wrote the article because a lot of people are not aware they have a choice.
True perhaps, but that's because lots of people write poor-quality HTML. By following best practices like this, it becomes much less necessary to overhaul your HTML during a design change.
http://njclarke.com/posts/why-i-quit-my-job-to-work-on-open-...
I never wrote a follow up to it, I guess in part because I'm still not sure exactly what I got out of it. I certainly improved a lot as a programmer - I'd say I worked harder on programming than at any time in my life, and doing almost all of my work in public held me to a higher standard than what I was used to. I spoke at several conferences and managed to get over my fear of public speaking, which was another goal of mine.
Most importantly, I also got to be a lot more present in my 1-year old son's life for that time, which I will never regret.
It did however take a big toll on my family financially, and I can't help coming away with the feeling that there are ways I may have accomplished those same goals without having gone to the extreme of sacrificing almost all income. I'm almost 40 now and given the historic ageism in our profession I worry a little about the kinds of jobs that will remain open to me over the next 20 years.
Anyway I think that if you're at the point in your life where you have enough money to satisfy the kind of lifestyle you want to live, but don't have the responsibility of a spouse and children, then absolutely go for it.
I saw this firsthand in Seattle when the Sonics left for Oklahoma City. Several of my friends who were lifelong fans swore they would never watch NBA basketball again and became hardcore MLS (Major League Soccer) fans.
Almost every HTML5 demo I've seen just reproduces something we could already to with technologies that ran on the desktop years ago. We're supposed to be excited that we can now implement - barely, and extremely laboriously, and with a clunky, buggy, incompatibility-ridden toolkit - the same kinds of things desktop apps programmers have been doing for a long time.
As a web developer pushing 40, I dread seeing our profession head towards making desktop-style apps in the browser, and along way spending the next 10 years repeating the mistakes and relearning the lessons of current desktop app developers. I'm not sure I've got enough time left to stomach that.
https://github.com/keplerproject/luacov/blob/master/src/luac...
The fact that you applied at 50 places is a bit of a deceptive statistic, because first of all, there's no way you carefully crafted your initial contact to each one.
At each of the places I contacted during my job search, my initial email was very carefully worded. I spent about 3 hours writing and revising one fairly short email, to make sure it conveyed exactly what I wanted.
If you just send a generic form letter to a company, they're going to give you the same consideration you have given them: very little.
Even if you did tailor the email to each company, there's no way you as a candidate are going to appeal to more than a handful of the companies, because they all have their own quirks and cultures. NOBODY is a viable candidate for 50 different Ruby-oriented companies.
Also, no offense but I have to concur with other comments here that your writing may have had something to do with it. If what you sent them was worded at all like what you've posted here, then you probably lost a lot of potential responses because of that.
If you want to get your foot in the door at a company, the first impression you make is everything. Sending a poorly worded email is a surefire way to shoot yourself in the foot.