An old friend of mine, Geoffrey Grosenbach, shares thoughts on why thinking like a developer could be a good thing...even if you're not...a developer.
Thinking Like a Developer
26 Sep 2016
Entries tagged: development
A Redesign for the Future
1 Jun 2016
Our work with the Portland-based Meyer Memorial Trust (MMT) recently launched and the first applications to enter its new system are making their way to MMT this month! In this post, we wanted to share our process for building the grant management database, the lessons we learned, and the result of almost three years of working together with MMT.
How We Built Our New Website On Squarespace
18 Apr 2016
Why is Ruby On Rails a Good Fit in 2016?
5 Apr 2016
An overview of why we use Ruby on Rails and why it is a good framework for the people we work with.
Learning D3
29 Mar 2016
I recently had the opportunity to use D3.js for the first time. The learning curve was steep, I was able to produce a series of dynamic charts that I was quite proud of. Here is a summary and brief walkthrough of my learning experience.
Computed Macros in Ember
24 Mar 2016
Simplicity vs. Maintainability: "One Model, One Endpoint" with Ember Data
3 Mar 2016
Early in our Ember development we came to a crossroad that had significant impact on the Model structure in our application. In this post I’ll summarize one of many issues we ran into during those first several months, and solicit feedback in search of a "best practice" for the Adapter/Serializer structure in the following scenario.
An interview with Carlos on the Treehouse blog
23 Feb 2016
The folks over at Treehouse interviewed Carlos on our approach to hiring junior developers.
Debugging HTTP Requests with Sinatra
23 Feb 2016
Recently I was working on a task where I was attempting to connect to a third party API (from a Rails app using the HTTParty gem). The API had a fairly complicated authorization header that needed to be built, by concatenating the body of the request itself along with various authorization headers, then being hashed, and then being base64 encoded and escaped. If the header was improperly formed, all I saw was a 403 Forbidden response - not particularly helpful for debugging.
A Reflection on "The Rails Doctrine"
8 Feb 2016
Planet Argon has worked with Ruby on Rails for over a decade. While not without it's hardships or challenges, we feel that "The Rails Doctrine" perfectly highlights the reasons why Planet Argon has found RoR to be a recipe for success. Both in business and the happiness of all parties involved in a project.