There are thousands of different Android powered devices, with different screen sizes, chip architectures, hardware configurations, and software versions. Unfortunately, segmentation is the price to pay for openness, and there are thousands ways your app can fail on different devices. Regardless of such huge segmentation, the majority of bugs are actually introduced because of logic errors. These bugs are easily prevented, as long as we get the basics right! Here's a quick rundown of the 10 most common mistakes Android developers make.
Google Glass promises to revolutionize how we use our devices to interact with the world. But from a developer's standpoint, what is so special about developing for the Glass? You'll be glad to know that the answer is "Nothing!" Here's a step-by-step tutorial that walks you through developing your first Google Glass app.
The popularity and usage of Scala is rapidly on the rise, as evidenced by the ever-increasing number of open positions for Scala developers. In this article, Toptal engineer Matt Hicks introduces you to the power and capabilities of the Scala language.
The recent resurgence in Artificial Intelligence has been powered in no small part by a new trend in machine learning, known as "Deep Learning". In this article, I'll introduce you to the key concepts and algorithms behind Deep Learning, beginning with the simplest building block.
>If it ain't broke, don't fix it. It's a well known phrase, but as we know, most of the human technological progress was made by people who decided to fix what isn’t broken. Especially in the software industry one could argue that most of what we do is fixing what isn’t broken. Fixing functionality, improving the UI, improving speed and memory efficiency, adding features: these are all activities for which it is easy to see if they are worth doing, and then we argue for or against spending our time on them. However, there is an activity, which for the most part falls into a gray area: refactoring, and especially large scale refactoring.
Inexperienced programmers often think that Java's automatic garbage collection frees them from the burden of memory management. This is a common misperception: while the garbage collector does its best, it's entirely possible for even the best programmer to fall prey to crippling memory leaks. In this post, I'll explain how and why memory leaks occur in Java and outline an approach for detecting such leaks with the help of a visual interface.
From the very first days in our lives as programmers, we've all dealt with data structures: Arrays, linked lists, trees, sets, stacks and queues are our everyday companions, and the experienced programmer knows when and why to use them. In this article we'll see how an oft-neglected data structure, the trie, really shines in application domains with specific features, like word games.
World-class articles, delivered weekly.
Check out your inbox to confirm your invite.
Join the Toptal® community.