So we have already achieved 1 goal 😍 thank you, Philipp!

I guess it’s an ego thing?

Yup, the same thought came to mind))

if (and that is a strong if) your goal to make them not do that... make lots of small PR's. it will probably upset them though... so be careful.

Eventually he got frustrated by my question - by what means he could review my Python code? He went off the rails, started ranting that he knows general architecture patterns better and so on))) and got a response he was scratching for. “I know everything better than anyone else” type of managers are quite common in Georgia, but this is American company and has no damn clue how he ended up here. Now CEO and HR is discussing how/if that guy and I can go on working together. And I’m the person who put all the mess, written by 3 very beginner python developers and a data scientist for 6 months, into a proper, production grade shape and lay the foundation for the product in less than 2 months. It’s funny how some people mistakenly take friendly and respectful attitude as a weakness, and eventually get surprised when they get whipped for their actions by that very friendly face. 😄

😱

:man-shrugging: It is what it is :D

Sounds healthier for you in the end. The manager you depict will neither change nor see a problem in his/her behaviour.

Yeah. I've been in a similar situation. I left the organisation and got a job in a company where my opinion and skills were valued. I've worked as a permanent member of staff in about 8 orgs & as a consultant in 20+ and I've only had this issue twice with 2 individuals only so pretty sure it's not me!

> It’s funny how some people mistakenly take friendly and respectful attitude as a weakness This hasn't left my mind lately. Being polite and reasonable is a must, but if you don't "show your teeth" from time to time people can take advantage of that perceived weakness

Good on you for standing up to him, and leaving in a good mood. Sounds like a terrible co-worker to have for anyone, too bad for them.

@U1Z4D5SSV Exactly, I was relieved, some serious weight did get off my shoulders. @U05390U2P That’s the next checkpoint in line, although there are some pending projects in the company I don’t plan to stay. On the other hand, I don’t have that amount of experience, but I had 2 similar encounters before in my 8+ years of experience. The one I observed immediately and left before I signed the contract. Another took about 5-6 months, Bank of Georgia. @U45T93RA6 well, in this case I guess I was a bit too late to the party :D I couldn’t imagine someone would go so far beyond professional line. @U0AQ3HP9U Thank you! Yes, I feel sorry for 3 junior devs that I was supervising. But in the end I don’t really fathom how can company tolerate such employees. From their point of view - I was the only person in the team who didn’t follow/accepted the process 😄

I don’t understand why there are version conflicts if it’s the same kaocha version in your plugin and the target project? Shouldn’t they have the same transient dependencies?

It’s not the same version 🙂 I can’t know that plugin users will have the same version.

Ah, now I get it 🙂 Then :provided is the best way. You could look up the kaocha version in the classpath while initialising, and output a warning if the kaocha version was never tested with your plugin

Thanks, @U0N9SJHCH, that’s a good suggestion! I’ll try this and see how it works and feels.

Also you can alias import with “mranderson” it renames the packages to provide an independent copy of a lib

Oh nice, bookmarked!

I tried it with cheshire once and it worked like a charme

Many libraries using jackson use shadowing, because it is used everywhere

But I’m not sure how it would work when using it with a plugin system

@U054UD60U interesting! Circumvent the problem entirely.

But, also, bloat the plugin.

There’s always a tradeoff 🙂

Thanks a lot for the option! Very cool.