Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Meanwhile me just hoping someone would say:
"Bro mind if I clean this up?"
irene284236dI’m right here with you. I am working in a codebase where the code is clever AF. That makes it terse and there are no comments. Then functions gets moved out of a class somewhere even if it has no reusability anywhere else. “It makes the file shorter” what kind of rationale is that for having to open sixty files to figure out what one does? Private methods are an option.
🎶refactor while you work🎶🎶🎶🎶🎶🎶🎶
orimligt43536dI'm on the other end here. We have very good code reviews on my new place which made me realize my code style is shit. On the bright side this will probably have a positive outcome in the long run.
Root7029736d@SortOfTested I do, and continually get yelled at for it. 🙄
It’s always better, but they don’t seem to give a crap. “This change doesn’t seem necessary, and it wipes out commit history for those lines”
Good to know someone else’s commit message is more important than readability. Such a pity that there’s no git history command that would allow me to do some meaningful freaking work.
To be abundantly clear: /s
git log -- filename should produce a previous commit
pleuph78736dIf you know you know what you are doing, you should be able to explain why things need to be different. If that is not appreciated, you may need another place of work. I know that may not be easy, but it's taken me a few horrible experiences to realise this.
I knew about the ego.
I spent years getting over mine and it’s still pretty bad.
Hard not to feel smart when you’re doing things daily with math and logic that 20 years ago were considered “magic”, while most everybody else struggles logging into their own email client.