• submit to reddit
Allen Coin04/01/13
3569 views
0 replies

Links You Don't Want to Miss - April 1

Today: Debugging with the kitchen oven, Apple's new game controller, Web designers vs. Web developers, and a CSS April Fool's Prank you can play on your coworkers!

Mitch Pronschinske04/01/13
2314 views
0 replies

ZeroMQ: Supercharged Sockets

Rick is a developer at GitHub, a self-diagnosed REST nerd, bleeding edge DB enthusiast, with an active OSS profile. Here he will show you how to get the most out of the lightweight ZeroMQ message broker.

Johanna Rothman04/01/13
2407 views
1 replies

Telecommuting, Hoteling, and Managing Product Development

There are two sides of this conversation about telecommuting: the employee side and the management side. I hope you stick around for both sides. You can yell at me at the end.

Mitch Pronschinske03/29/13
1454 views
0 replies

Cloudbursing with Amazon EC2 and SQS

Learn how this can actually work with Amazon EC2 and SQS. The implementation is based on Ruby on Rails and Resque/Redis, but the concepts are broadly applicable.

Eric Gregory03/29/13
3733 views
0 replies

Links You Don't Want To Miss (3/29)

Today: Too many programmers think they know more about statistics than they do (which is to say, anything), Nintendo introduces a web framework, and a Chrome project member eyes asm.js.

Mitch Pronschinske03/28/13
1584 views
0 replies

Webinar: Using SMTP with Amazon Simple Email Service

Learn how Amazon Simple Email Service (Amazon SES) just got simpler with Simple Mail Transfer Protocol (SMTP) support. Amazon SES is AWS's highly scalable and cost-effective bulk and transactional email-sending service for businesses and developers.

Mitch Pronschinske03/28/13
1328 views
0 replies

Getting Productive with the AWS SDK for Ruby

Learn best practices for using the AWS SDK for Ruby, including configuration, logging, debugging, consuming high and low level interfaces, collections, memoization, Rails integrations, AWS::Record and more.

Mitch Pronschinske03/26/13
31574 views
0 replies

Links You Don't Want To Miss (3/27)

News about Google's Go and Ruby. Plus, the hoops that job candidates have to jump through and Erlang the Movie II: The Sequel.

Anders Abel03/26/13
9872 views
4 replies

How We Achieved the Best Code Quality in My Career

My recently finished project produced the best code quality in my career so far. The key success factors were a clear architecture, insane compiler warning levels and last but not least code reviews.

Allen Coin03/26/13
4887 views
0 replies

Links You Don't Want To Miss (3/26)

Today: The computer science of JavaScript, The White House shares its web API standards, Digg wants to replace Google Reader, and Conway's Law of Starship Captains.

David Shaw03/25/13
1771 views
0 replies

You Can Be Comfortable And Productive At The Same Time!

An office might not seem like an unhealthy working environment when compared to factories and car garages. Working in an office demands sitting for long periods of time working in front of a computer which means comfort and right posture is of the utmost importance.

Paul Wells03/22/13
9049 views
0 replies

5 Ways Objects Can Communicate With Each Other Heading Towards Decoupling

Decoupling can be achieved and yield flexibility, but this does not mean it is appropriate for every call from one object to another. The best thing to do is start with straight method calls, but keep cohesion in mind.

Leigh Shevchik03/22/13
796 views
0 replies

New Relic on Heroku: Measuring Queue Time Using Ruby Agent

On March 5, we released version 3.5.7 of the New Relic Ruby agent, which contains several changes to how Request Queueing is reported.

John Sonmez03/21/13
24116 views
5 replies

There Are Only 2 Roles of Code

All code can be classified into two distinct roles; code that does work (algorithms) and code that coordinates work (coordinators). I would say that 90% of the code I have written does not nicely divide my classes into algorithms and coordinators.

Jurgen Appelo03/21/13
3398 views
3 replies

Stop Blaming the System!

I see it again and again. The suggestion of systems thinkers and Agile writers to stop blaming people and instead try blaming the system.