#177 - jun 26th 2016


Examples of UI/UX, graphic performance, web design and flashy things.
MockupEditor design
Create instant mockups of your scene.


Web applications, resources and tools, available for making our life easier or funnier.
Remotely Awesome web
Remote jobs aggregation website.
Jobspresso web
JFind remote jobs and careers.
Authentic Jobs web
Web, Design, Freelance, and Tech Jobs.
Upwork web
Get Freelance Jobs Online.
Dr. Jekyll's Themes design
A Jaekyll theme directory.
Git-tips tool
Most commonly used git tips and tricks.
PG Casts tool
PostgreSQL screencasts from the people at Hashrocket.
2016 State of DevOps Report ops
The annual Puppet report with data about devops.


A selection of gems or applications updated during past week.
Ruby 2.4.0-preview1 jun 20 rb
Many features improvement, they say.
Rails 5.0.0.rc2 jun 24 rb
Details of the last RC release for Rails 5.
Groupify rb
Add group and membership functionality to your Rails models.
Action_access rb
Access control system for Ruby on Rails.
Iris go
A fast web framework in Go.
Elixir 1.3 jun 21 el
Various fixes and new evolutions.
Verk el
A job processing system that just verks!
Places js
Turn any input into an address autocomplete


From the blogosphere or news feeds ...
About controlling the Referer header jun 20 web
Everything you could ever want to know (and more) about controlling the Referer header.
Redesign Hacker News jun 20 design
The 5 areas to improve, how and why.
A Review Of Immutability In Ruby jun 21 rb
Options available to Rubyists regarding immutability.
Content Jumping (and How To Avoid It) jun 21 css3
One of the more eye-twinging behaviors of web sites and some possibilities.
Behavior changes in Ruby 2.4 jun 22 rb
Changes that are not entirely backward compatible.
Liberate Your Search in Rails with Tags jun 23 rb
How to take a complicated search model and open it up with tags.
Getting Started with Hapi.js jun 23 js
An alternative to express.js.
Understanding Elixir's Ecto Querying DSL jun 24 el
Basics of querying with Elixir's Ecto library, going through joins, associations, aggregation functions, and so on.
10 benefits of Code Review for the win jun 24 tool
Problem: People make mistakes.
The shape of open source jun 24 web
At its core, open source is about collaboration. Here are some graphs.
Ruby script to achieve fast incremental back-up on btrfs partition jun 24 ops
The script and the details about it.


Screencasts and conferences videos, or other video feeds ...
Drifting Ruby #34 (3m) jun 19 rb
Some neat tips and tricks for interacting with and parsing JSON responses from an API.
Links curated by mose (publisher), mose (editors), lincoln, tysliu, nauman (contributors) .


The random rant of the week by mose.

Remote working

For some random strange reason I had a lot of links this week about remote working websites. I know it's a very real topic for our craft. But I still see a lot of companies that have hard time coping with the concept.

On one hand, there is a shortage of technically skilled staff. The growth of the tech industry and especially the online services is way too fast for the education system to catch up. It's been like that for pretty much 20 years now. And there is an unbalanced repartition between where the growing companies are and where the growing population of techies are. So it would only make sense that either relocation would be much easier or remote working much more widespread, no? Well, no. Relocation is bound to laws that are not driven by the only technical area. And remoting is dependent on a cultural and also legal shift.

Because working with remote staff, many of us know what it means. First it involves a level of trust in the staff that is unprecedented. The same level of trust you need to invest when working with a contractor, actually. Then the old-fashioned control and command system in place with traditional management systems gets totally inefficient.

More even, to be efficient with a remote team means adopting a work organization and tools that are specifically thought for this setup. From what I can experience, it's either one or the other. When half the staff works in an office locally it's not easy (yet not impossible) to be efficient with another half remote.

Some stuff will be likely to happen locally with old ways of oral communication and meetings with sparse note-taking. That will put the remote staff in the dark of some parts of the internal process. It may create a double-speed kind of organization, there is the ones that are full speed and the ones that are just, well, not in the core. Oh it's still possible to make it work. It's just harder.

Or maybe it's like the web and the mobile. Slowly companies need to become remote-first and then eventually also work on local office-based scale. But there are still various barriers for having a real remote-friendly world anyways. The legal status is not clear,m for example, money transfers between countries, compliances with social coverage conventions, no international law seems to cover international employment with individuals.

From what I can understand, remote working from a distant country is still a hack, legally speaking. Companies need to find tricks. Luckily, hacking is something we are not bad at. But still. I wonder when it's going to change, and see a legal ground for a really normal remote working context.

Green Ruby News was a feed of fresh links of the week about ruby, javascript, webdev, devops, collected by mose, xenor and tysliu every sunday.