@grmpyprogrammer @Crunkle_Foreskin I think "this is called senior dev" is unwilling, maybe not the lead developer per se.
@Crunkle_Foreskin
(4/4)
Finally, depending on your personality and his personality this might be an endless battle. Since you can't change personalities.
However, I hope everything will eventually settle a bit. And you can find a middle ground.
It also depends on the company (low and high) management and the corporate culture, whether speaking-up is embraced or not. Or whether there are meeting about improvements and retrospectives.
@Crunkle_Foreskin
(3/4)
Then next you really want to involve more people at this stage, ideally 4 or 5 team members should be on-board in order to brainstorm together.
Most importantly, try to not push your changes, this person seems a bit unable to cope with change (I hope he is not too old :P?). Another approach is "pull management"; try to make him curious about the topics, be positive and praise others where applicable, focus on the strengths of the developers, support each other.
@Crunkle_Foreskin
(2/4)
So that being said. I think something else is also going on, communication and relationship. I bet he is actually a bit afraid of you doing (too) good and being successful at your job. So then this "senior guy" might think it he doesn't come across well.
My advice here is to try to first repair the relationship with him, talk with him at the coffee about other stuff. Maybe you have hobbies in common?
My reply in 4 parts:
(1/4)
@ernest @unofficial_kbin_guide I think a dedicated website like this kbin guide is indeed the way to go. Codeberg wiki is limited in several ways. Making this guide somehow part of an official project / documentation would be great. @unofficial_kbin_guide You agree?
@unofficial_kbin_guide for the most part we can actually copy and paste this guide to the official wiki page we have. 😉
@Hairyblue not advising Lemmy. And here is why: https://mstdn.social/@feditips/106835057054633379
@melroy
@mastodon.melroy.org