Khizer Rehan

Frontend Engineer

[Khizer Rehan @KhizerDev]

Kyaaa baat hai Bhai...... Zabardast

- Did you check what after sale services they provided ?
- Did you know what Quotation they have given?
- Did you know what support they have provided (Sending Team with 0 Equipment) and Just sending team keh bahi inko chup Karwa doo.

Company Response = Chaknah

Now zalalat horahi hai. They even don't have the part they needs to be replaced and Quoter 3.5 Million Rs for Batter replacement

Wah Kya baat hai ( After Sale Services ki)

Please you are respectful and most listened voice don't portray your image in wrong direction.

Thank you

[Khizer Rehan @KhizerDev]

@FarzaTV Nice Analogy!

IMO, CS fundamentals will continue to matter, and experienced engineers who’ve spent years experimenting, troubleshooting, and building a strong foundation are best positioned to benefit the most from LLMs.

[Matthieu Riegler @Jean__Meche]

Signals Form will be promoted to stable in v22.

#Angular

https://t.co/rYoA2kcbBP

[Khizer Rehan @KhizerDev]

Why I did changed from "string" to TemplateRef

@ ContentChild('labelTag') uses a fixed template name as a shared contract between parent and child, so every <custom-component> must define #labelTag, which can lead to duplicate names in the same template when multiple siblings exist.

@ ContentChild(TemplateRef) has no naming contract and simply picks up the projected template per instance, so each <custom-component> resolves its own content independently with no collisions.

FYI: This approach still works in case each component has 1 template

This works beacuse

- Angular projects that ng-template into the child component.

- Each <custom-component> instance has its own projected content scope runs ContentChild independently resolves whatever template exists inside it

Instead, it works like this per component instance:

<custom-component>
<ng-template> A </ng-template>
</custom-component>

<custom-component>
<ng-template> B </ng-template>
</custom-component>

IMO, that still be problematic incase of multiple templates within same tag

Angular will try to "FIRST" matching TemplateRef found

<custom-component>
<ng-template> A </ng-template>
<ng-template> B </ng-template> <!-- duplicate -->
</custom-component>

[Khizer Rehan @KhizerDev]

TIL: #Angular

While working on the codebase, I ran some existing Angular migrations
(https://t.co/vSo6wecgjt). Most files were migrated successfully, but a few template files were not updated due to control flow issues. I found that this was related to the @ ContentChild usage with a magic string if a template contains multiple ng-template elements with the same @ ContentChild reference variable, the migration script fails to process them automatically.

Angular GitHub references:
PR #53204: fix(migrations): Update CF migration to skip templates with duplicate ng-template names#53204

[Khizer Rehan @KhizerDev]

@ ContentChild('tabLabel') label!: TemplateRef&lt;any&gt;

Changed to

@ ContentChild(TemplateRef) labelTemplate: TemplateRef&lt;any&gt;;

[Khizer Rehan @KhizerDev]

Angular Errors Encyclopedia
TIL: https://t.co/WifZcO8GIn

#angular

[Khizer Rehan @KhizerDev]

Focus on business priorities, not just technical perfection. Align with your org’s goals even if it means compromising on your ideal architecture to show reliability and impact.

#Business #Revenue

[Khizer Rehan @KhizerDev]

This is a great improvement rest

IMO,@Service() feels like a nicer, more semantic wrapper over @Injectable({ providedIn: 'root' }) less boilerplate and more aligned with inject()-based DI.

[Matthieu Riegler @Jean__Meche]

Angular will introduce a new decorator in v22: @Service

- Root by default
- inject() only

It will stream line how we define services and reduce even more the boilerplate.

https://t.co/zzFHs6F2YY

[Khizer Rehan @KhizerDev]

Linux Kernel 7.0 shipped 🚀

https://t.co/VbmmP20L3d

As someone new to Docker/Kubernetes, this caught my eye 👇

Huge improvement in container creation performance (~40%) thanks to Open Tree Namespaces.

Benchmark (60s window):
• pivot_root: ~73K containers
• open_tree: ~109K containers

That’s a massive win for container heavy workloads 🐳📦

Sources:
- https://t.co/5F2RfXeIjd
- https://t.co/k7kLLo7Ean

#Linux #Kubernetes #Docker #Containers

[Khizer Rehan @KhizerDev]

The Winner’s Formula:

#motivation

Most people quit after a few losses.

They try once… fail… and take it personally.
Try again… fail… and start doubting themselves.
After a few more setbacks, they stop completely.

Not because they’re incapable—
but because they expected it to be easy.

They thought success meant getting it right quickly.
They thought winning meant avoiding failure.

That’s the mistake.

Because failure isn’t the opposite of success—
it’s part of the process.

Every missed attempt teaches you something.
Every loss sharpens your judgment.
Every setback builds resilience.

But only if you stay in the game.

The ones who win aren’t the ones who never fail.
They’re the ones who refuse to stop.

They keep showing up.
Keep adjusting.
Keep learning.

While everyone else is sitting on the sidelines,
overthinking, doubting, and waiting for the “perfect moment.”

There is no perfect moment.

There’s only repetition.

Trial and error.
Wins and losses.
Progress built over time.

And the longer you stay consistent,
the more your odds start to shift in your favor.

That’s how momentum is built.

Not from one big breakthrough—
but from refusing to quit after multiple failures.

So stop chasing perfection.

Stop expecting everything to work immediately.

Focus on staying in the game long enough to figure it out.

Because the man who keeps going,
even when things don’t work out at first…

is the man who eventually becomes unstoppable.

If you’re ready to build that level of persistence, discipline, and winning mindset—

#copied

[ThePrimeagen @ThePrimeagen]

if only there was a graph that could encompass this information in a more easily digestible way.

also, constant time taking time is funny in a way that i thought not possible

[Claude @claudeai]

Introducing Code Review, a new feature for Claude Code.

When a PR opens, Claude dispatches a team of agents to hunt for bugs.

[Khizer Rehan @KhizerDev]

TIL:

Issue Faced:
I incremented a BusyCounter before an API call and decremented it in next.

But when the sources array was empty:

forkJoin([]) → completes immediately
❌ next never fires
❌ no complete handler

Resulted: BusyCounter never decremented → infinite spinner loop

#angular #rxjs

[Kubernetes @kubernetesio]

The Kubernetes Dashboard was officially retired and archived on January 21, 2026.

To continue providing a modern, extensible web UI for the community, the project now recommends transitioning to Headlamp.

Now under SIG UI, Headlamp is a user-friendly tool for managing and troubleshooting your clusters.

Check out the project and docs here:
🔗 https://t.co/7e4hDAOJFd

[Khizer Rehan @KhizerDev]

Basic #Linux Command to search recursively.

[fabian @fabianstelzer]

Documentary: non-technical founder discovers Claude Code

[Khizer Rehan @KhizerDev]

💯

[Enea Jahollari 🅰 @Enea_Jahollari]

ngxtension v7.1.0 version released 🎉

- added injectAttribute utility
- added SignalMap and SignalSet
- added injectLeafActivatedRoute
- added https://t.co/KPSNOO7FTq and https://t.co/nqgNKvHISg
- bug fixes (some related to SSR)

Check it out : https://t.co/NX2DSpOt8U