I totally accept that there might be reasons I'm unaware of to do things in a different way, but I also think that if I ask about a design choice, I should get a better reason for it than "because I said so", which is what I'm getting. I have 20 years of professional software development experience under my belt, 10 of them in the current company I work for - I think I deserve a better explanation then simply "because". That's what's bugging me.
Trouble maker and Problem solver ⚙️🔧
Loves simplicity, hates bullshit 💩.
Productivity obsessed, avid learner 🖥🚀
Sport and outdoor freak 🧗⛰
Metalhead 🎸🤘 Father of 2 👨👩👦👦
Opinions are my own
oh. with so much experience, I would find it hard to accept such an answer.
In the end experienced devs are there to build stuff but mostly to provide their expertise, if it´s not listened at all why hiring them at all.
and personally - but that is maybe just a flaw in my attitude - I would really find impolite and unacceptable an answer like "because i said so" - I barely use that with my kids - imagine at work.
Exactly! I couldn't have said it better myself. And frankly, even if I had just one year of experience I wouldn't accept this kind of answers.
You know, even if I'm not the smartest person or best developer in the room (which is probably true), even if it's a technology I'm not that familiar with - even then, I've learned a thing or two about software development over the years. Otherwise, I wouldn't be employed as a developer.
I don't mind if my opinion gets rejected - as long as I get a valid reason for it. If me and another dev are proposing different but equally valid solutions to the same problem, I really don't mind implementing the other dev's solution - and if it's better then mine I'm happy to do it because it means I'm learning something new - but unfortunately, that's not the case here.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I totally accept that there might be reasons I'm unaware of to do things in a different way, but I also think that if I ask about a design choice, I should get a better reason for it than "because I said so", which is what I'm getting. I have 20 years of professional software development experience under my belt, 10 of them in the current company I work for - I think I deserve a better explanation then simply "because". That's what's bugging me.
oh. with so much experience, I would find it hard to accept such an answer.
In the end experienced devs are there to build stuff but mostly to provide their expertise, if it´s not listened at all why hiring them at all.
and personally - but that is maybe just a flaw in my attitude - I would really find impolite and unacceptable an answer like "because i said so" - I barely use that with my kids - imagine at work.
Exactly! I couldn't have said it better myself. And frankly, even if I had just one year of experience I wouldn't accept this kind of answers.
You know, even if I'm not the smartest person or best developer in the room (which is probably true), even if it's a technology I'm not that familiar with - even then, I've learned a thing or two about software development over the years. Otherwise, I wouldn't be employed as a developer.
I don't mind if my opinion gets rejected - as long as I get a valid reason for it. If me and another dev are proposing different but equally valid solutions to the same problem, I really don't mind implementing the other dev's solution - and if it's better then mine I'm happy to do it because it means I'm learning something new - but unfortunately, that's not the case here.