I’m Michał Łęcicki (aka Maikhel), ruby software engineer from Visuality 👋 I believe self-improvement, responsibility and clean solutions are necessary to get things done: both in software development and real life. Feel free to check some of my posts below. There are also some photos and more information about me.
Preserving data quality is always a challenge. Especially in the Ruby on Rails world where products ship fast. It means some compromises are made along the way and often data quality is sacrificed. And when it comes to data - it’s better to prevent than cure. Continue reading to see how you can avoid many data problems, at different stages of Rails app development. You will thank me later.
Posted on 10 August 2022
I’ve always been curious about productivity tools and techniques to try. But when I read a book written by David Allen, it amazed me. I finally found a framework that could replace the to-do lists I was rewriting every day! Let me share the most beneficial aspects of GTD.
Posted on 14 May 2022
Some time ago, we needed to implement a full email inbox feature in the Ruby on Rails application. It was supposed to have all the basic functionalities that regular email inboxes have: send and receive messages, collect them in threads, have a contact book, etc. While email sending is a relatively frequent feature among Rails applications (there are tons of different solutions around the web), receiving messages is not so popular. So, let’s take a look at possible ways of building an email receiver mechanism with Rails.
Posted on 26 February 2021
When playing board games, I always try to improve my performance and find some clever way to beat my opponents. I love analysing, discussing and recalling past games to find the most useful strategy and see things that are not seen by other players. This allowed me to form a few simple rules that increase chances of victory — not only in board games but also in real-life activities.
Posted on 31 December 2019
Uncertainty is an inseparable part of creating any software. At the beginning of the project you never have a full knowledge about future requirements and features. Developers don’t know the whole specification, project manager doesn’t know all clients’s expectations and usually clients are not aware about all features their product should have. When the amount of unspecified requirements is significant, choosing to create a prototype could be really beneficial.
Posted on 04 July 2019
Page 3 out of 3