Yeah, I get all that, but still frustrating. It’s all about balance) There were 2 huge DTOs with all the same properties but the name of 1 id(one entity was split into 2), So what I did, is fill an expando object with all the properties, including both ids, and then just call a simple method that created an instance of a generic target type with filled properties from the expando. Then I would just call this method with one of this 2 types as target when I need them. The method is just 4 lines on creating an instance and filling it using for each over expando’s dictionary. That’s it. Maybe it’s just my bias, but to me it’s simple, takes little space and just 1 method. Would appreciate any feedback)

My biggest mistake this month....is that I still haven’t quit my job 🤪. But actually, I’ve made a mistake of listening to my superior during PR. I had an elegant solution to a particular problem(a bit of a duck 🦆 typing in C# for 2 similar, but not related entities), he said it’s too complex(yeah, fill object’s properties and turn it into a desired type is soooo complex 🤣). Made me rewrite it into a bulk of copy-paste logic, that took 3x more space and looks awful(+ harder to maintain). He said it will cut some logic branching, but it did not at all, it has even increased it.... I know about reducing complexity and all for it, but it just triggers me, when developers complain about ‘complex’ solutions, just because they don’t know the language features and can’t utilize them(even though this feature fits the problem like a glove and was even introduced to solve such problems). Sorry for the rant 🤭

Maybe static code analysis? It won’t be much, with quite a few false-positives, but still worth a try IMO. When I encountered such lack of review, I mostly googled “best practices” for resolving situations which I was not sure about. After that try to criticize your code yourself: “Maybe I can get rid of this if statement?”, “How do other people go about implementing metrics?”, etc.

C#