Although nowadays we’re swamped with knowledge on more or less any topic we can imagine, it can still be hard sometimes to find reliable sources. In every industry, however, there is always a handful of individuals who really know their stuff and following their social media outlets, blogs, and their presence on other platforms is probably the best thing you can do for your career. In case you missed it, Karolina already drafted a similar list of Vue.js experts to watch in 2018. Now it’s time for Node.js.
You know, truth be told, there’s more than a couple of IoT geeks on our team here at Monterail. In late 2015, we set up a Raspberry Pi-based smart office system at our Wrocław offices, a process that one of my co-workers described in detail in a separate blog post. Since nearly three years have passed since the installation of the system, and given that we’ve grown a lot during these two years, we’ve decided that it was time to introduce a couple of upgrades to the system and make our office even smarter.
Amazon Alexa, the popular voice assistant helping with everyday tasks, has become a best friend to many households in the US and elsewhere. The list of available features for Alexa, released by both Amazon and third parties, keeps growing steadily, but according to reports from January of 2018, that the total number of skills (apps) working in the US only 25,784. More vendors are looking to integrate their product with the voice assistant—currently, you can link it to your Gmail account, your calendar, phone, or even home lighting.
Recently, I had a pleasure of attending the Wroclove.rb conference in Wrocław where one talk in particular caught my attention more than others. “Web Performance with Rails” by Stefan Wintermeyer was, in my opinion, the best prepared, one of the most indispensable, and definitely the most useful of all the talks but, most importantly for me, it was a wellspring of new knowledge for me and a source of inspiration that ultimately drove me to write this post.
Have you heard about progressive Web apps? Of course you have. The whole Internet seems to be discussing them right now. And the subject got even hotter after Google I/O 18’ and a long-awaited confirmation that PWAs are coming to desktop for Chrome OS 67 in early June. Work is already under way for Windows and Mac.
For a long time, I’ve been hearing a lot of criticism about the Rails way and some months ago my private experiences convinced me that I cannot find any use cases for that approach. It has developers build very fat models, controllers, and DRY is commonly understood as a method of extracting repeated one-liners to new methods.
This is a story of how a day-to-day developer overcame his fears and came out of his comfort zone. Of how he and his team got into a project which code was so bad they cried a little when they saw it for the first time. Of how they took care of it and made it great. Of how they made clients happy and left the whole team with a “mission accomplished” feeling. Of how they finally succeeded.
Is there anyone out there in the Ruby community who doesn’t know Active Record? I don’t think so. Many of us start our adventure with Rails by writing AR models. And we write them a lot. We detect the N+1 issue many times. We refactor it much more. We doubt our ideas, solutions, and AR many, many times in our Ruby lives.
In object-oriented programming, SOLID states for five design principles that help a developer build easy to extend and maintain software. In this article I’m not going to explain what’s hidden behind it though. It’s been already done by Uncle Bob (who wrote the rules down) and in dozens of articles all over the web (like the one on by Lea Karam).