|French interactive design studio, with a nicely done website.|
|Connect with potential team members, investors, beta testers and early adopters (well done Gerben).|
|A hand-picked directory of the best free resources for creatives..|
|A curated list of awesome MySQL software, libraries and resources.|
|Erlang in anger|
|(ebook) free little guide about how to be the Erlang medic in a time of war.|
|Yet another role-based authorization system for Rails.|
|Universal Ruby Test Framework.|
|A library for manipulating nested collections in Ruby.|
|Smoke is a jQuery Plugin library designed for use with Bootstrap 3.|
|Easy to use web application framework for writing scalable web APIs in C.|
|Free Network Analyzer Tools for MySQL and PostgreSQL|
|Like tcpdump but database focused.|
|Processor in ruby for a DSL that outputs to the Terraform specification format.|
|Creates RPM, Deb and tarball packages using shell script.|
|A New Way to Understand Your Rails App’s Performance||may 11|
|About mini-profiler and flamegraph.|
|My solution to #5 Software Engineer challenge||may 11|
|Apparently every Software Engineer should be able to solve this in less than 1 hour.|
|How Ruby Uses Memory||may 11|
|Why memory use goes up or down as your code executes.|
|More Inspections||may 12|
|Introduce inspect options in irb.|
|The At-Rules of CSS||may 12|
|The at-rule is where it's at for making CSS do some crazy and interesting things.|
|Rails: Don’t “pluck” Unnecessarily||may 13|
|`pluck` can lead to multi query unnecessarily.|
|Mega Dropdown||may 13|
|A responsive and easy to customize mega-dropdown component.|
|Experimental MySQL HTTP API and Ruby||may 14|
|MySQL 5.7 ships it's experimental HTTP API for SQL/CRUD/JSON endpoints.|
|Two alternative libraries that allow you to perform Ajax requests.|
|Responsive Images with WURFL Image Tailor||may 14|
|When it comes to images and mobile devices, there is a lot more to consider.|
|Speed Up Your Rails Views By Deferring Changes||may 15|
|Building a Slack slash command with Sinatra, Finch and Heroku||may 15|
|Registering a slash command with local sinatra application.|
|Test Incoming Webhook Requests with Faraday||may 15|
|A trick to simulate external webhooks in your test suite.|
|How To Write Ruby Faster at the Source Code Level||may 16|
|Performance boosts by using another method(s) to achieve the same goal.|
|Gorails 55 (19m)||may 15|
|My Development Environment|
There is something that I always did in my career managing internet tools. I volunteer helping non-technical people to get a presence online, build up communities and such things. But I have to confess, this comes with a price. A price on your nerves when you realize that easy obvious things that you take for granted are actually not clear at all by the average Joe.
Yeah sure they can post of facebook. For many of them, it's pretty much all what internet means. But for the real things, they have no clue what they are doing. Talk about the merits of a chaos money to test your infrastructure. Well, the man on the street is pretty much the best you can get when it comes to chaos testing your design and workflow.
But whatever infuriating it can be, it's a great thing to keep in mind. People have no clue what they are doing. They don't know what an url is. They think smileys are fun. They feel writing all in capitals is just a detail. When some popup appears they consider it's all broken and there is no need to read what's written on it because anyways that's over their heads.
So, when you design your applications, you may be lucky enough to face an educated population. But in many cases, you may not. Take it in account. Make things over-explicit and use images to bypass the inability of the modern average people to read anything that is more than a sentence of 5 words.
Go volunteer to help your fellow neighbors in your local non-tech communities. It's hard, but it helps keep in touch with the reality.
And above all, keep patience. It's not their fault. There has never been any economical incentive to educate users. The shortest path is always the best path. So for sure, you should make things easy. But if you get any occasion to provide your users some education, it's never going to be on your spec sheets. You can do it as a natural thing to do. Add optional text to explain why things are the way they are. Few will read it, but they will learn from it.