Safetest is a new UI testing library that combines Playwright, Jest/Vitest, and React for an E2E testing solution for applications and component testing. It works with multiple UI libraries and test runners and provides powerful reporting capabilities. https://t.co/A0XiCLveSk

Three steps to use Angular signal inputs now 💪🏼 PS. Was tested on a small project, don't do it in production! 🫤 #Angular #ngxtension

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. •

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.

👉 Official @playwrightweb's Component Testing support for Angular is a work in progress. https://t.co/Oubbt7XzIu

🔔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

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.

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 💪:

@andybudd I’ve been quoting @KentBeck for years saying your backlog should be a “list of questions, not features.”

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.

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.

SpaceX website in 2002 Created by 2Advanced Studios and Shane Mielke #WebDesignHistory

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.

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.

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.

"Sprints are just agile training wheels."

People not helping other people because "it's a distraction" is a dysfunction that falls firmly in the lap of upper management. 1/3

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. https://t.co/oXwNRERaCt

Ein Zeichen, das man nur dann setzt, wenn man dadurch keinerlei Konsequenzen zu befürchten hat, ist kein Zeichen. #OneLoveBinde

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 👇