Recently I’ve had to add new indexes to existing tables in a Postgres database, while developing my Rails project.

I’ve realized that adding those was taking me a long time due to the amount of data in these tables. I was going crazy until I found out this Postgres option. What happens next is incredible…

Once I’ve gotten familiar with the basic commands, my first problem was how ugly emacs looked out of the box. No one on earth can have any pleasure working on an ugly UI. So I’ve started looking for how to change it.

This lead me to the initialization of configuring emacs defaults.

This will be a part of a series where I’ll be trying the devil’s question.

Recently I found that our current project had a bunch of temporary files that were not being cleaned up.

Recently in one of our projects, we decided to take a deeper look at N+1 queries, as well as general DB Operations performance. We’ve started by installing this awesome gem called bullet . This gem, creates a log file for you, where it lists all the N+1 queries found, unnecessary eager loading queries and missing requires. This is quite useful as a starting point for improving your general web application performance.

We’ve successfully cleaned up most of the logged queries and we’ve moved on with our lives. Because our application relies a lot on indexedDB, we’ve never experienced (at least not until today) a lot of hassle after making bullet part of our development environment.

Recently came against the deal of choosing a secure password for some random access.

Even though it is not a good policy to use the migrations to populate your database, sometimes, when there are very static things it is almost safe to assume that you can do it.

Recently in our project we’ve had an issue that involved multiline text wrapping.

In my current job, we are using indexedDB to handle data offline and make it available on the browser even when there is no internet connection.

When starting a new project is important for you to keep in mind that it is going to be used and handled by someone else in the future (worst case scenario is the future you – who might not remember everything your present you thought when starting the project). Therefore, there are some basic steps that you can go through in order to keep your project organised, usable and maintainable.