Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Well best thing IMO is to 'show' developers.
"Hey check this out, I did this thing, I think it could save us some time."
That's pretty much every react codebase I've ever seen in the wild not part of an OS project from Facebook
So nobody likes being told that you are beeing in the wrong.
What you need is to do is to carefully observe his behavior when he codes and collect his pain points with the codebase. That will take time.
To convince him to change, craft a list with personal benefits for him with each pain point solution. That may be less time spent on tedious task X or more praise from Boss for x.
Present him that in a whiteboard session. But put your ego away and always think what he desires. That way you get it your way.
@kirodian The book "This is Service Design Doing" may help you with some systematic methods on how to observe and introduce change.
The methods are free of charge on the website. https://thisisservicedesigndoing.com/...
This Is Service Design Doing: Applying Service ... - Amazon.com