I’m a big Cypress fan, so I’m shocked to say this: I just switched to @playwrightweb.
Here are 16 reasons I switched:
1. WAY Faster. ~2X faster with 1 core. ~6x faster with multiple cores (uses multiple workers)
2. Tests multiple browsers in parallel.
1/5
Comparison:👇
My collegue and I from @mindmatters are at the react alicante conference. After 2 years of covid this is now my first conference visit. I will try to share some snaphots of the conf.
#reactalicante#mindmatters
This Impact Map template shows (1) the difference between problem/strategic and solution/tactical design, and (2) most Scrum/Agile teams start at the right (tactical) rather than left (strategic) because stories are written before knowing the *why*.
#ImpactMapping#DDDesign
Mystery: "Get it done faster/sooner/more" Why?
What happens after we get it done faster/sooner/more? I need to remember to ask this question. If there's no good answer then this is just someone pushing their anxiety down a power gradient.
A demand for estimates stems from fear. The way to address that fear is with transparency. Deliver frequently. Track progress with a public kanban board or equivalent. Have a continuous dialog with management. The demand for estimates will wither away.
To fight Zoom fatigue, give people the freedom to turn their cameras off.
New experiment: videos off reduces exhaustion and boosts engagement—especially for women and newcomers.
Cameras off doesn't reflect disengagement. It helps to prevent burnout and promote attention.
CACM paper describing a framework of five dimensions to assess developer productivity. Any attempt to measure must touch at least three of these dimensions.
🙏 @nicolefv and her colleagues
https://t.co/aaq3sobP3x
It strikes me that the one-repo-per-service model just adds unnecessary complexity to dev w/ no real advantage. Why do it? For the most part, we are building applications that use multiple services. I see little point in splitting them into separate repos. Am I missing something?
try to keep refactoring separate (commits/ PRs) from bug fixes or enhancements. benefits?
- keeps me focused on the task at hand - improving design
- gives the other devs n mgrs confidence. so when i say im "refactoring" they don't panic. anymore 🤓😆
other benefits?
If you're interested in programmer productivity, staff turnover, codebase size, Conway's law, etc., this piece by @robsmallshire is well worth a read:
Predictive Models of Development Teams and the Systems They Build
https://t.co/CbAgJOwjwQ
Impediments to being agile? Looking forward to a convo with 2 long-time sparring partners, @scottwambler & @ivarjacobson on Wednesday. https://t.co/lSe9nh5sYe
My take: incentives (but don't tell them, I want it to be a surprise)
Super excited to share the latest! The SPACE of Developer Productivity: There's more to it than you think. 🚀🌠 https://t.co/CMWNTH5jhk
Check it out and let us know what you think! Many thanks to my fab coauthors and our great reviewers. 🤗
Not gonna lie, I spent a lot of time back in the day looking for DRY shortcuts to eliminate repetition of one or more of the Arrange/Act/Assert steps in tests. I've come around to appreciating the immediate clarity of tests that have each of the three steps explicit.