Developers are a fussy bunch. We sweat on the tiniest details and every aspect of our product has to be just right. We don’t like entrusting our precious designs to anyone outside our inner circle. Yet we’re increasing delegating key quality assurance (QA) tasks to robots. The market for automated testing products is expected to be worth $20 billion by 2023 – three times as much as now.

Today, Docker or Kubernetes are obvious choices. But, back in 2015, these technologies were just emerging and hoping for massive adoption. How do tech companies make the right open source technology choices early?

Realistically speaking, how many times do you redownload an application that’s buggy? Unless it’s a hugely beneficial app, which one might begrudgingly use (off the top of my head, I can’t think of any that aren’t replaceable), users tend to just switch to an alternative app that does the same thing — sans bugs.

Thanks for continuing to read all of our streaming data use cases during my exploration of Talend Data Streams. For the last article of this series, I wanted to walk you through a complete IoT integration scenario using a low consumption device and leveraging only cloud services. In my previous posts, I’ve used a Raspberry Pi and some sensors as my main devices. This single board computer is pretty powerful and you can install a light version of Linux as well.

Solving a Rubik’s Cube. Skiing uphill. Completing Goldeneye on the N64 and looking suave when standing next to George Clooney. These are all things which are harder than marketing your product to developers. But, to be honest, we can’t think of too many more. We’ve tried everything to promote Bugfender to the development community. Being developers ourselves, we should have known how difficult this would be.