قد يعجبك
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. netflixtechblog.com/introducing-sa…
Three steps to use Angular signal inputs now 💪🏼 PS. Was tested on a small project, don't do it in production! 🫤 #Angular #ngxtension
The wait is over. 17.1 is available. make sure to upgrade and enjoy the full power of reactive inputs. 🎉🎉
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. github.com/microsoft/play…
github.com
feat(ct): angular component testing by sand4rt · Pull Request #27783 · microsoft/playwright
closes: #14153 and https://github.com/sand4rt/playwright-ct-angular TODO Enable vite-plugin-angular JIT mode: feat(vite-plugin-angular): add support for JIT mode analogjs/analog#374 (comment) Fi...
🔔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 💪:…
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.
I think the work may be in ready for deployment status or already deployed to be included in the sprint review, but not only deployed.
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.
I think the work may be in ready for deployment status or already deployed to be included in the sprint review, but not only deployed.
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.
Uh. I strongly disagree. Throw out PRs and you have a system for raising tech debt fast. Goal is not that you, a single developer, be happy but to ensure quality and to align the team. You can't avoid context switching, unless you have a person assigned to fix your errors ;)
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."
“I once attended a planning meeting in which it was discussed for 20 minutes whether a task should be included in the next sprint. The task could be done in five minutes.” This is silly. If we’re not working because "we don’t want to pull something extra into the sprint”,…
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. corporate-rebels.com/cia-field-manu…
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 👇
United States الاتجاهات
- 1. LeBron 77.9K posts
- 2. Cowboys 58.1K posts
- 3. Cowboys 58.1K posts
- 4. Gibbs 13.4K posts
- 5. Brandon Aubrey 5,704 posts
- 6. Ferguson 8,778 posts
- 7. Bland 7,523 posts
- 8. #OnePride 7,421 posts
- 9. CeeDee 8,952 posts
- 10. Goff 7,504 posts
- 11. #DALvsDET 5,115 posts
- 12. Shang Tsung 13.1K posts
- 13. Austin Reaves 11K posts
- 14. #LakeShow 3,467 posts
- 15. Pickens 10.4K posts
- 16. Al Michaels N/A
- 17. DJ Reed N/A
- 18. Sixers 11.6K posts
- 19. Jamo 3,980 posts
- 20. Toronto 29.7K posts
Something went wrong.
Something went wrong.