We love open source and we invest in continuous learning. We give back our knowledge to the community.

New Features in Ruby 2.5.0


The 2.5 series of Ruby first saw the light on October 10th, as part of the first preview release toward Ruby 2.5.0. Just a couple of months later, on Christmas day (a popular release date on the Ruby releases calendar), the first stable version of the series was born.

Reflected on the release notes, we can find a whole bunch of features, changes and performance improvements which found their way to the final release. On this post, I’d like to do a quick rundown of the features that I’ve found most interesting.

Unopinionated Comparison of Glimmer and React

javascript Comments

In this article, we will discuss how different (or similar) it is to use Glimmer as compared with React. Glimmer is a new library in the Ember ecosystem, which was released in March. Since the creation of this project, the Ember team has been experimenting with a new components API and the result of this work is expected to gradually be integrated into Ember itself in the future.

To some extent, Glimmer is comparable with React because the scope of both libraries is very similar: UI components for the web. However, let’s take a look at some examples to highlight some of the similarities, as well as the differences.

Remote Retrospectives Using Trello


At WyeWorks, we are passionate about improving on what we do. Indeed, our software development process emphasizes continuous improvement. To implement this, we use Scrum’s proposed framework. This article intends to explain our experience conducting Sprint Retrospectives with teams located across different parts of the world, in this particular case members working in Spain, Germany, and Uruguay.

On several occasions, we have done retrospectives with remote team members, trying several techniques such as paper and post-its and some digital solutions. This year, however, we performed an experiment from June up to the current day that we found we preferred to the previous ones. That’s why we want to share it with you.

A Review of Server Side Rendering in Javascript Frameworks

javascript Comments

The Javascript ecosystem is always moving fast, so it’s important to keep track of how everything is progressing, especially when it comes to tools and frameworks. The people at This.Dot produces an amazing series of webinars, called This.Javascript, that discuss the latest on major Javascript frameworks and tools. This post is the first in a series of articles about topics that caught my attention after watching the latest episode.

Let’s now discuss the current state of Server Side Rendering (SSR) in Javascript frameworks. Each of the big contenders in the ecosystem made remarkable progress in their particular SSR solutions in 2017. Moreover, the existing solutions are still improving while more and more people are using them for real stuff.

What the Tag? Episode 1 - the Document Object

html Comments

Twenty three years ago, as I was learning to walk, something more important was going on, something that has been part of the technology we use every day, something that pretty much brought us to where we are today (in terms of web development): HTML’s birth!

In this series we’ll dig into the DNA of modern HTML (or as the people at WHATWG call it, The Living Standard). We will identify and explore things that are unusual or unknown (just because nobody was told about them).

Better Tests Feedback With Ember-qunit-nice-errors

ember Comments

As any Ember developer probably knows by now, the error messages shown by failing asserts are far from ideal. Getting a failed, expected argument to be truthy, was: false followed by a stack trace that points to lines on the generated test file (one file with all your compiled tests), can be pretty disappointing when you want to be able to get quick feedback from your tests.

One of the best practices when using QUnit is to always include an error message that explains what’s the purpose of the assertion. This is a good practice but in reality it falls short: developers tend to be lazy and not include all messages, or sometimes the error message and the assertion are one to one equivalent, e.g.: assert.equal(page.title, 'hello world', "Page title is hello world"); Having better errors by default can help in those cases.

As part of our Technical Thursdays’ last cycle, we set out to improve this, looking to both enhance our tests and learn more about ember-cli and its addons.

The result was ember-qunit-nice-errors, a just add water and mix kinda addon 😉

Behavior Changes in Ruby 2.4


The first preview version of Ruby 2.4 was released a few days ago. This particular release includes a bunch of new features. Moreover, it introduces some fixes and changes that are not entirely backward compatible. Thus, we need to pay close attention to these differences in this new version of Ruby.

In this post, we’ll focus on some remarkable changes in behavior, so as to better understand how our applications could be affected or improved once we upgrade to Ruby 2.4.