Rails plugin which adds a convenient way to override attr_accessible protection.... You can mark certain attributes as trusted for different roles.

When I realized what had gone wrong, the light almost blinded me.

Steak is like Cucumber but in plain Ruby.

Pretty print your Ruby objects with style -- in full color and with proper indentation

I love Cucumber, but I hate writing step definitions. They are ugly, awkward to write and very, very boring: Most step defintions merely create objects for a scenario to chew on.

Next in our series on not shooting yourself in the foot: Doing a sudo shutdown -h now on the main database server right before you head home to cook dinner for six.

Unfortunately vanilla Ruby modules lack support for many idioms popular in modern Ruby. Most importantly, we have become accustomed to composing our classes with meta-programming macros such as has_many, validates_presence_of or after_save. And modules weren't built with macros in mind.

Though we ended up switching to what I consider to be a technically superior product based on simplicity, we arrived there because of poor community interaction on the part of the Bundler developers.

If you need to "originally" write your code in Swahili, while listening to Milli Vanilli, while reclining in a patch of mud, and then you need fifty oompa loompas to translate the Swahili into C, that is none of Steve Jobs fucking business.

I’m a principled person. Apple’s offended my principles. Consequently, I’ve decided to abandon iPhone development. I won’t work in this ask-permission environment any longer.

What happens if the iPhone application you’ve based a business on is found to depend on a library that is forbidden with iPhone OS 4? Do you start over or give up? A lot of developers are asking themselves that question today.

You know how you tell when an app for the iPhone was written in MonoTouch? It doesn’t leak memory.

It’s hard to build a business on a platform where you feel like you cannot trust the men in power. If they can take down Adobe a few days before the launch of their flagship product, what hope do smaller players hold?

They can ship their own product and give it away till you go bust, then start charging for it; and use secret APIs you can’t see; and they can break the published APIs you use. All of these things have historically been done by platform vendors.

Either way, nobody likes stepping in shit. And nobody likes cleaning up shit. So the whole interaction starts off on the wrong foot, perhaps the one covered in shit. Your job, as developer or as reporter, is to deliberately steer it back to being a positive one where the developer wants to fix shit and the reporter wants to continue to report shit.

Code up top for quick reference, details down below—we’ll prepare typefaces for use on the web, go through @font-face CSS line-by-line, and get the experts’ take on browser support.

Download hundreds of prepackaged @font-face kits

Apple puts itself in an untenable position trying to play gatekeeper while simultaneously having such a broad and deep marketplace structure. It's like watching a character from Alice in Wonderland attempt to beat Kurt Godel at a game of chess by trying to change the rules faster than those rules can be exploited.

So what Apple does not want is for some other company to establish a de facto standard software platform on top of Cocoa Touch. Not Adobe’s Flash. Not .NET (through MonoTouch). If that were to happen, there’s no lock-in advantage.

Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).