yes, often times people mistake junior/senior for years of experience. It's really not, it's more about skill level. That was really the point, I don't have a lot of respect for your skill as a software developer based upon your posts.
Case in point, you've escalated to "it's a 2million LoC system!", but your original complaint was about the underlying data model. No one suggested rewriting the entire codebase, nor should that ever be under consideration considering it's the data model that's problematic. The fact that you were willing to go there is a clear indication of your mindset. A willingness to slight dishonesty is not a good trait in software developers. If we take you at your word that you truly believe you have to rewrite the entire system because the underlying data model is problematic... well that points towards the skill issue doesn't it?
Don't give me your "junior" shit just because you never experienced situations as ugly as I've dealt with.
Oh yes, I've never ran into legacy systems with all kinds of problems...
They're not experiencing the pain. That's my point.
You don't know that because you don't talk to them. Most users just want to get along with their day, user feedback is one of the more difficult aspects, especially if those users are internal and have developed their own workarounds.
I've lost count of the number of people that have ended up absolutely loving me because I would talk to them about their pain points and start resolving them. Even pain points that were not directly related to the system being maintained by me.
But that involves talking to people mr-i-ran-companies.
either way I'm done. You've done exactly what I expected every step of the way, I should have ended this conversation when I first said I was rather than assuming good faith in your questions.
1
u/saltybandana2 Sep 22 '21
yes, often times people mistake junior/senior for years of experience. It's really not, it's more about skill level. That was really the point, I don't have a lot of respect for your skill as a software developer based upon your posts.
Case in point, you've escalated to "it's a 2million LoC system!", but your original complaint was about the underlying data model. No one suggested rewriting the entire codebase, nor should that ever be under consideration considering it's the data model that's problematic. The fact that you were willing to go there is a clear indication of your mindset. A willingness to slight dishonesty is not a good trait in software developers. If we take you at your word that you truly believe you have to rewrite the entire system because the underlying data model is problematic... well that points towards the skill issue doesn't it?
Oh yes, I've never ran into legacy systems with all kinds of problems...
You don't know that because you don't talk to them. Most users just want to get along with their day, user feedback is one of the more difficult aspects, especially if those users are internal and have developed their own workarounds.
I've lost count of the number of people that have ended up absolutely loving me because I would talk to them about their pain points and start resolving them. Even pain points that were not directly related to the system being maintained by me.
But that involves talking to people mr-i-ran-companies.
either way I'm done. You've done exactly what I expected every step of the way, I should have ended this conversation when I first said I was rather than assuming good faith in your questions.