Last month I decided to quit, to stop being a manager/developer. 5 years ago I was looking for a place where I can improve my rails skills and suddenly I stayed at that place for 5 full years :).

Below are the scribbles, I hope to read them again in few years (dang) and see how far I /hopefully!/ grew from there.

After like 3 weeks of not touching code I decided to refresh my pet project a little bit, below are random issues you might encounter while trying to upgrade your old Rails 4 app to Rails 5.

Recently I have been selling a lot of my stuff. Simply getting rid of unused or unneeded things - and mostly I’m packing & sending it to other parts of the country by using a package carrier that requires printing labels. The standard drill. But those labels are kinda smallish, you can fit like 4 on single A4 page (it’s like a horizontal strip kid of thing).

Ok so I’m sending 3 packages and I get 3 pdfs to print with huge amount of white space. I don’t own a printer anymore (sold it as well), I need to go photocopy point, technically speaking I could simply go and ask them to print 3 separate documents. But the environment and extra 20 cents - I just couldn’t stand it :P.

You’re building open source API client? That’s great ❤️ I like you already. But please keep in mind:

Pfew, after over a year of inactivity it’s time to refresh this site a little bit. It was on my todo list for over a while now.

Lately I have been looking for some solid alternatives to Ruby, and I must admit up-front - Rails spoiled me, badly.

I was hungry for some performance boosts, and let’s face it - dynamically typed languages can get you until some point.

I played with few popular modern languages (manually dealing with memory management? No thank you sir) and tried to hook them into Rails application.

Lately I had to migrate pretty fat (300GB+ data and 150GB+ of index data) postgres table - application grew, we had to get rid of one pretty big column that was redundant now, change main composite index, change one column type etc. etc. The problem was - do it without significant amount of downtime.

You can google up tons of solutions, but let me walk through approach I chose - hopefully you will find it somewhat useful.