You've probably heard that "data is the new oil" before. That’s a really cool analogy – said somebody in 2006. Now, this perspective has become a trope. Yet...it still depicts what Data Engineering is really well. That’s why we’re going to disappoint and talk about Data Engineering with gasoline analogies once again. But don't leave; we promise it's worth reading.
Ordering IT in the early 2000s usually meant listing functional requirements. Back then, developing software in accordance with a specification provided by the client was a common practice. As a result, the outcomes were often disastrous. So, in this blog post, we’re going to show you how to do it professionally in the 3rd decade of the 21st century to avoid flops.
Last year, online sales on Black Friday hit $9.03 billion For context, just 3 years earlier, the revenue generated from eCommerce reached only $1.3 billion. As a result of the rising digitalization, the need to transform warehouses into smart logistic centres is growing accordingly. And funnily enough, although some warehouses have already embraced the miracles of modern technology, many others still use… paper counts.
Did you know that in 2021, numerous manufacturing machines are still operated by Windows 95’s ancient precursor? Since MS-DOS premiered in 1981 (Ronald Reagan just started serving his first term), you may naturally think – how is that even possible? The short answer is – legacy systems are not easy to replace. And interestingly, it’s rarely due to the cost factor.
Launching something new – especially when it’s innovative – naturally bears a risk of failure. Although the reasons for an offering’s lack of success are often complex, there are overarching themes that link the failure of new products. Luckily, there's a way to avoid all of these traps. In this article, we'll show you why prototyping is so important and why you should never start developing a big software solution without the right preparations.