It's weird how these "senior engineers" bash on other people's code while they themselves are still stuck coding in 2007 and refuse anything new or different. "Software Engineer" has become a laughing stock that I don't want to associate myself with the title anymore. Instead of engineers, I'd call those seniors "software tools" (also human "tools" for that matter).

"senior" probably refers to their age instead of skill level

At least, they are stuck in 2007 and not in 1982...

Explaining to a senior how classes works and stuff like that and just to hear that he does not understand, that it is to complicated and that in Cobol he didn't have that.

What is "bashing"? What don't these people like about your code?

I have had to correct people's code, but it is things like no initializing variables, and not setting pointers to null after deleting an object (yet still relying on pointer being null). Or helping people sort out memory leaks.

@Demolishun not necessarily my code, I'm talking about refusing and putting down anything they don't know/use.

.. and instead of listening and learning from their experience you bash on their advice.

They too were once young bucks, believing they are the best ever, looking into latest techniques and products,

Then they learned... that sometimes `echo "hello world"`

is better than defining a logging module shared globally and detects terminal types plus verifies color scheme etc etc..

But no, you won't listen, like they didn't listen,

and thus - history repeats itself..

@Nihil75 yeah, fuck off

@Nihil75 I would love to learn from them if they have something to offer except whining and putting down everything different than what they already know

@rantsauce I want to learn too not listening to 'back in my days we used goto, or floppy disks'

I don't care, I also know all that. Look to the future damn you.

@Grumm plot twist: the future IS floppy disks and goto but they're called something new and buzzwordy.

@rantsauce only a cunt knows everything