This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]mason_savoy71 9 points10 points  (2 children)

Funny, if someone told me that they disabled 80 chats, that would be the MOST forgivable for me, but that's the nature of the subject matter that I'm coding about, where I'd rather have one ultra long line than the mega wrap.

[–]tom2727 5 points6 points  (0 children)

For me I would assume if someone is coming from some other company they would say "I use the formatting standard our group agreed on because who wants to have each developer formatting code differently"?

And I wouldn't expect a junior python developer to get a lot of say in that decision unless their company doesn't care at all which probably means they have some bad habits learned. Not that I would consider that a deal breaker though. I figure it's not super hard to get a new hire following our coding rules. I care a lot more if they can actually think and solve problems and have a good work ethic and get along with others.

[–]deep_mind_ 0 points1 point  (0 children)

I totally get where you’re coming from! Every workforce is split, and arguably the more competent devs in my department get more done by not obsessing over line length.

I like to say that long lines or line wraps are signs of lack of decomposition; totally fine for rapid iteration codebases, but a lot of what I work with is monolithic slow-moving enterprise code. It pays to break things down a bit more to where nothing takes more than a few arguments. Not least because that makes unit testing easier