Podcasts Technology Syntax - Tasty Web Development Treats Hasty Treat - Getting Buy-in for a Tool Like Prettier From Your Team

Hasty Treat - Getting Buy-in for a Tool Like Prettier From Your Team

Published: April 27, 2020, 1 p.m.

b'

In this Hasty Treat, Scott and Wes talk about getting buy-in from your team when using new tools.

LogRocket - Sponsor

LogRocket lets you replay what users do on your site, helping you reproduce bugs and fix issues faster. It\\u2019s an exception tracker, a session re-player and a performance monitor. Get 14 days free at\\xa0logrocket.com/syntax.

Show Notes

02:53 - Q: "I wrote a long message to our architect asking if I could install prettier into our component generator for new projects moving forward, and the response I got was: \\u201cDon\\u2019t auto-format, not all devs want that and prettier doesn\\u2019t always format the way I like, I don\\u2019t want to enforce that on devs.\\u201d

This sucks because I know the codebase would benefit so much. Right now every time I visit a project so much of the code is not spaced out that it makes it hard to read quickly for me, lots of the React code is bunched up with no spacing - it\\u2019s a mess to read for me especially because I am very organized. If this was your situation where you know a new tool/standard is something that can help a lot but it\\u2019s shot down, do you just give up? I don\\u2019t know how to respond to this because I am the only dev who has ever proposed this at my company and I just started here.

05:03 - Lots to unpack here

  1. Some senior devs don\\u2019t like getting suggestions from other devs. There is a sense that these things change quickly and I bet there is some anxiety over that at play here.
  2. Senior devs know better than to slap new tools into the codebase because they have probably done it and regretted it. What if it broke your code.

08:20 - So what can you do?

  1. Ask for their thoughts on a tool instead of suggesting it - it seems you have done this already
  2. Show the dev that even though it looks weird, it\\u2019s better for readability.
  3. Look at existing guidelines and try to match the settings as close as possible (not always an option with prettier).
  4. Put together a solid argument for it, written down.
  5. Use it in a smaller project. Everyone is against prettier at first, but once they use it, they realize how amazing it is.
  6. Can you just Prettier the code yourself and then format it otherwise before you check it in? This depends on if you have existing formats.

Links

Tweet us your tasty treats!

'