Blog

The third part of this series is about Angular Services. We’ll see how we can use a service in a component and look at the basic mechanisms of dependency injection.

From the basics to the first features: How do you create Angular components that can exchange data with each other? That’s what the second part of the big Angular tutorial is about. We’ll also take a look at how to filter the output data. Angular is designed to make web application development easy, efficient, and scalable. This is the declared goal of the framework I present in this article series. After we’ve already taken a look at the history of Angular, the creation of a project, and the basic elements of the Angular CLI in the first part, we will... Read More

Progressive Web Apps are touted everywhere as the only true solution and the app of the future. Some decision-makers and developers are tempted to dismiss native apps outright as a dusty bridging technology. But whether it is advisable for a company to switch from native apps entirely to PWAs depends on many different factors that require closer examination. Let’s take a bird’s eye view of the decision-making process.

JavaScript projects are complex, with many homegrown problems. This article explores some of these problems and their causes. We will discuss how you can find a way out of the complexity trap can be found with the help of modern tools and standards, such as Snowpack and ESM.

As a web developer, how can I use DevOps for myself? Where does DevOps begin and what does it involve? How do I design my daily routine to achieve the maximum benefit for software development and the warranty of application operation? This article shows how easily we can use React and GitLab to create a Single Page Application (SPA), test it, and put it into production.

A backend programmed in Node.js and executed with Docker is not much use on its own if it cannot be accessed for lack of a client. However, it does not have to have a graphical user interface. A command line tool will do - and is practical in many cases. How does it work?

Anyone developing an application in Node.js not only has to deal with the code itself. It also involves connecting infrastructure, including databases, and the execution layer with Docker. How does that work?

The case for asynchrony in JavaScript is clear: Callbacks are evil and Promises are the only correct solution. No, actually async/await is the solution, but this relies on Promises, which involve some callbacks. So not everything is as clear as it seems. In the following, we will clarify why asynchronicity is necessary.

When developing with Node.js, it is not only important to write the actual code, but also to ensure quality. In addition to conscientious code structuring, this also includes applying code guidelines and executing automated tests.