Bēhance Dev Links Issue 01

World cup results for hackers. Uses Soccer For Good API

Nothing like getting sports scores and info in your Terminal!

worldcup

submitted by Rachel White


JS NICE

“Statistical Renaming, Type Inference and Deobfuscation”

Nice!

submitted by Joe Sepi


Create a TV Show Tracker using AngularJS, Node.js and MongoDB

An introduction to full-stack javascript development that uses express on the backend, mongodb for data storage, and AngularJS on the client.

submitted by Sean Dunn


Colorize log files on CentOS and Ubuntu using ccze tool

Even though you might be using centralized logging tools like Splunk, Logstash, or Sumologic, occasionally you just want to go in and tail a log yourself. Ccze is an awesome, custom-color formatting tool that makes the arduous task of reading/searching through logs a little more pleasant.

Example-using-ccze-tool

submitted by Malcolm Jones Read more →

Deployment with Scarlett ( Hubot + HipChat + Nodejs + CoffeScript + Phing )

Clase Premier / Scarlett Johansson by César Moreno on Behance

Clase Premier / Scarlett Johansson by César Moreno on Behance

Here at Behance, we deploy a lot of code, very VERY frequently. We are constantly adding new features to our applications, hotfixing bugs, and changing things to give everyone a better user experience.

The Problem:

Currently, we have 3 operations engineers who have the credentials to build our applications to our pre-production and production environments ( Myself, Ko Uchiyama, and Chris Henry ). If none of us are available for whatever reason, changes don’t get pushed. At the same time, if we ARE available, on a really bad deployment day we can receive anywhere from 12-30 requests to push changes which can REALLY interrupt our work flow or weekend ( Especially mine since I’ve become the “main build engineer guy” lately). How can we make this workflow better?

The Solution:

Build a robot to do it for you! Duh.

Read more →

Introducing the Behance API

On behalf of the Behance Team, I’m proud to announce the opening of our public API and developer site: http://be.net/dev. We’ve been internally using a private API for well over a year now, creating our own portfolio website builder, ProSite. With this second version, we’re making it public: the developer community can showcase Behance’s sorted, curated and appreciated work in their own experiences.

Read more →