@addyosmani SDD often lays in the hands of devlopers. I think we need more collaboration in specs. Acceptence critera, goals, edge cases and domaim knowledge. The problem is, how do we collaborate?
Code reviews aren’t just about catching bugs; they’re a chance to teach, learn, and grow as a team. Sharing constructive feedback fosters collaboration.
How do you create a positive review culture?
TTFR (Time to First Review) is vital for team productivity. Quick feedback speeds up PR merging and keeps developers engaged. Often, PRs get delayed. What's your team's approach to reduce delays? Clear ownership, rotating reviewers, or other strategies?
Today's suggestion: Embrace automation.
Leave the recurring tasks like linting, testing, and deployment to automated tools. This frees developers to concentrate on the core task: creating.
Which automation tool do you swear by?
Smaller PRs lead to faster reviews, making developers happier.
Dividing big changes into smaller parts has been transformative for our team: less review fatigue and more merges. How do you manage large PRs?
Does your day vanish before you can focus? Balancing deep work with team collaboration can be tough. Think Slack pings and meetings.
Here’s what I’m trying:
➡️ Daily blocks of time for deep work.
➡️ Alerting the team when I’m busy to prioritize urgent tasks.
Share your tips!
🎉 Vue Tips Collection (Second Edition) is here! 🎉
Master Vue in only 5 minutes a day.
A collection of 118 tips on using @vuejs, all packaged in a beautiful hardcover book.
https://t.co/2EzTLnbuJl
🧑🚀⭐ Calling all aspiring astronauts—Astro 3.0 touches down next week. We're giving away 10 of these official Astro hats to celebrate!
Retweet for your chance to win.
🚨 Giveaway Alert 🚨
We are giving away 20 @reactify_in T-shirts and stickers.
Follow us and Retweet this to participate in this giveaway and help us spread the word about @ReactNexus.
https://t.co/uIFgKKahEf
We will randomly pick 20 winners on Tuesday evening.
I want a do a livestream, showing how to write maintainable React code with:
- SOLID principles
- Proper IoC
- Typescript
- Generated API clients
- React Query
- StorybookJS
After this, if you write bad FE code, you need to go and wash your head.
RT if you're interested.
Raycast × Vercel Giveaway 🎁
@leeerob and I are giving away 10 Raycast mugs and 10 Vercel water bottles to 20 followers who:
· Follow @raycastapp and @vercel
· RT this tweet
Winners announced on Feb 13