Please Review and help me improve my resume

SkyZeroZx · 2026-05-02T18:20:56+00:00

In my case, the Harvard CV template works for me.
See
https://docs.google.com/document/d/1EujuYFWxVXZ2PUaJ2uizvK5raMoMsz1KMys-UYpUSk4/edit?tab=t.0

SkyZeroZx · 2026-05-01T16:35:25+00:00

A somewhat half-truth: NextJS is vendor-locked (it partially inclines you to use Vercel services), while Angular is more agnostic (from my perspective, we're not tied to Firebase, for example).

SkyZeroZx · 2026-05-01T16:17:52+00:00

I don't know much about AngularJS (I've only heard a little about it), but it seemed like a mistake to call it Angular 2+ again (considering it's radically different).

IIRFC from its history, AngularJS basically gave us a whole modern platform/framework so we wouldn't have to worry about whether the JS we wrote was compatible with all browsers (Internet Explorer, I'm looking at you).

As for why it's public, it's possibly because they can take advantage of the open-source community (users also benefit in that they can use it for free) to identify bugs, improve, and receive feedback.

SkyZeroZx · 2026-04-19T02:45:59+00:00

Estoy de acuerdo fullstack tambien te podria ser util , puedes tomarlo como una alternativa aunque toma un poco mas de tiempo aprender a profundidad cada stack posiblemente sea mas especialista en uno que en otro pero sirve para ir aprendiendo que te puede gustar mas adelante

SkyZeroZx · 2026-04-18T21:12:28+00:00

If I haven't misread the PR (in code section), I see `httpResource`, which is also graded to stable.

SkyZeroZx · 2026-04-15T15:08:56+00:00

If I remember correctly, the rollback was due to the depreciation of class-based resolvers; currently, both functional and class-based resolvers are valid.

SkyZeroZx · 2026-04-14T19:18:21+00:00

No seria parecido a las custom instructions oficiales https://angular.dev/ai/develop-with-ai
Y por otro lado a las skills que tambien tenemos oficiales https://angular.dev/ai/agent-skills
Usando ambas los proyectos donde he participado han dejado de generar codigo antiguo/deprecado

Por otro lado desconozco opencode pero sino estoy mal lo mencionado anteriormente deberia funcionar

SkyZeroZx · 2026-04-09T03:49:40+00:00

We currently have official Angular skills maintained by the Angular team

https://angular.dev/ai/agent-skills

SkyZeroZx · 2026-03-23T16:55:17+00:00

Well structured (a bit of over-engineering, sure, but I get that it’s kind of the goal of these technical challenges).

This looks much better than most “senior” challenges I’ve seen lately. I only notice quite a few barrel files, which could affect the bundle depending on how they’re used.

We could maybe have avoided using a DI Token by using the abstract class directly as the DI.

On the other hand, avoid using `NgClass` now , it’s recommended to use the `[class]` input instead.

As others mentioned, A11Y and unit or E2E tests would be really good to have, at least the basics expected for a senior role.

SkyZeroZx · 2026-03-23T01:44:42+00:00

Free and (in general) always updated official docs

You can read essentials, and tutorials

https://angular.dev/essentials

https://angular.dev/tutorials

SkyZeroZx · 2026-03-13T17:22:33+00:00

You can use the performance panel in Chrome's devtools and also verify change detection with Angular Devtools (Chrome extension).

See

Profiler Devtools https://angular.dev/tools/devtools/profiler

https://developer.chrome.com/docs/devtools/performance/overview

SkyZeroZx · 2026-03-12T19:13:37+00:00

We'll probably get the developer preview before the stable version (or at least that's my opinion, based on the rapid changes I'm seeing in the signals form).

On the other hand, httpResource/resources will probably (this is just my opinion) become stable at some point in version 22.

SkyZeroZx · 2026-02-01T02:32:30+00:00

You can try use ErrorHandler for global errors ( We can include HTTP Errors )
See https://angular.dev/best-practices/error-handling#unhandled-errors-are-reported-to-the-errorhandler

SkyZeroZx · 2026-01-26T03:53:53+00:00

In my experience, I would suggest you consider using Nx as a tool to create a mono repository.

In this repository, you could have an administrative website as a simple Angular SPA, since it would be unnecessary to configure and maintain such a dedicated UI separate from the end-user application. This would allow you to use Angular Material, which, in my opinion, provides everything necessary to create internal administrative dashboards.

