|70th anniversary of the outbreak of the Warsaw Rising.|
|Is it vulnerable?|
|Check if your ruby project vulnerable by uploading Gemfile.lock|
|Big List of Naughty Strings|
|List of strings which have a high probability of causing issues when used as user-input data.|
|Web based calculator using math.js.|
|Become a Programmer|
|Collection of resources to become a programmer.|
|Scan the HTTP security headers of websites.|
|Efficient Rails DevOps|
|(book) successor of 'Build Your own Rails Server'.|
|Designing for Performance|
|(book) Weighing Aesthetics and Speed.|
|Rails 4.2.4.rc1 and 4.1.13.rc1|
|If you feel like living on the edge.|
|A factory to produce FactoryGirl templates.|
|Get IDs or screen names from links to social network accounts.|
|Tool that automatically formats CSS source code, inspired by Gofmt.|
|Standalone AngularJS module that provides growl-style alerts and messages.|
|The new recommended way to get started with Docker on win and mac.|
|How widely used are security based HTTP response headers?||aug 9|
|There is a bunch of security dialog happening in a HTTP request and response.|
|Non-Rails Frameworks in Ruby: Cuba, Sinatra, Padrino, Lotus||aug 10|
|A comprehensive comparison by route, model, controller, and view.|
|How To Time Travel Using ActiveSupport TimeHelpers||aug 10|
|Use built-in travel method in Rails 4.1 to do simple time traveling instead of Timecop.|
|Using lazy enumerators to work with large files in Ruby||aug 10|
|The lazy magic in ruby enumerators.|
|Announcing Rails Rumble 2015||aug 11|
|This year rumble will happen on nov 7-8. Get ready.|
|Testing Hubot Scripts||aug 11|
|Various testing cases and a couple pitfalls while building Hubot tests.|
|What it’s like to come back to a Ruby project after 6 months||aug 11|
|We've all been there before...|
|It can be nice to localize the time for the reader.|
|How to Improve Loading Time with basket.js||aug 12|
|Running three hours of Ruby tests in under three minutes||aug 13|
|How Stripe do distributed testing.|
|The Pathway for New Railists||aug 13|
|A guide for you to start your journey with Rails.|
|Understanding Critical CSS||aug 13|
|The web is slow, yet there are a few simple strategies to make websites faster.|
|Responsive Design Is Not Enough, We Need Responsive Performance||aug 14|
|Responsive Design with Graceful Improvement.|
|Build a Real-Time Status Update App with AngularJS & Firebase||aug 14|
|Firebase is a realtime data store that makes it very easy to save and sync data across any platform.|
|Strategies for Cache-Busting CSS||aug 14|
|Strategies for breaking the cache and forcing the browser to download a new copy of the CSS.|
|RustCamp 2015 (9 videos)||aug 14|
|Get to know Rust a bit.|
The ruby community is quite blessed in the way that there are very vocal activist promoting diversity, especially on gender parity. It's not exclusive to ruby I noticed the same intention in other communities (like the pyladies in python).
Anybody that spent some years in IT cannot avoid to notice that there are mostly guys. The ladies are either frowned upon or very special cases. For ages I have been wondering why. My sister is a sysadmin at a university, there is nothing shocking about that and she does a damn good job.
So I paid attention on what are the people responsible for that. I identified various categories of people that I consider are responsible of our lack of parity. Well, not them directly but the behaviors they perpetuate are certainly part of the problem. If we could find a way to correct those behaviors, it would lead to a natural change in the group.
In all those people I know, and in all their behaviors, I think I detected something that is related to the Religion Of Competitiveness. Those people are believers that knowledge is power and they are not gonna share it more than necessary. They will find anything to avoid more people reach their level of knowledge. And if they can find some kind of reason to discard other people, either trivial and socially acceptable in the given group reason to discard other people, they will do. Gender is the first victim in such a schema. What is socially acceptable is a self-perpetuated meme.
Talking to those people is pointless, they are in denial. They see nothing wrong. You can't change them. You have to change their environment, that will be the only way.
So it means that in a competition context, there are still ways to win, by playing the competition game and winning it. But to break the competition paradigm, there is a lot to do. Companies policies are not enough to enforce a more open mindset. But I believe that there is ways to organize the information in a way that keeping it for oneself devaluates it. And from the eradication of the tyranny of knowledge, we shall reach a less competition-based culture in IT. And all discrimination pretexts may vanish by themselves.
Rather than fighting for diversity, we should fight against the spirit of competition. It's kind of not easy, I reckon, because our society tends to push people to be competitive. That's what capitalism is all about. But IT population already has proven that the established system don't take hold on them. Geeks and techies are educated people (often self-educated, but it's the same) and they can think on their own, chose the path to follow. If you can find a way, in your context, to change the environment towards less power for the competitive type of people, that could deserve a try.
Well, that's just a rant, a wild thought. Such a topic would deserve more space for development. But that's what I wanted to share this week. Anyways I doubt there is that much people reading those line hahaha.