If you've been working with signals in Angular, you probably may have felt this issue of signal calls not being type narrowed by Typenoscript. This issue also happens in normal Typenoscript code, because currently the function calls cannot be type narrowed.
There's currently an open issue in Github in Typenoscript repo, where you can give a thumbs up if you want this issue to be taken into consideration by the TS team. The more thumbs up we can have on the issue the better!
Issue link: https://github.com/microsoft/TypeScript/issues/57725
There's currently an open issue in Github in Typenoscript repo, where you can give a thumbs up if you want this issue to be taken into consideration by the TS team. The more thumbs up we can have on the issue the better!
Issue link: https://github.com/microsoft/TypeScript/issues/57725
❤1
https://www.theeuropeanengineer.com/p/how-to-think-about-money-if-youre?open=false#%C2%A7heres-what-you-need-to-know-about-european-tech-workers-compensation-in
https://docs.google.com/spreadsheets/d/1iTNwiAQ0s5iD6RqI7B30uWqQ8wNJqRnmHvxo5zRffu8/edit?gid=603717461#gid=603717461
https://docs.google.com/spreadsheets/d/1iTNwiAQ0s5iD6RqI7B30uWqQ8wNJqRnmHvxo5zRffu8/edit?gid=603717461#gid=603717461
Theeuropeanengineer
How to think about money - if you're a dev in Europe
What is money even for?
😭1
Forwarded from DevLoom
An effective architecture doesn’t just fit your application—it grows with it.
In this talk, we’ll explore how to design an Angular architecture tailored to your app’s current size, with a clear path for scaling as complexity increases. We’ll start small, with a single feature module, and progress step-by-step: splitting into sub-modules, grouping functionality into domains, and evolving toward a modular architecture. At the peak of this evolution, we’ll touch on microfrontends as a strategy for scaling teams and applications effectively.
Using Sheriff, we’ll also show how to enforce architectural rules, ensuring your codebase remains clean, maintainable, and scalable at every stage of growth.
In this talk, we’ll explore how to design an Angular architecture tailored to your app’s current size, with a clear path for scaling as complexity increases. We’ll start small, with a single feature module, and progress step-by-step: splitting into sub-modules, grouping functionality into domains, and evolving toward a modular architecture. At the peak of this evolution, we’ll touch on microfrontends as a strategy for scaling teams and applications effectively.
Using Sheriff, we’ll also show how to enforce architectural rules, ensuring your codebase remains clean, maintainable, and scalable at every stage of growth.
How to speed up your Germany "Einbürgerungstest" like a good )))
v1.0.0
PS: first install "Tampermonkey" Chrome extension and create a new noscript.
v1.0.0
$('head').append('<style type="text/css">.blinker-class{color:white;background-color:#0063a5;animation:1s linear infinite blink;border-radius:50%;margin:auto}@keyframes blink{25%,75%{opacity:.5}50%{opacity:0}}</style>');$(".t3instructiontext .t3borderless").find(".t3data[name='FARBE']").parent().addClass('blinker-class');PS: first install "Tampermonkey" Chrome extension and create a new noscript.
❤1
This media is not supported in your browser
VIEW IN TELEGRAM
Oldschool ppl are u here?)
AWS UG Munich - January 2025
AGENDA:
Address: view@gMaps
RSVP?
#meetup #mucMeetup
AGENDA:
18:00 - Doors open, networking, drinks, food
18:30 - Markus Ostertag (AWS Hero): Recent AWS announcements
19:15 - Benjamin Hofmann, Biyan Cicek and Tim Chen (MaibornWolff): Incident Resolution Assistance with AI
20:00 - Ovidiu Hutuleac (Sr. Data Solutions Architect @ AWS): Deep Dive into Amazon Aurora DSQL
20:45 - More drinks, more networking
Address: view@gMaps
MaibornWolff GmbH KARE Kraftwerk
Drygalski-Allee 25, 11th Floor · München
RSVP?
#meetup #mucMeetup
Drygalski-Allee 25 · Drygalski-Allee 25, 81477 München, Germany
Building
#webinar
🚨 Improve Your Angular Architecture for Long-Term Maintainability
Webinar with Manfred Steyer, GDE
https://www.angulararchitects.io/improve-your-angular-architecture-for-long-term-maintainability/?mc_cid=c5c4030e8b&mc_eid=0d74431810
14.01.25, 16:00-17:30, CEST Berlin
🚨 Improve Your Angular Architecture for Long-Term Maintainability
Webinar with Manfred Steyer, GDE
https://www.angulararchitects.io/improve-your-angular-architecture-for-long-term-maintainability/?mc_cid=c5c4030e8b&mc_eid=0d74431810
This media is not supported in your browser
VIEW IN TELEGRAM
While loop without an exit condition in real life 😅
Show this to your juniors if they again asked how work
Show this to your juniors if they again asked how work
while(true) {...} 😊"The 17 Rules of Software Engineering – Every Developer Should Know"
These principles capture the essence of what makes great software engineering practices timeless.
✅ Stop falling in love with your own code.
✅ You will regret complexity when on-call.
✅ Everything is a trade-off. There's no 'best.'
As someone who's spent years in software development, from optimizing Angular applications to architecting large-scale systems, these rules are a reminder of the lessons hard-learned in the trenches:
- Every line of code is a liability: Less is more.
- Document your decisions: The best code can’t fix poor communication.
- Ship early, iterate often: The faster you learn, the better the outcome.
Software engineering is not just about writing code—it's about building resilient systems, fostering collaboration, and thinking long-term. These 17 rules are a checklist every developer, junior or senior, should internalize.
What’s the one rule here that resonates the most with your experience?
These principles capture the essence of what makes great software engineering practices timeless.
✅ Stop falling in love with your own code.
✅ You will regret complexity when on-call.
✅ Everything is a trade-off. There's no 'best.'
As someone who's spent years in software development, from optimizing Angular applications to architecting large-scale systems, these rules are a reminder of the lessons hard-learned in the trenches:
- Every line of code is a liability: Less is more.
- Document your decisions: The best code can’t fix poor communication.
- Ship early, iterate often: The faster you learn, the better the outcome.
Software engineering is not just about writing code—it's about building resilient systems, fostering collaboration, and thinking long-term. These 17 rules are a checklist every developer, junior or senior, should internalize.
What’s the one rule here that resonates the most with your experience?