Web Developer
Germany / Düsseldorf
Joined August 2007
- Tweets2.9K
- Following664
- Followers168
- Likes2.9K
Pascal Küsgen retweeted
Three steps to use Angular signal inputs now 💪🏼
PS. Was tested on a small project, don't do it in production! 🫤
#Angular #ngxtension
Pascal Küsgen retweeted
Frontend Unit Tests.
🟡 The Gold Standard 🟡
Everyone racing for top coverage.
But reality looks much much different.
When NOT to Write Frontend Unit Tests:
• PoCs/MVPs: Here today, irrelevant tomorrow.
• UI part that is changed a lot: Don't waste your time.
• Experimental features: Can change any minute.
• Basic static components: Not worth it.
• Overwhelming mocking: Value > Effort.
• Deadlines: Especially in startups.
• Limited resources: Business value first/early phase.
• Redundant scenarios: 100% coverage is not the goal.
• Backend is more important: Frontend is changing much more often.
When TO Write Frontend Unit Tests:
• Critical features: Some things just can't fail.
• Complex logic: Once stable of course.
• Reusable components: The Foundation.
• Regression prevention: When it breaks often.
• Set in stone features: Worth the effort.
• Documentation: Tests can be great for that.
• Pre-refactoring: Before embarking on refactoring.
• Integration points: Vulnerable places.
Business Perspective:
• User Focus: E2E reflecting customer experience.
• Cost Efficiency: E2E tests can catch critical bugs.
• Time Savings: Reducing emphasis on unit tests can speed up development cycles.
• Real-world Relevance: E2E tests in near-production environments offer tangible insights.
• Simplified Reporting: E2E results are often more digestible for non-technical stakeholders.
• Coverage Overkill: Extensive unit tests can be redundant with a strong E2E suite.
• Maintenance Overhead: Frontend changes might require frequent unit test updates.
Businesses often lean towards ROI.
E2E tests often provide clearer value.
Pascal Küsgen retweeted
The web development industry almost entirely missed the point of Flux and unidirectionality. Most modern React, SolidJS, etc apps are MVC. Which isn't a problem for simple apps. But when features have to be complex, it helps to know the most fundamental lessons of the industry.
Pascal Küsgen retweeted
👉 Official @playwrightweb's Component Testing support for Angular is a work in progress.
github.com/microsoft/playwri…
Pascal Küsgen retweeted
🔔I’m available for new challenges.
I’m currently seeking new challenges as an Angular Frontend Engineer. I am eager to contribute to your team's success by ensuring faster delivery and a successful Angular application. My expertise lies in best practices, performance optimization, architectural design, and training.
👉 Available immediately
👉 Expertise in: Angular / TS / NgRx / RxJs / Nx
👉 Open to full remote or hybrid positions in the Grenoble area
🙏 RT is highly appreciated 🙏
✅ Visit my personal website: thomaslaforge.dev/home
✅ Check out my current project for the Angular community: AngularChallenges on GitHub: github.com/tomalaforge/angul…
If you would like more information or wish to connect with me, please feel free to reach out to me on X or via email at [email protected].
I look forward to taking on new challenges with you! 🚀
Pascal Küsgen retweeted
Refining a story and defining details before you implement, release, and get feedback is just waterfall requirements gathering. Those requirements _will_ be wrong. Agile is NOT waterfall. It's not doing what you did before but with new names.
Pascal Küsgen retweeted
What if I told you that using Input getters and setters, to convert inputs to something else before being used in the component isn't going to be necessary anymore?
Take a look at the before and after 👇
All this is possible to this new PR, thanks to @_crisbeto 💪:
github.com/angular/angular/p…
A more detailed blog post is coming ⚡️
Get ready to remove a lot of code!!!
#angular #angularrenaissance
Pascal Küsgen retweeted
I’ve been quoting @KentBeck for years saying your backlog should be a “list of questions, not features.”
Pascal Küsgen retweeted
A story describes your customer/user's problems, not yours. The whole point is to identify things that customers actually need—that solves their problems. To do that, you have to identify the problems. Stories do not describe solutions. Those are your problem.
Pascal Küsgen retweeted
I'm not a fan of Scrum allowing the work to be called done if it's in the "ready for deployment status." If it's not deployed, its inventory (in the Lean sense)—money spent that's not creating revenue. It's waste, pure and simple.
Pascal Küsgen retweeted
SpaceX website in 2002
Created by 2Advanced Studios and Shane Mielke
#WebDesignHistory
ALT SpaceX website in 2002
Pascal Küsgen retweeted
PRs are not a burden. They do active damage when used out of the original context (a distributed network of untrusted contributors working as isolated individuals). Using them outside that context is not burdensome, it's destructive.
This Post is from an account that no longer exists. Learn more
Pascal Küsgen retweeted
PRs driving code reviews make sense only if you are working as isolated individuals and your work is not trusted by the team--in other words, an open source project. When the team is working, collaboratively, programming in an ensemble, for example, PRs are nothing but waste.
Pascal Küsgen retweeted
Unpopular opinion: Pull requests are a terrible idea in almost all contexts.
Focus on finishing things as a team instead of keeping everybody busy. Do code reviews in real-time through pairing or ensembling instead of blocking the flow of work waiting for a pull request review.
Pascal Küsgen retweeted
People not helping other people because "it's a distraction" is a dysfunction that falls firmly in the lap of upper management. 1/3
Pascal Küsgen retweeted
TIL: The CIA “The Simple Sabotage Field Manual” from WWII suggested enforcing the bureaucracy at companies that delivered to the enemy as a viable sabotage technique.
corporate-rebels.com/cia-fie…
ALT Facsimile suggesting interfering in production by insisting on doing everything through formal channels.
ALT Facsimile suggesting interfering in production by questioning the decision power of the group.
ALT Facsimile suggesting interfering in production by referring all matters to a committee, and keeping that large.
ALT Facsimile suggesting interfering in production by holding conferences when more critical work is to be done.
Pascal Küsgen retweeted
Ein Zeichen, das man nur dann setzt, wenn man dadurch keinerlei Konsequenzen zu befürchten hat, ist kein Zeichen. #OneLoveBinde
Pascal Küsgen retweeted
You might be using a SharedModule to share components between different modules of your application 🤔
In most cases it will cause issues with tree shaking and bundle size of your modules 🍃
Let’s explore why, and what might be the possible alternatives 👇
![@NgModule({ declarations: [ButtonComponent, IconComponent], exports: [ButtonComponent, IconComponent], }) export class SharedModule {}](https://pbs.twimg.com/media/FbUa-TvWYAAXppL.jpg?name=orig)
ALT @NgModule({ declarations: [ButtonComponent, IconComponent], exports: [ButtonComponent, IconComponent], }) export class SharedModule {}
![@NgModule({ declarations: [ButtonComponent], exports: [ButtonComponent], }) export class ButttonModule {} @NgModule({ declarations: [IconComponent], exports: [IconComponent], }) export class IconModule {} Single Component Angular Modules (SCAMs)](https://pbs.twimg.com/media/FbUa-TyXkAADwbu.jpg?name=orig)
ALT @NgModule({ declarations: [ButtonComponent], exports: [ButtonComponent], }) export class ButttonModule {} @NgModule({ declarations: [IconComponent], exports: [IconComponent], }) export class IconModule {} Single Component Angular Modules (SCAMs)
Pascal Küsgen retweeted
Nach Ostern führen wir wieder unseren #Angular Architektur Workshop durch (100% online & interaktiv).
Jetzt Early Bird sichern!
angulararchitects.io/termine…