A smooth, cross-platform experience is the dream of every developer and business owner since the release of modern smartphones. In the history of mobile we’ve had iPhones and Blackberries, Android, Windows Phones, and a handful of smaller players. Building a native app for each one of these platforms sounds like an expensive venture and a long and arduous process.
I remember hearing about Agile for the first time. The concept behind it seemed pretty straightforward: sprints, planning sessions, and backlog—it all looked like it could really help us accomplish more in the same timeframe (especially in comparison to Waterfall).
One of the first things one learns as a quality assurance specialists is that there are three basic types of automated tests: unit, integration, and end-to-end tests.
You probably already know this: the first step to learning something in any subject is acknowledging that you don’t necessarily know it all inside out.
Our latest post on the Thunderbird redesign drew a lot of buzz from industry press. Some people loved the new, modern look, others preferred Thunderbird’s current default version. As a result, the mockups stirred some lively conversation on social media sites like Reddit and few other places on the Web, including OMGUbuntu, Antyweb or the Thunderbird Twitter.
2017 was a real adventure and a genuine milestone for our team. And just in case some of us happened to forget what awesome human beings we’re working with, we’re going to write all the great stuff that happened last year down.
Recently, I’ve been playing around with a search in Elasticsearch and got stuck with development when attempting to work with an array of objects. Indexing went fine, the query results, however, did not look as expected.
This is really exciting: our team has just wrapped up the work on State of Vue.js—a comprehensive report crafted for developers and technology businesses interested in making educated decisions about their stack.
A couple of months back, I finished my first major project with Ruby but sans Rails. You probably don’t know that, but I’m one of these people who first try to master a framework and only then look at the language documentation. This is the approach taught by “the Rails way.” When I started my adventure with Rails, I believed it to be a perfect framework, God’s gift to developers. A couple of months later, I saw big, old RoR projects… and I wanted nothing more than to run away from Ruby as far away as possible.