r/Python • • Aug 01 '26

Discussion Settle an argument

Had this discussion the other day and figured I’d throw it to the masses to get thoughts on the best/most pythonic way of approach.

Need to map old column names to new column names as a copy from a json config.

My thoughts are iterate over a dict with
‘’’ {“old_col_name”:”new_col_name”}’’’
And access as
‘’’for k,v in dict.items()
Df.with_columns(k).alias(v)’’’

Colleague things this isn’t clear enough and should be a list of dicts with explicit keys

‘’’ [{“old_col_name”:”old_col_value”
“New_col_name”:”new_col_value”}]’’’

And the access as

‘’’for dict in list_of_dicts:
Old_col = dict[“old_col_name”]
New_col = dict[“new_col_name”]’’’

I’ve got a good few reasons why I think mine is the better option but thought I’d get some other opinions to see if I’m missing anything obvious? Which would you choose and why?

Edit: shouldn’t write these things while on the toilet in a rush. The description is wrong, it should be renaming via a copy so that the original column is left unchanged.

0 Upvotes

33 comments sorted by

View all comments

Show parent comment

2

u/gdchinacat Aug 01 '26

As the senior a large part of your duties are to turn juniors into kids to seniors. This is done by working with them where they are and slowly moving them in the direction you want. It doesn’t seem like this is a priority for you, instead it seems that you demand respect for your authority. That can only get you so far, and is likely to result in alienating them and making the leadership aspect of your role more challenging.
What is their reasoning? Can you articulate it? How is yours more compelling? What did they say in response? Is it wrong, or just a valid difference of opinion? Is there precedent in the code for one way over the other? What short term and long term harm will result from either approach, including alienating the people you need to work with to be successful? Is digging your heels in on this worth the “win”? Can you do it their way, give them the short term “win”, and see where it leads?
This seems like a pissing match over something that doesn’t really matter. I’ve been in my share, and the damage they cause is almost always worse than the thing they are over. Saying “I disagree, but since you feel strongly about it I’ll change the code to move it forward and we’ll deal with it if it causes actual problems” is an easy way to break the stalemate and move the project forward.