Clojurians Log v2
clojure-europe
Goooood Morning!
š
Moin!
Morning
morning
mƄnmƄn!
Good morning!
Gooood morning! Let's start the day with some good news. We are super excited to announce :clojureD 2021 - Special Summer Edition! Save the date: 5 June 2021 online worldwide It will be special, more news will follow soon. Please help us to spread the word.Ā :smiling_face_with_3_hearts: https://clojured.de
6ā¤ļø10š4š„³Thatās hearth warming news!
So we have already achieved 1 goal š thank you, Philipp!
Lovely!
Btw, fellow Clojurians, a project manager ādemandsā not to merge a PR without his or another C# devās approval (Python codebase, C# ex-dev) and Iām a chief python engineer, and I wonder if I missed something on the managerial side of development in the world?
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.
@ramart Exactly, I was relieved, some serious weight did get off my shoulders. @agile_geek 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. @vemv 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. @reefersleep 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 š
1šGood morning everyone (āmorningā is a relative term for me nowadays)
Library implementors; Iām creating a plugin for Kaocha. It has two deps: Clojure and Kaocha. However, whenever I use my plugin in a project, which naturally also has Kaocha as a dependency, thereās lots of dependency conflicts. Whatās the best way to solve this in a way that doesnāt force plugin users to tediously write a long :exclusions list? Use :provided for the Kaocha dependency in my plugin project and detail in my project README which version of Kaocha that my plugin assumes? Doesnāt seem very solid, might break subtly if someone uses my plugin with an incompatible version of Kaocha. Or is that not how :provided works?
I guess itās an ego thing?
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, @javahippie, thatās a good suggestion! Iāll try this and see how it works and feels.
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. š
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
@ordnungswidrig interesting! Circumvent the problem entirely.
But, also, bloat the plugin.
Thereās always a tradeoff š
Thanks a lot for the option! Very cool.
:man-shrugging: It is what it is :D