Navigating an AMD codebase in Sublime Text using Static Analysis and Node.js

As your JavaScript codebases grow, it can be difficult to stay productive within your editor. Whether you are looking for modules that require the current module or simply trying to hop between dependencies; most tasks related to navigating a large codebase require numerous steps that become tedious and can seriously hinder productivity.

Behance engineer, Joel Kemp, writes about how he used static analysis techniques via Esprima and Node.js to overcome these problems within Sublime Text 3. Check out the post: Navigating an AMD Codebase in Sublime Text.

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 →

Developer’s Toolkit: Mike Sherov

This post is part of a series where Behance developers talk about the various tools they use to get things done and make ideas happen.

noname1. Who are you, and what do you do at Behance?
I’m Mike (and that’s one of my twins, Grant, on my shoulders. Julian’s a bit shy!). I’m primarily a JS engineer, but I also dabble in PHP, Mustache, and SCSS. I guess you’d say I’m a full stack dev who just prefers writing JS. I have a strong passion for testing, deployment, and code quality. I maintain (and contribute to) Behance’s static analysis toolchain: SCSSLint, JSHint, JSCS, PHPCS, and am currently working on centralized logging using Sumologic.
Read more →

Developer’s Toolkit: Rachel White

This post is part of a series where Behance developers talk about the various tools they use to get things done and make ideas happen.

75932_10101210392506118_795298238_n1. Who are you and what do you do at Behance? 

I’m Rachel White, and I’m a Software Engineer. I’m on the JavaScript team and I mostly work on refactoring legacy code to be more up-to-date with new standards we’ve set for ourselves. Sometimes I work on CSS projects and prototyping new ideas for the site, too.

Read more →

Developer’s Toolkit: Mark Dunphy

This post is part of a series where Behance developers talk about the various tools they use to get things done and make ideas happen.

Hello it's Mark!1. Who are you, and what do you do at Behance?

By now you’ve probably already learned my name, so I suppose I won’t go into that. However, I will tell you that I’m a backend software engineer at Behance.  I have the interesting position of floating between teams and products quite frequently, so I get to leave a little Mark (hah, get it?) on everything.  Beyond the sprinkling of love and code I put into other team members’ projects, I’m primarily responsible for Behance emails (notifications, automated digests, switching service providers, you name it) and fighting spam.

Read more →

Developer’s Toolkit: Andrew Crerar

This post is part of a series where Behance developers talk about the various tools they use to get things done and make ideas happen.

andrew 1. Who are you, and what do you do at Behance?
I’m Andrew and I’m responsible for the development and day-to-day operation of our Custom Creative Networks. What is a Custom Creative Network (CCN)? I’m glad you asked! CCN’s are essentially streamlined, thinner versions of Behance but differ in that they have the ability to be customized; really cool stuff. On a normal day you can catch me working the full stack: anything from writing SQL, PHP, or JS, to making CSS changes and going to production (Wooo)!
Read more →

Developer’s Toolkit: Nina Berg

This post is part of a series where Behance developers talk about the various tools they use to get things done and make ideas happen.

ninaberg1. Who are you and what do you do at Behance?

Hey there, I’m Nina Berg, a Quality Engineer here at Behance. Our team’s job is to ensure Behance is as stable and bug-free as possible. To that end, we work on developing whatever tools, infrastructure, and processes are needed to test our website. My recent projects include working on a Selenium testing library called Paige, and designing a continuous integration workflow for the cookbooks our devops team works on.
Read more →

Developer’s Toolkit: Krasimir Georgiev

This post is part of a series where Behance developers talk about the various tools they use to get things done and make ideas happen.

krasWho are you and what do you do at Behance?

Hi there! My name is Krasimir, software engineer here at Behance. I’m part of the backend team and my main responsibility is to break the site and fix it after that (on my first day here Bryan said I could, so I do it from time to time).

My job is to implement new features and improve the old ones. I work on a better way of storing and retrieving the images on Behance. I was also involved in improving the way invites and requests on the site work. The rest of what I do is still under wraps.

I moved to NYC almost 4 years ago and joined Behance about 1 year ago. It’s great to be a part of something that I’ve known and followed for a long time even when I was back in Bulgaria.
Read more →

Moving Data Centers with Chef

Moving data centers is scary, make it less scary with Chef, U-Haul not included.

@mtldo + @cfortier at #chefconf2014

At ChefConf 2014 this year, Chris Fortier and I had the privilege of presenting on the challenges of moving from a physical data center to the cloud. Beyond the move, we had to move towards more automation and a hands off approach to managing servers. This meant learning Amazon Web Services in depth and getting Chef onto every one of our machines. The result of our work was a library of cookbooks that could reliably work in three distinct locations: physical servers in Rackspace, laptops in our SoHo office, and cloud instances in AWS. As we developed these cookbooks we gradually improved our process and testing techniques. We reached a flow that kept cookbooks tested and trustworthy no matter where we launched. This also gave the whole team visibility into system changes that would have been easily missed otherwise.

Read more →

Developer’s Toolkit: Chris Fortier

This post is part of a series where Behance developers talk about the various tools they use to get things done and make ideas happen.

fortier1. Who are you and what do you do at Behance?

Hello, I’m Chris Fortier and I am the Lead Quality Engineer at Behance. My main responsibility is to help guide the Quality Engineering Team so that we can figure out how to test all the various aspects of our websites. I’ve been on the team for a year now (I know, I’ve slacked off on writing this post) and I’ve been involved in quite a few projects. The first major project that I worked on was an automated process to build a replica of our production environments so that we can have a more effective development and testing process. These environments are built on VirtualBox and OpenStack virtual machines. For the past several months I’ve been working very closely with the DevOps team as we adopt Chef and standardize our infrastructure as code. Looking forward to 2014, we are in the process of a complete overhaul of our testing infrastructure and busy trying to figure out how to build a Continuous Deployment process. Stay tuned for details.
Read more →