R. Clayton Miller's 10/GUI is probably one of the most dramatic reimaginations of the desktop user interface I’ve seen in a long time. This concept proposes a multitouch interaction system that does not require a multitouch screen (and thus does not have to deal with all the problems such a screen causes), but instead uses a multitouch area near the keyboard.
If you need big synchronization points, e.g. for big marketing campaigns, you might be better off using an iterative development approach. If you want to ensure a continuous flow of features, which are optimized for time to market (cycle time), Kanban might work better for you.
What Pradipta Archiputra (aka "MAX ARCHIE") uses to send his recruitment emails. This plugin pretends that CC and BCC
If I ruled the world, IE would not be used by people. Since that is not the case, we need to put these rules to memory.
Browsera automatically detects cross-browser layout problems and scripting errors on your website.
DevIL is a fast and lightweight image library that supports the loading and saving of images in almost any graphics format. It also provides some basic image manipulation functionality.
Concerns is a simple Rails plugin that provides you with a simple way to organise your Controllers, Models and Mailers, and split them into smaller chunks of logic. It is especially useful when you have lengthly models, and you get fed with having to scroll through several hundred lines of code.
Apple's random rules for iPhone app approval are a recipe for trivial apps and alienated developers
validate( "email".is("required").andIsAn("email") );
Google Chrome Frame is a plugin for Internet Explorer that embeds the entire Chrome web rendering engine inside IE.
Stop writing your own random string generators. Rails does this for you.
decided to go fixtureless with Shoulda + Factory Girl. All good, except one problem. Slow as fuck tests. So here’s fast_context as a solution for it. fast_context compiles all the ‘should’s within a context into a single test.
Deadweight is RCov for CSS, kind of. Given a set of stylesheets and a set of URLs, it determines which selectors are actually used and reports which can be "safely" deleted.
The idea behind scrooge is both surprisingly simple and powerful: instead of forcing the developer to manually specify each attribute column, simply observe and record for some period of time all of the attribute accesses and then reuse this knowledge in the future to automatically optimize your subsequent query requests.
All methods generated by string_attr_reader are now added to that new module instead of the class. The result is that when overriding those methods you can now call super because they’re are inherited from the new module.