This month, Bugfender turned four years old. We didn’t throw a massive party to celebrate the birthday (the team is spread all over the world, which makes party-planning rather tricky) but we all reflected with pride on the amazing journey we’ve been on. Over the last four years we’ve watched Bugfender become a vibrant, sustainable venture. What started as a spin-out from our parent company, Mobile Jazz, is now established in its own right.
At Bugfender, we strive to keep improving. The number of smartphone users is rising all the time, as is the number of smartphone models. So the challenge of fixing bugs is getting increasingly difficult. So it’s with great pride that we announce new and improved support for both Ionic and Unity.
We know that data is a key driver of success in today data-driven world. Often, companies struggle to efficiently integrate and process enterprise data for fast and reliable analytics, due to reliance on legacy ETL solutions and data silos. To solve this problem, companies are adopting cloud platforms like Microsoft Azure to modernize their IT infrastructure.
A common perspective that I see amongst software designers and developers is that Machine Learning and Artificial Intelligence (AI) are technologies which are only meant for an elite group. However, if a particular technology is to truly succeed and scale, it should be friendly with the common man (in this case a normal software developer).
Azure SQL Data Warehouse (DW) has quickly become one of the most important elements of the Azure Data Services landscape. Customers are flocking to Azure SQL DW to take advantage of its rich functionality, broad availability and ease-of-use. As a result, Talend’s world-class capabilities in data integration, data quality and preparation, and data governance are a natural fit with Azure SQL DW.
Since the release of Talend 7.1 users can build Talend jobs as Docker images and publish them to Docker registries. In this blog post, I am going to run through the steps to publish to the major cloud provider container registries (AWS, Azure and Google Cloud). Before I dig into publishing container images to registries, I am going to remind you the basics of building Talend Jobs in Docker images from Talend Studio as well as point out the difference between a local build and a remote build.
How do you organize an effective meeting when you don’t have a physical space to hold it? How do you manage workflows across different time zones, when some people are starting work as others go to bed? How do you integrate new people into the culture when you don’t have a physical HR department?