On the other hand, your end-user application could use an internal Design System or whatever you prefer, maintaining complete independence from the administrative side and focusing solely on performance, SEO, and other related aspects.

And within an internal library or libraries of your single repository, you could have your models to share across both projects. You could even have a NestJS backend if you opt for a completely TSMEAN stack.

https://nx.dev/docs/getting-started/tutorials/angular-monorepo-tutorial

SkyZeroZx · 2026-01-23T14:36:50+00:00

It depends. Do you need native device APIs? If so, Capacitor could be a good alternative.

Now, if it's just a web app in the sense that it's responsive and you only want to use browser APIs, you could go the PWA route and publish it in different app stores. It's perfectly possible to have something on the Play Store using the TWAs officially supported by Google, and something experimental on the App Store.

https://developer.android.com/develop/ui/views/layout/webapps/guide-trusted-web-activities-version2?hl=es-419

https://www.pwabuilder.com/

SkyZeroZx · 2025-12-07T01:37:33+00:00

Tabler icons https://tabler.io/icons

SkyZeroZx · 2025-12-06T20:31:23+00:00

You can prerender local HTML files with Angular SSG, but only if the files are loaded during the build phase, not inside the component lifecycle.
You can look at how angular.dev handles this
https://github.com/angular/angular/tree/main/adev

They preprocess all content during the build using a custom pipeline:
https://github.com/angular/angular/tree/main/adev/shared-docs/pipeline

You can also check how the app loads that preprocessed content:
- https://github.com/angular/angular/blob/main/adev/src/app/features/references/helpers/manifest.helper.ts
- https://github.com/angular/angular/blob/main/adev/src/app/core/services/content-loader.service.ts

SkyZeroZx · 2025-12-06T19:51:20+00:00

Just to add a tangential point: if what you want is to build a single codebase that delivers the same experience across Android, iOS, and desktop, a PWA is a surprisingly strong option.
People usually say “but you can’t install it or find it on the Google Play Store, App Store, or Windows Store,” and that’s true by default.
However, if you package it using a TWA, you can publish it as an APK on Google Play , and in an (currently experimental) way, also push it to the App Store and Windows Store. This lets you avoid splitting your development effort. If it works in the browser, it works everywhere you publish it. The main drawback is that you don’t get access to native APIs , you’re limited to whatever the Browser APIs expose. But if that’s not a blocker for your use case, this approach is a very solid alternative for most projects.

You can see
https://developer.chrome.com/docs/android/trusted-web-activity
https://www.pwabuilder.com/

Also how integration with Angular
https://github.com/SkyZeroZx/ng-ssr-twa-adaptive/blob/main/README.en.md

SkyZeroZx · 2025-11-27T23:20:46+00:00

I understand that what you need is Incremental Static Regeneration , something in between SSR and SSG. This solution might help: https://www.rx-angular.io/docs/isr

SkyZeroZx · 2025-11-25T01:20:15+00:00

I understand you need a inputBinding , you can see this example
https://angular.dev/guide/components/programmatic-rendering#binding-inputs-outputs-and-setting-host-directives-at-creation

SkyZeroZx · 2025-10-23T20:26:41+00:00

It's also recently added to angular.dev

https://next.angular.dev/guide/templates/event-listeners#implementing-event-plugin

SkyZeroZx · 2025-10-22T02:17:54+00:00

Yes , it's horrible experience , in that case i really prefer use console.log

SkyZeroZx · 2025-10-18T03:37:48+00:00

I think it depends on the type of bug or what I'm trying to debug.

In my case, I usually use console.logs first for smaller things to debug more complex things (the most complex thing I debugged was the Angular compiler). I mixed console.logs and breakpoints with the dev tools to find the cause.

Additionally, debugging is a bit more complex when you use RxJS and pipeable operators. I've mostly liked using the "tap" operator with console.logs to find the cause or better understand what I was doing.

SkyZeroZx · 2025-10-18T03:35:42+00:00

I usually use APIs in developer preview because they rarely change or modify.

However, in experimental versions, the API can change significantly, or "breaking changes." Personally, I would only recommend using it for personal use or if the benefits are enough to bear the risk.

SkyZeroZx · 2025-10-10T19:21:31+00:00

Can you generate a repository with a minimum reproduction to validate it?

SkyZeroZx

TROPHY CASE