Peter Marklund

Peter Marklund's Home

Peter on Rails

Lessons Learned in Ruby on Rails and related technologies. Subscribe

Sat May 29, 2010
Programming

Migrating RSpec to Mocha

Over at the MyNewsdesk developer blog:

Make a Comment

Tue May 11, 2010
Programming

PostgreSQL Unreliable Default Sort Order and Random Rails Test Failures

More good stuff from the MyNewsdesk Developer Blog:

Make a Comment

Wed May 05, 2010
Programming

Rails 2.3.2 Bug and Rails Cache Enable/Disable

Two new posts from the MyNewsdesk Developer Blog:

Make a Comment

Tue April 20, 2010
Programming

New Plugins For Rails Model Caching: Cachable Model

As part of an ongoing effort to offload out database at MyNewsdesk I have released a new Rails plugin called Cachable Model. The plugin is similar to an older plugin called Cached Model in that it basically caches primary key id lookups for ActiveRecord models. The Cachable Model plugin has an extra feature that lets you cache lookups by other unique columns as well. Here is an example:

Make a Comment

Mon January 18, 2010
Programming

Newsdesk Developer Blog - Back in Business

Now that I'm back working at Newsdesk I've started posting in our developer blog again:

Make a Comment

Wed January 06, 2010
Programming

Book Tip: The Mythical Man Month

Fred Brooks is a Computer Science professor who managed 5000 man-year IT projects at IBM in the sixties. His words carry a lot of weight and he certainly has something profound to say about software engineering. The central theme of the book is that of conceptual integrity. It's about the need to have a single architect, a master mind, who oversees all development and makes sure all the parts fit together. "A clean, elegant programming product must present to each of its users a coherent mental model of the application". The ideal scenario for conceptual integrity naturally is having a single programmer. The problem is that some systems are so big that in order to finish them before they are obsolete you need a large number of developers. Much of the book is spent discussing this difficult problem. How do you organize huge developer teams?

Read More