<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=266259327823226&amp;ev=PageView&amp;noscript=1">
Skip to content

Full Stack Doesn't Belong Only to Software Developers

Tuomo Riihentupa works as a Lead Architect at Cloud1. He is responsible for some of Cloud1's most significant client accounts. Tuomo's background includes experience working both as a consultant and an end client. In his current role, he aims to bring a strong understanding of the client's needs and daily challenges.

"Getting the most out of data" has been Cloud1's statement for several years. Tuomo still endorses the core idea embodied in this phrase, which might be somewhat familiar. He also elaborates on this core concept through the development of the Cloud1 Data Hub concept and skills. This approach indicates a focus not just on data collection and management, but on maximizing the value and utility of data in meeting customer needs and addressing business challenges.

Cloud1 Data Hub – From Words to Actions 

Tuomo emphasizes that "getting the most out of data" doesn't necessarily mean embarking on grandiose data warehouse projects. Instead, it's about making data easily, quickly, and controllably available where and when it's needed: For one user, data may fuel reliable analytics; for another, it might enable new business opportunities; and for a third, it could lay the foundation for process automation and productivity enhancement. The common denominator and value creator in all these scenarios is data, so it's natural to center activities around it.

Many in the industry talk about nobly harnessing data for the greater good, but conceptualized and replicable models are often still lacking. It's easy to end up in a situation where one data project after another solves the same problems and, while often reaching a good outcome, does so only in its narrow context.

Tuomo sees the Cloud1 Data Hub concept as an exception. In this concept, processes and business objectives are examined purely from a data perspective, rather than through the lens of integration, data warehousing, or organizational biases. While the central technology, the Azure Data Platform, is highly capable in its role, it alone doesn't solve the age-old problem of data silos. That's why a concept is needed that ties together architecture, governance, technology, and development methods. Putting data at the center is also a shift in thinking and requires a willingness to innovate; otherwise, there's a risk of merely repeating the past.

"There must be a clear vision for the utilization of cloud and data. Otherwise, there is a great risk of implementing new things in old ways", Tuomo Riihentupa, Cloud1

Not everything has to be done all at once; needs vary from large to small, data usage requirements can differ significantly, and the lifecycles of data solutions can be short or long. The Cloud1 Data Hub concept responds to these challenges, and by adopting it, it's easy to elevate data to its rightful place at the center of everything.

Tuomo Riihentupa | Cloud1

Full Stack Developer Equivalent in the Data World?

The principle of "getting the most out of data" guides not only technology and management models but also the development of people's skills. In customer organizations, challenges in utilizing data often manifest as a gap between units that consume data and those that produce it. A significant cause of this gap can be traced back to people, as job roles inevitably lead to a one-sidedness in skills. Suppliers must be wary of falling into the same trap with different competency groups and organizational structures. In data work, versatility and the willingness to step outside one’s designated area are key to success. Therefore, it's advisable to reassess and refresh old job demarcations and roles.

It's time to refresh the traditional cost center thinking in role assignments”, Tuomo Riihentupa, Cloud1

With a broad skill set, the same level of versatility, flexibility, and foresight achieved in application development can be attained in data development. To solve a specific need or challenge, it shouldn't be necessary to bring in many individual specialists, like an ETL developer, a data modeler, an integration architect, and a BI guru. If these skills are found in one person, you can speak of a Full Stack Data Engineer, whose skill set is a winning combination in client projects and highly valuable in the job market. While there is still a place for deep specialists, the trend is shifting towards pursuing more comprehensive skills in data development as well. Skills need to match needs, and roles must evolve with the world – fortunately, this has already been internalized at Cloud1 well in advance.