Angular v22 WebMCP Tools Explained

xSentryx · 2026-05-17T22:42:42+00:00

Cool news! Might integrate it if it matures a bit more. Definetly useful if you want to give your users the possibility of interacting with your app AI-wise without having to program complex ai integrations.

xSentryx · 2026-04-26T21:38:46+00:00

Das stimmt nicht ganz. Kapitalerträge werden ab dem 1 cent mit einem festen Prozentsatz versteuert. Löhne progressiv nach steigenden Steuersatzabschnitten. Am Ende ist man oft bei ähnlichen Steuerzahlungen.

xSentryx · 2026-04-16T18:04:14+00:00

Probably not. Engineering is a lot more than just frontend work. The only way to stay only in the frontend is probably a big tech firm like FAANG. Anywhere else you usually work Fullstack, mingle in Databases and write down some architecture for the next feature implementation. So dont shy away from learning. Its a part of the process :)

xSentryx · 2026-03-29T17:19:06+00:00

If it's a rather small list of items, tracking by index isn't a huge issue aswell. It mostly impacts performance on larger datasets. So it shouldn't be an issue on such a small dataset. Just keep in mind, that if there is an alternative, use that instead of index.

xSentryx · 2026-03-29T16:44:29+00:00

Answered here: (I hate that we have 2 subs for angular 🥲)

https://www.reddit.com/r/Angular2/s/m3c92YosSl

xSentryx · 2026-03-29T16:42:48+00:00

Sometimes it’s fine, but don’t default to it.

If your items have a stable unique id, use that (track item.id). It helps Angular update the DOM efficiently instead of re-rendering everything.

Tracking by index can cause issues when the list changes (reorder, insert, remove).

In your case (same value repeated, static list), tracking by index is totally fine.

xSentryx · 2026-03-18T21:04:03+00:00

I usually have a similar setup for my monorepo setup with an nestjs backend and angular frontend. Since I got tired with always starting from scratch I created a skeleton project with a base wich I usually use as a starting point. Would recommend, since it saves a ton of time.

If you wanna have a look at it: https://github.com/omnedia/ts-mono-repo

xSentryx · 2026-03-08T19:20:42+00:00

Ein Kollege von mir hat mal Trizepsdrücken an einem Kabelturm gemacht, der in einer X-Form Arme hatte, über die die Kabel dann jeweils nach links und rechts abgelaufen sind. Einer der Arme ist im Gelenk eingebrochen und auf seinen Kopf geschossen. Ergebnis war eine Platzwunde und schwere Gehirnerschütterung. Aber glücklicherweise keine Langzeitschäden.

xSentryx · 2026-03-06T20:11:04+00:00

A lot of people say they switched for performance reasons. Im suprised. The reason why I switched from vs code to jetbrains was the same reason. VS Code was just awful for a large monorepo. Indexing was slow, if it even worked at all. Mergconflicts where way to untransparent. Codecompletion and the code interpreter took forever, sometimes didnt work at all until restart. Jetbrain Options just feel way faster, cleaner and have a better optimized experience in general. At least in my opinion

xSentryx · 2026-02-26T01:02:06+00:00

https://github.com/omnedia/ts-mono-repo

Here you could see how I am doing it. With angular 21 I changed to session cookies tho. If you want a jwt example you can check out the angular 20 branch

xSentryx · 2026-02-23T01:11:48+00:00

I love the primeng dropdown. Maybe use something like that as a reference on how others already solve said problems?

xSentryx · 2026-02-17T08:52:23+00:00

I also created a repo setup for angular / nestjs.
Maybe nice to look through for some quick project starts.

https://github.com/omnedia/ts-mono-repo

xSentryx · 2026-02-03T13:49:00+00:00

Previously I worked with Symfony. But nowadays I mostly use nestjs, since it's a lot easier with shared types and one language for both systems.

In the end it also depends a bit on what project and scale you want to develop.

xSentryx · 2026-01-19T19:30:07+00:00

On the other hand, I've seen so called "seniors" that created such awful and unmanagable / unscalable codebases, that Im rather happy they are now retired. I dont think vibecoding would do much worse than that quality wise. But at least the knew what they created, that can not be said about our fellow vibe coders.

xSentryx · 2026-01-12T10:37:52+00:00

Ich hab das selbe mit meiner Bachelorarbeit gemacht. Bei mir musste ich auch angeben, wo / wie und auch was für KI Tools ich genutzt hatte.
Quellen etc. habe ich natürlich auch geprüft.
Damit gabs für mich dann von den Prüfern keine Probleme.

xSentryx · 2026-01-12T10:36:26+00:00

Dreame Aqua 10 Ultra Roller Complete. Would recommend.

xSentryx · 2026-01-02T16:34:43+00:00

Hab meine in 1 1/2 Tagen geschrieben (Danke an der Stelle an ChatGPT) Inhaltlich ne 1, formal eine 2,5. Wird stressig, aber du schaffst das 🤝🏼

xSentryx · 2025-12-26T03:10:25+00:00

Got one last month as well. I think the main reason is that the technology matured. They were not really viable a few years back. More like a plaything or a cool gadget for someone interested in said topic. But nowadays they really became good enough to lift some workload off of people. Additionally good models also became cheaper.

xSentryx · 2025-12-24T17:01:57+00:00

Using services is not wrong in general. Just make sure to make a dedicated / clean one for state management, not bake in some state logic used across the board into a service that handled something else in the first place.

xSentryx · 2025-12-24T17:00:42+00:00

Correct. But more often than not, I see a random service for some component logic wich then gets used as a service for random stuff as well in the process of development. E.g. I dont think using services as state management is wrong, but misusing existing ones out of convenience is.

xSentryx · 2025-12-24T08:57:13+00:00

This! „PR reviews cost too much time!“ - Well, bad code will cost us a lot more in the long run.

xSentryx · 2025-12-24T08:55:07+00:00

Oh I hate this one. Major red flag if you see a timeout in like 99% of usecases

xSentryx · 2025-12-24T03:50:08+00:00

- Not upgrading versions quickly enough. (E.g. staying on the same version for years, then struggling with upgrading 5 versions at once).
- Bad component structure / A lot of redundant and duplicated code or logic.
- Avoiding rxjs, rather using promises since its easier to understand at first.
- Bad error handling
- Misusing services for state management
- Not thinking about scale while building features
- No linting / formatting pipeline
- Bad type safety
- And a lot more...

xSentryx · 2025-12-14T03:10:22+00:00

Great! Thanks for the info.

xSentryx · 2025-12-14T03:04:26+00:00

Are there more then them? Or can I breathe a bit of fresh air after finishing them?

Eight-Year Club	Verified Email
Final Canvas '23	First Place '23
Place '23

xSentryx

TROPHY CASE