thetabyte
Joined 15 years ago
Joined 15 years ago
This may also have the side effect of allowing for some opinions to be shared, without being mired in flame-y back and forth. (And, importantly, still allows the story to stay more visible)
I tend to have a lot of respect for pg, and found his apology for what happened in that thread to be admirable. Whether or not preventing discussion of the issue on HN is positive or negative...I have very complex feelings on the issue, and see valid arguments on both sides.
What I do not have mixed feelings about, however, is that these issues need to be put front and center, so that people in our industry a) know they exist b) know how common they are c) are inspired to make personal effort to fix it. I would hope that pg agrees.
If he does, why not make such stories, when they set off the flamewar detector, maintain their ranking, but disable comments? That way, the issue is still raised, and people are still alerted to it, but it prevents the (some believe) "unproductive" discussion.
Then they came for the socialists, and I didn't speak out because I wasn't a socialist.
Then they came for the trade unionists, and I didn't speak out because I wasn't a trade unionist.
Then they came for me, and there was no one left to speak for me."
-- Martin Niemöller, 1946
Because if so, please, run, I'd like to see it happen.
By pitiful, I meant that this shutdown seems minuscule among the variety of other privacy violations—but that hardly justifies the Guardian using this specific reveal as an attack piece.
Like many people here, I agree that there is nothing more important than building things that you can show people. However, the process of getting to that level of capability can often be somewhat mystifying. There are a few tools I recommend for that. First of all, interactive tutorials, like those at Code School, are fantastic introductions to web frameworks, if you're just getting started. I first learned Ruby on Rails with Rails for Zombies. However, these tutorials will not give you the skills to actually build anything—rather, they are a good primer. From there, find a good book, preferably one that focuses on actually building something, like Michael Hartl's Rails Tutorial. Finally, I really love to use screencasts (a la Railscasts) for picking up domain specific information for particular tasks. Hope that helps!
Second, a relevant question:
I've just recently started freelancing myself, and I see a variety of advice. "No Rails developer should make under $75/hour!", "Take what you can get, work your way up slowly!" "You probably charge too little!", etc. How do you actually evaluate how much your skills are worth as a freelancer? How do you match with clients who need and are willing to pay for your particular skill level? If anyone has any links to relevant advice, those would be great to.