Kim Arnett [she/her] leads the mobile team at Deque Systems, bringing expertise in iOS development and a strong focus on accessibility, user experience, and team dynamics.
🎉🎉🎉
Excellent post Abbey! I hope people read this and find the courage to take it back to their teams and spark improvements for their team. sends to my team too
Kim Arnett [she/her] leads the mobile team at Deque Systems, bringing expertise in iOS development and a strong focus on accessibility, user experience, and team dynamics.
This has me curious about looking at this question from the perspective of the reviewer — I wonder what steps can be taken to help people adopt some of these practices in a way that limits stress and overload on their part.
Let's say you have buy in from reviewers that these are important things worth considering — but there is potentially extra burden on the reviewer's part that might not entirely be overcome by buy-in and practice.
I'm just wondering out loud what some steps to think in that direction are.
Yeah that's where I think it's hard to articulate in some ways. Like, everybody involved has a role and we ultimately want to maximize mutual effectiveness and growth without burning anyone out in the process.
So, while yeah you put more on the review-ee, it just made me think about the overall pendulum of making sure we all get on the same page.
It's only a half-thought so don't read too much into my comment 😄
Ingo Steinke is a Berlin-based senior web developer focusing on front-end web development to create and improve websites and make the web more accessible, sustainable, and user-friendly.
Full Stack Web Developer, Certified AWS Solution Architect, Triathlete 🏊♂️🚴♂️🏃♂️, Love to play Basketball🏀, Reading Books and blogs and exploring new places.
Thank you for the great post Abbey Perini! Well written.
Nice point 👍 - A collaborative, psychologically safe feedback process can quickly increase code quality and productivity
We're a place where coders share, stay up-to-date and grow their careers.
🎉🎉🎉
Excellent post Abbey! I hope people read this and find the courage to take it back to their teams and spark improvements for their team.
sends to my team too
💙💙💙 Still not over watching that Taylor Poindexter talk and thinking "Kim does all of this"
🥺💙
Really great post!
This has me curious about looking at this question from the perspective of the reviewer — I wonder what steps can be taken to help people adopt some of these practices in a way that limits stress and overload on their part.
Let's say you have buy in from reviewers that these are important things worth considering — but there is potentially extra burden on the reviewer's part that might not entirely be overcome by buy-in and practice.
I'm just wondering out loud what some steps to think in that direction are.
Which things do you think are extra burden on the reviewer's part? Because I feel like I put a lot more on the review-ee 🤣
Yeah that's where I think it's hard to articulate in some ways. Like, everybody involved has a role and we ultimately want to maximize mutual effectiveness and growth without burning anyone out in the process.
So, while yeah you put more on the review-ee, it just made me think about the overall pendulum of making sure we all get on the same page.
It's only a half-thought so don't read too much into my comment 😄
I get it. There's a reason people get whole degrees in communication 🤣
Now I start to understand StackOverflow and large parts of the Linux community. 😂
Really good read and some solid points, thanks! Especially love the emphasis on how critical it is on a team feeling safe to ask the stupid questions
Trust is relatively easy to lose but extremely hard to rebuild!
Great title, nice memes!
Thank you for the great post Abbey Perini! Well written.
Nice point 👍 - A collaborative, psychologically safe feedback process can quickly increase code quality and productivity