2 ms·
Those "vacuous" roles exist to ensure that the dev team isn't lighting company money on fire working on the wrong thing, or crippled by inefficient bureaucracy
by psunavy03 3y ago
Those "vacuous" roles exist to ensure that the dev team isn't lighting company money on fire working on the wrong thing, or crippled by inefficient bureaucracy which is also lighting money on fire. Which isn't "vacuous;" there is value in saving the company money.
- brailsafe 3y agoIf that's what they do
- psunavy03 3y agoSome strong "junior developer" vibes here . . . nontechnical roles are not automatically fluff, and meetings are not automatically wastes of time.
- brailsafe 3y ago> Some strong "junior developer" vibes here How defensive. It seems to me like it would take someone with a rather fragile ego and low level of maturity to infer and write such a thing. I didn't call you or anyone else a bootlicker, so maybe save the personal attacks for your next sprint review or Reddit. > nontechnical roles are not automatically fluff, and meetings are not automatically wastes of time. If this had been your interpretation of my comment, then you'd have been right, but it's a choice to hold back and interpret a comment maliciously or charitably, and it's a choice to put people down. Non-technical roles do have value, as long as they aren't themselves an embodiment of their crippled inefficient bureaucracy.
- deleted 3y ago[deleted]