Let's continue our journey into LLMs and Gemini! In the previous article, we moved beyond simple text generation and learned: * how to force the model to speak our language using structured outputs (JSON schemas) * how to connect the model to our actual code and logic using function calling (tool us
Let's continue our journey into LLMs and Gemini! In the previous article, we learned * how LLMs generate text, what are tokens, what configuration parameters like temperature, topP and so on mean * how to create a Google Cloud project, get a Gemini API key, and use the SDK to make text generation re
Like it or not, we live in the age of AI, and it can be both exciting and frustrating. On one hand, AI can help us unlock almost unlimited capabilities for the apps we build; if in the past, tasks like image recognition or text classification could be a dealbreaker for the average developer, today,
Today, everyone, everywhere in the Angular community is talking about Signals. They are the new way to manage state and reactivity in Angular applications, promising a better way to build logic and a very much improved change detection. However, many are hesitant. And this is understandable! Not onl
Introduction Error handling is as much of an important topic as it is also hated, and even more so, overlooked. Of course, we all enjoy authoring cool features, fascinating animations and beautiful UIs, but not so much do we love writing a bunch of code whose only purpose is to save us when somethin
In a previous article, I have covered the new Resource API, which was added in Angular in version 19 as an experimental feature to promote better approaches with reactive programming. If you have not read that article and are completely unfamiliar with the Resource API completely, I suggest you eith
Angular is a very, very powerful framework, which means it has lots of features. Of course, everyone knows the essentials, like components, services, routing, etc. But obviously, almost every Angular developer has some features they've never tried, or even heard of. In today's article, we are going
There are millions of Angular projects out there, and we have undoubtedly encountered lots of poorly written code. Also, there are many "Angular Bad Practices" articles—I wrote several of them—but trust me, this is not one of them. Bad practices often involve phrases like "avoid too complex componen
Introduction Recently, I shared my experience migrating a large Angular application to standalone components in a Twitter thread. This sparked a lot of interest, so I expanded it into a more detailed guide. Migrating a complex Angular application to use standalone building blocks is a significant en
If you have been using Angular for a while, you may have heard terms like "reactive primitive", or "RxJS interoperability", or "declarative programming" a lot recently. I trust that you, at least on some level, understand what all of those mean; however, when it comes to real life, it is sometimes q
Angular v19 is all the rage these days! Of course, everyone talks about SSR improvements, like incremental hydration, linkedSignal and resource/rxResource APIs, and you can already find some articles about them in here: * Article on Resource API by myself * Article about porting the Resource API to
With the introduction of signals in Angular v16, the framework started a new path towards rethinking reactivity and change detection. Signals were a welcome and very popular addition. however, everyone understood that they are still in a raw state and more reactive primitives are needed to make them
Introduction Angular interceptors are a feature that is widely known, but seldom used aside from the most basic needs (authentication, authorization). However, there are lots of use cases when interceptors can be very useful. In this article, we will explore some interesting and very common scenario
There are many articles online about Angular best practices, or even best practices for components specifically. Of course, components are the most important building blocks of the framework, but we know that directives are almost as important, and when it comes to them, there are also certain patte
Angular is a very opinionated framework, with multiple different rules and solidified approaches that help developers easily navigate decisions within their projects. However, as with any tool, there is some variability, and the core team cannot, and, more importantly, will not make every single dec
Dependency Injection is a technique that we use every single day as Angular developers. It allows us to reuse things, access native constructs like HttpClient, retrieve data from routing, and much more. However, my general feeling has been that Angular developers often underestimate the capabilities
Original cover photo by Hansjörg Keller on Unsplash. In my previous articles, we covered access...
![Signals — [MEGA Article] - Superpowers with Directives and Dependency Injection](/assets/thumbs/bcc511c3ef.png "[MEGA Article] - Superpowers with Directives and Dependency Injection")
Introduction I have been saying this for a looong while: Directives are the most underutilized part of Angular. They provide a powerful toolset for doing magic in templates, and yet in most projects, it is used in the most common, "attribute directives that do some limited business logic" style. The
Original cover photo by Shyam on Unsplash. If we ask any Angular developer "What is the hottest...
Original cover photo by Jr Korpa on Unsplash. Lots of time has passed since I wrote my previous...
Original cover photo by Ivan Bandura on Unsplash. It's time for the 6th installment of this article...
Original cover photo by Carlos Alberto Gómez Iñiguez on Unsplash. On April 4th, 2023, the Angular...
Original cover photo by Pawel Czerwinski on Unsplash. Here we are, part 5 of our series dedicated to...
Original cover photo by Justin Wolff on Unsplash. Welcome to the fourth part of my exploration of...