A requirement that most of us have probably tackled already, or if not, most likely we will have in the future, is the migration of existing functionalities to a new and modern technology. Although there are multiple reasons why such a migration can be beneficial, we will try to expose those that have been most relevant to us, but first let's see which was the initial context. In our case, the goal was to migrate the existing functionalities from a monolithic application to microservices on the backend side and to microfrontends on the frontend side. Our objective for this article is to present the challenges encountered along the way and at the same time the solutions we have chosen.

When talking about a startup most of the people think about a small garage company with the goal to build a sustainable business, developing a new disruptive product or service. However, in the automotive industry, these kinds of startups are rather rare. The market is split between big companies with mostly a clear and stable business case. In this environment, a “startup” is frequently related to the question: How can a new business (new customer/partner or product/service) be raised and scaled in an already established organization? In this context, the new business could become a startup within the organization.

Our story begins in the seventeen century with Netherlands, the most advanced country of Europe at the time. Because of the adoption of Reformation in the preceding century (specifically the Calvinist ideology) and the proximity of the Atlantic Ocean, the Dutch people went through unprecedented developments. They were at the forefront of the geographical discoveries and fared brilliantly against Spain, the most powerful state at the moment, winning their formal independence from them after a struggle that lasted 80 years. But their most important discoveries with lasting impact even today were in the economic realm. They implemented the first modern stock-exchange and discovered first that a company could be split in tiny tranches called shares (societate pe actiuni in Romanian) which could be traded freely by all people, who thus became owners and sellers of small parts of a company. That company was the first mega-corporation, the Dutch East India Company.

In this article we’ll present the fundamentals of Solidity, the language of choice for developing Smart Contracts on Ethereum or Ethereum cloned blockchains. The theory and examples presented in this article are inspired primarily from two books. The first one, “Mastering Ethereum”, is written by two British computer scientists: Andreas M. Antonopoulos, a very known popularizer of Bitcoin and Gavin Wood, the creator of Solidity itself. The second book “Building Ethereum Dapps” written by Roberto Infante at Manning is my personal favorite: it is easy to understand but also tackles very complex aspects of Solidity and of the Ethereum ecosystem.

Negotiation is the process where a series of strategic discussions happen between two parties with the purpose to reach an agreement that satisfies all the stakeholders. By negotiating, all involved parties avoid a potential argument and find a common ground where they reach a consensus. Remember, in case one party must give up more than the other on its list of demands, then a compromise occurs in that negotiation versus a consensus where both parties give up and accept the outcome on the same level.

The performance can be translated the way we manage to accomplish our daily tasks which are mapped to our company’s­­ goals and vision. The performance is usually brought into the light each time when we talk about employee evaluation – how well he managed to execute and deliver the expected work activities.

We live in a world of constant development and change. But, how can we adapt to all of these changes? The answer is quite simple, we must bring Digitalization in Engineering, Manufacturing and Industrial IoT. In this paper, we would aim to dive-in in a solution that could help us reach the desired level of digitalization, by changing the way we see the “world” and by changing the way the computers understand the data that they are manipulating.

Bosch Future Mobility Challenge (BFMC) is an international student competition organized by Bosch Engineering Center Cluj that challenges teams of 2 to 5 students and a university mentor to demonstrate - after 6 months of development - the capabilities of the 1/10 scale vehicle provided by us, to navigate in a designated environment simulating a miniature smart city. Through this competition, we want to introduce the students to the automotive and autonomous driving (AD) fields, to see the challenges and complexities that these two face.

Ovidiu Mățan: People know you as the father of BDD. How did all of this start out?

Dan North: I was working as a developer at ThoughtWorks, a global software consultancy, back in 2003. We were advocating an XP-like delivery model, using practices like iterations, user stories, pair-programming, continuous integration, test-driven development, etc. The big sticking point seemed to be TDD - the developers thought that writing tests was the work of lowly testers. The testers didn't like the idea of programmers writing tests either - maybe because they didn't think the programmers knew how to write tests, maybe because they were afraid they would be out of a job!

Steganography is a technique whereby information is hidden inside otherwise innocuous- seeming information to preserve its secrecy. Etymologically, it comes from the combination of the Greek word steganos (which means concealed) and graphia (which means writing).