
Łukasz PawełczakScaling an Angular application: Build fast, fix less
A small Angular project feels light. Two friends push code, handle feedback, and ship features in a single afternoon. Then users arrive. Feature requests pile up.
4 min read
13 articles

Łukasz PawełczakA small Angular project feels light. Two friends push code, handle feedback, and ship features in a single afternoon. Then users arrive. Feature requests pile up.
4 min read

Łukasz PawełczakObservables and RxJS are considered the cornerstones of the Angular framework. The RxJS library allows us to create our applications in a reactive way. Nevertheless, observables come with one pretty large downside
7 min read

Łukasz PawełczakOne of the most popular methods of communication between components is by inputs. In the community, they are known for being easy to use, understand and implement. Is this really true?
9 min read

Łukasz PawełczakAngular is known to provide complete solutions out of the box. It gives developers all the tools alongside the guideline on how to create applications. Overall that makes it more strict than other solutions like React or Vue. In my opinion, Angular is still very flexible
5 min read

Łukasz PawełczakDoes the module returned by the static forRoot method come with the providers declared in @NgModule() decorator? I thought that is an interesting question because Angular can act either way. The method forRoot returns an object that implements ModuleWithProviders which consists of a reference to an Angular ngModule and a list of providers
5 min read

Łukasz PawełczakWorking in an advanced frontend application requires us to use patterns. The main benefit of them is that they allow many programmers to work on one codebase. Patterns introduce aspects of common language and allow us to better understand how the code works. Some of them are universal like Singleton, Factory or Builder, but there are also others that may be less standardized, one of them is the Container Presenter.
9 min read

Łukasz PawełczakLike most of you, I work in a team of a couple of programmers and our responsibility is to handle a few big Angular projects. In order to keep our project's codebase clean, readable and without any bugs we try to use verified Angular patterns. One of them is obviously the Smart and dumb components pattern
6 min read

Łukasz PawełczakRecently I had the pleasure of doing a small refactor in an Angular project. Refactor is one of my favorite things to do so I was glad that I had a chance to do it. It wasn't anything especially complicated, a basic name change, but the interesting part is that after my modifications our unit tests started to fail. I was confused by the whole situation so I started to unravel the mystery that was behind the failing tests
5 min read

Łukasz PawełczakTesting the RxJs library may require programmers to change their way of thinking as it brings lots of challenges. It is agnostic from any JavaScript framework and has lots of features which makes it a very popular library amongst frontend technical stack.
3 min read

Łukasz PawełczakEvery good programmer should know this famous Robert C. Martin concept "Good architecture allows us to delay making serious decisions as long as possible". This quote should be taken into consideration every time an architectural decision is being made. It is especially important in today's frontend development where everything is rapidly changing.
9 min read

Łukasz PawełczakThe smart and dumb components pattern is a very commonly used practice. I like to call it pure and impure, I feel that it makes more sense when you take functional programming into consideration. There are also other names for this pattern: "Container and Presentational", "Advanced and Simple".
10 min read

Łukasz PawełczakAt the beginning of the creation of the Angular framework, the angular team made a great choice by going with the component pattern. Based on what is going on in the JavaScript world this a direction all the big players are taking (Vue, React, Svelte). The component seems to perfectly fit the nature of HTML itself. This global movement caused components to be the focal point of the angular framework and that is why they are one of the most complex features of it. You can easily say they are the backbone of every application...
11 min read

Łukasz PawełczakStandard angular service is called singleton by default, but can you actually call it singleton? The angular dependency injection mechanism is one of the best parts of the framework...
9 min read