It may sound crazy, but CrossBreeze was born from a certain laziness. Let’s start by saying that we like our work, but laziness in the sense of not wanting to do the same thing 100 times. And not only us, but also most data engineers don’t feel like doing that. If we do the same thing 3 times, we start thinking: can’t it be done smarter? It certainly can! With CrossBreeze we have found a different way of working and we would like to tell you more about it. <\/p>\n\n
Harmen and Willem, the founders of CrossBreeze, met each other through a joint project. They soon discovered that they shared the same vision and working method. Or actually it was more of a frustration. Harmen: \u201cWith every new project or new client I had to reinvent the wheel. I couldn\u2019t take the tooling that I had created with a previous assignment with me.\u201d So we asked ourselves: Can\u2019t we do it smarter? Can we house the tooling somewhere, so that we can use it at different organizations? The answer to this question was the start of CrossBreeze. <\/p>\n\n
If you don’t want to do something 100x, you have to automate it. So we started developing and selling tools for this. We soon discovered that tools are difficult to sell, because the users (data engineers) have to change their working methods. And they are not always open to that. Moreover, BI managers had difficulty seeing the added value, because the product is technical and abstract and only delivers added value in combination with a process change. So we asked the question again: “Can’t it be done smarter?”. In fact, our added value is not so much in the tools we develop, but in the working method we apply: model-driven development and code generation<\/a>. This is also why organizations come to CrossBreeze. Our working method ensures that organizations accelerate the development of their data solutions and improve their quality. And with this approach, they can simply use their existing technology and architecture. <\/p>\n\n We now guide teams in applying our method<\/a>. In short, this means that there is a better demarcation of functionality and technology. Technology is recorded in templates (patterns) and functional logic in a technology-independent model. Based on the model and the templates, the software is generated using an engine. In other words: writing the code is robotized. This also means that when you want to change technology, you don’t have to rebuild everything. You then only develop templates for the new target technology, while the functional model remains unchanged. And that saves a lot of time! <\/p>\n\n We want companies to experience the CrossBreeze approach as a breath of fresh air. That is where the name CrossBreeze comes from. With our approach, we apply data engineering at a different level, a way that makes work much more fun! In addition, a breath of fresh air comes through the team: people start working in a different way and different roles are needed. The focus of the work shifts from programming to modeling. This means you get more modelers in the team and you have a smaller group of developers left to set up and maintain the technology-specific components. Such a transition naturally requires something from an organization, but CrossBreeze guides you through it without any worries. <\/p>\n\n Our customers often see us as a source of information and come to us when they get stuck, for example. They like to brainstorm with us, which is very characteristic of CrossBreeze. We see ourselves as a knowledge holder of model-driven data solutions and therefore provide training and consultancy in addition to best practices. In short, we provide the complete picture for a successful transition to model-driven data engineering. <\/p>\n\n So, could your organization use some speed and efficiency? Then meet Willem<\/a> and Harmen<\/a>. They will be happy to show you how to gain insight from your data faster. <\/p>\n","protected":false},"excerpt":{"rendered":" It may sound crazy, but CrossBreeze was born from a certain laziness. Let’s start by saying that we like our work, but laziness in the sense of not wanting to do the same thing 100 times. And not only us, but also most data engineers don’t feel like doing that. If we do the same […]<\/p>\n","protected":false},"author":6,"featured_media":0,"parent":0,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":{"content-type":"","footnotes":""},"hf_cat_page":[47],"class_list":["post-2968","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/crossbreeze.nl\/en\/wp-json\/wp\/v2\/pages\/2968","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/crossbreeze.nl\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/crossbreeze.nl\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/crossbreeze.nl\/en\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/crossbreeze.nl\/en\/wp-json\/wp\/v2\/comments?post=2968"}],"version-history":[{"count":0,"href":"https:\/\/crossbreeze.nl\/en\/wp-json\/wp\/v2\/pages\/2968\/revisions"}],"wp:attachment":[{"href":"https:\/\/crossbreeze.nl\/en\/wp-json\/wp\/v2\/media?parent=2968"}],"wp:term":[{"taxonomy":"hf_cat_page","embeddable":true,"href":"https:\/\/crossbreeze.nl\/en\/wp-json\/wp\/v2\/hf_cat_page?post=2968"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Timeless and technology independent<\/h2>\n\n
It feels like a breath of fresh air<\/h2>\n\n
Your own knowledge holder<\/h2>\n\n