class BaseLab < Blog::Awesome
  topics :technology, :coding
  authors :devs => 'Makers of Base CRM'
import blog
class BaseLab(blog.Awesome):
  topics = ["technology", "coding"]
  authors = {'devs': 'Makers of Base CRM'}
var BaseLab = new Blog.Awesome({
  topics: ['technology', 'coding'],
  authors: {'devs': 'Makers of Base CRM'}
@interface BaseLab : Blog <Awesome>
@property (strong) NSArray *topics = @[technology, coding];
@property (strong) NSDictionary *authors = @[devs : @"Makers of Base CRM"];
[[BaseLab new] publish];
class BaseLab: public AwesomeBlog {
  BaseLab() {
    authors["devs"] = "Makers of Base CRM";

class BaseLab extends Blog.Awesome {
  private Topic[] topics = new Topic[] {
    new Topic("technology"), new Topic ("coding") };
  private Map<AuthorType, String> authors = new HashMap<AuthorType, String>();
  public BaseLab() {
    authors.put(new AuthorType("devs"), "Makers of Base CRM");}
new BaseLab().publish();

Is it time to fold on iOS4 and go all-in on iOS5?

Most iOS developers occasionally ask themselves whether it’s time to ditch iOS(n-1) and only support the latest and greatest iOS(n). This seems to be a common dilemma since Apple releases on average one major version of its mobile operating system per year.


The wroc_love.rb Conference

During this weekend a part of the Futuresimple team (Marcin, Michal, Przemek, and me) went to Wrocław to attend wroc_love.rb - a Ruby conference organised by the Lower Silesian Ruby User Group. We’d like to share our experiences.


CSRF Attack using JavaScript

Most of you are aware of the CSRF attack. I use JS on a daily basis but I actually never thought that the code I develop could be CSRF-prone.

You saw that coming - I was wrong and I want to share that harsh lesson.

Let’s assume you’re developing a web app called (obviously because it’s so good it will make everyone say OMG!). The app is getting bigger, lots of people use it, new features are being added on a weekly basis. At some point you conclude it would be nice to inform users about some recently added features.


Reinventing tools for developers, let's start with unix terminal

A big chunk of our day-to-day work concentrates around unix terminal. We all know the usual flow, opening our loved text editors, running scripts, consoles, profilers, running tests, ack’ing, logging into servers, shipping code to production etc. Actually if I were about to pick the most important development tool (except for the programming language), I would have a hard time choosing between a text editor and the terminal.


Gracefully exiting from console programs in Ruby

Imagine you write a CLI program or a Rake task which loops through some data performing some work on it. You run it and then you remembered something. You’d love to kill the process with ctrl-c, but that will raise an exception somewhere in the loop. What you want is for the iteration to complete and then you want the program to quit.

You could handle the Interrupt exception or add some conditions. But how about a cleaner and reusable way?

Prev page Next page
158 6
A broadcasting microframework making publishing of messages to different services easy.
128 10
Dropbox API Ruby Client
91 14
Node runner for Jasmine JavaScript BDD testing framework
4 1
Future Simple's github homepage
2 1
HTTP API Client Builder
2 0
Obedience Core
1 1
All kinds of presentations delivered by FS team members
1 1