Compelling job specs

The quest for the Holy Grail A job spec that developers relate to is a rare sight. I was chatting with an acquaintance that works in the recruiting space, about the never-ending battle between good an evil that is the relationship between recruiters and developers. The conversation got interesting when he said this: I am not sure our job specs are very good. At that point, I had a fleeting recollection that while on Twitter, I stumbled on the Zapier jobs page.

React on Phoenix

Phoenix’s author Chris McCord decided that instead of implementing a brand new pipeline for JavaScript and CSS, it was wiser to rely on existing tools. Specifically, Brunch was chosen. An advantage of this is that using React with ES6 and JSX is dead easy, as Babel is already available for us. In your Phoenix project’s directory install the Node modules you’ll need: $ npm install --save react react-dom babel-preset-react Change brunch-config.

Recruiters vs Devs: The Eternal Struggle

A sour relationship The relationship between developers and recruiters is not an easy one. For developers, recruiters are mostly a pain in the back, bothering them at all times of the day in order to offer jobs completely irrelevant to any goal a developer has in their career. For recruiters, developers end up being a bunch of spoiled kids who whine about job postings and bash recruiters (privately and publicly) because it builds camaraderie.

Trying out Elm

I’ve been out of the front-end game for a while, and decided to dip my toes back again after roughly 2 years of little-to-none JavaScript. So many things happened in the meanwhile! React, Redux, Flux, Om… What should I use to get back on track? As I’ve been dabbling a lot in Elixir and Phoenix space, I saw in the community a growing interest for Elm, a functional language that compiles to JavaScript.