- Dołączono
- 14 Lut 2023
Dear Christ get me out of here.
I've put in my notice, but hot damn my replacement has reminded me why I'm going back to school.
So, my company hired a woman to backfill on the work I was doing, which was basically requirements management (kill me) and documentation (which, fine, as long as we're documenting something useful instead of stacks of presentations for whatever new cycle of reviews the Government decides they need to layer on top of other reviews that were already in the pipeline).
My team lead asked her what her background was. She says (and this is why I want to kill myself), "I'm a systems engineer, but I'm not really technical. My background is in project management. But I'm really into Model-Based Systems Engineering."
I take full responsibility for why people see me the same way in that I've been stuck in this role for the last 15 or so years (long story...but it is my fault; no need for sympathy). But Christ divine, the profession of "engineer" is not to be taken seriously anymore when anyone without more cred than farting around in relational databases can be called an "engineer".
I've put in my notice, but hot damn my replacement has reminded me why I'm going back to school.
So, my company hired a woman to backfill on the work I was doing, which was basically requirements management (kill me) and documentation (which, fine, as long as we're documenting something useful instead of stacks of presentations for whatever new cycle of reviews the Government decides they need to layer on top of other reviews that were already in the pipeline).
My team lead asked her what her background was. She says (and this is why I want to kill myself), "I'm a systems engineer, but I'm not really technical. My background is in project management. But I'm really into Model-Based Systems Engineering."
"Systems Engineering" used to mean that you could manage a program because you were engineer enough to herd all the cats from multiple disciplines. The concept of "Systems Engineering" over the years has devolved into "requirements management", which is nothing but requirements capture, sticking it all in a relational database, and pretending that you're just as much engineer as everyone with an actual technical degree, because you call all of that "Model-Based". I used to be in modeling and simulation...if that's modeling, your ass is on fire./SPOILER]
I take full responsibility for why people see me the same way in that I've been stuck in this role for the last 15 or so years (long story...but it is my fault; no need for sympathy). But Christ divine, the profession of "engineer" is not to be taken seriously anymore when anyone without more cred than farting around in relational databases can be called an "engineer".