Weerasak.com

Ruby Techniques Revealed: Autoload by Peter Cooper

Autoload – Load stuff only when it's needed

Write an Internet search engine with 200 lines of Ruby code from saush.com

SaushEngine is a web search engine which means it goes out to Internet and harvests data on Internet web sites. Having said that, it’s definitely not production grade and lacks much of the features of a proper search engine (including high performance) in exchange for a simpler implementation.

TwitterAuth: For Near-Instant Twitter Apps by Intridea.com

The public beta of Twitter OAuth support has been released and I’m excited to introduce a new library that I’ve been working on called TwitterAuth. TwitterAuth is a Rails plugin that provides a full external authentication stack for Rails applications utilizing Twitter. Think of it as “Twitter Connect” for Rails, letting you create an application that may be logged into using only Twitter credentials.

The Book Of JOSH Scala In The Enterprise from The Grey Lens Man's View

Fast forward… Currently a very small team and myself are near completion of the first major functional component on the JOSH stack.

All of the development talent on the team are experienced Java developers. And they have been effective from Day 1.

No real discussions of covariance and contravariance was required. We did discuss HOF, anonymous lamba, closures, cut syntax, maps, folds, reduces. And strangely their heads did not explode. We did discuss the evil of mutable state, and referentially transparent functions.

They were enthralled.

Pragmatic Real-World Scala by Jonas Boner

Real-World Scala: Dependency Injection (DI) by Jonas Bonér

Scala is a very rich and deep language that gives you several ways of doing DI solely based on language constructs, but nothing prevents you from using existing Java DI frameworks, if that is preferred.

Clean Code Cheat Sheet by reborg@reborg.net

Apparently there is no definitive Grand Unified Theory but all of the following principles contribute somehow to separate good software from bad software. Please print on the wall.

Handling Bugs in an Agile Context by Elisabeth Hendrickson

Many of the traditional teams I worked with (back before I started working with Agile teams) had bug databases that were overflowing with bugs that would never be fixed. Usually these were things that had been reported by people on the team, generally testers, and prioritized as “cosmetic” or “low priority.”

Such collections of low priority issues never added value: we never did anything with all that information. And yet we lugged that data forward from release to release in the mistaken belief that there was value in tracking every single time someone reported some nit picky thing that the business just didn’t care about.

Prance with the Horses, Skittr with the Mice by David Pollak

How hard is it to build a highly scalable social messaging system? Not hard if you use the right tools. Over the last week and a half, in my spare time, I wrote a Twitter clone in Scala and lift. It's 884 'wc -l' lines of code including comments. It can handle 1M+ users on a two Intel Core 2 Duo boxes (one as the web front end and the other as the message broker.) With a weeks of full-time coding, it could be modified to scale linearly with the number of boxes in the system.

Seeing Metaclasses Clearly by why the lucky stiff

If you’re new to metaprogramming in Ruby and you’d like to start using it, perhaps these four methods could give you a bit more vision.