This is going to be a short piece on one particular habit which I practise when writing code. It’s extremely simple and obvious, but I’m surprised how many programmers skip it.
Do you know what “append-only CSS” is? It’s CSS you are so afraid of changing that you exclusively append new rules to one never-ending file.
How to deal with it? Take a look at the article about CSS refactoring which I co-authored.
I hate using modal dialog when the new content could be easily nested in the same page. I just don’t like the user experience of a popup. Why limit yourself to a small box when you can show it in the full-blown layout?
However, sometimes clients insist on a modal in their design and we have to deal with it. In this blog post I will show you how to make the modal dialog a little bit better – give it its own URL.
In this blog post I want to reflect on things which make Ruby a beautiful language to read and write, and on things which make Ruby on Rails a convenient tool to quickly prototype.
This is an introductory level blog post.
This post describes how to use Tiddle – gem for token authentication which I created. Tiddle is a Devise authentication strategy which supports multiple tokens per user.
This post describes the application architecture pattern which is (in general) nothing new, but (from my experience) rarely applied in the Rails world. I’m talking about the nice and simple abstraction – message queue. But let me start by describing the goals I want to achieve and some alternative solutions.
Programmers make mistakes. Some of them are just annoying (for others to read) and some are really dangerous. Here is my selection of 10 mistakes done by Ruby / Ruby on Rails developers. These tips are easy to follow and can save you much time of later debugging.
It’s been a while since my last post. I was writing my engineer’s thesis which caused general disgust towards writing at all. Anyway, these sad times are over and here comes the shiny new blogpost about introducing service layer in Rails applications. It does not contain any breakthrough thoughts, but is rather a mixture of ideas I learned from great Ruby developers.
I’ve recently started playing with AngularJS. Coming from the Rails world I expected a structure enforced by the framework, good default configuration and separation into development, test and production environments.
It seems that the way to start a new project suggested by the creators of AngularJS is to clone angular-seed project. While this seed project worked for me during development and testing, I was a bit lost when it came to deploying to production.