3 ms·

Rinse and repeat? I could be missing something, but are we saying we should adopt the mentality that we are too good for any job we might find ourselves in? It

Rinse and repeat? I could be missing something, but are we saying we should adopt the mentality that we are too good for any job we might find ourselves in? It sounds a bit arrogant to automatically assume that what you've chosen to divert your attention to has merit, and anyone who thinks otherwise is an asshole... I could be misreading, but your tone seems to veer more towards self-centeredness than empowerment.

codeonfire 11y ago
Hey, you don't know what it's like. Certain people claiming to be engineers have optimized on finding out what you're trying to accomplish and either blocking it or taking credit for it. They also have figured out how to punish people who do work that they are not getting credit for (i.e. authorized). This is their whole 'job' for which they get impressive titles and money for doing little actual work and having little actual knowledge. While you are sitting there coding all day they are off telling some VP about how they have you working on their project that was actually your idea and your sweat. The best policy for an engineer is the one I described.
- sangnoir 11y ago
  > Certain people claiming to be engineers have optimized on finding out what you're trying to accomplish and either blocking it or taking credit for it This is not universal, perhaps you ought to stop working for dysfunctional organizations > The best policy for an engineer is the one I described Again, not universally applicable. It might be the best policy for brogrammers.
sheepmullet 11y ago
> It sounds a bit arrogant to automatically assume that what you've chosen to divert your attention to has merit Why? When you are knee deep in solving problems for an organisation you will often have good insights. If you can't take the time to investigate these insights then you wind up a low productivity grunt. Unlike the OP I am upfront about needing control over my workflow. If you need to micro-manage... no problem... I'll find a new job.

codeonfire 11y ago

Hey, you don't know what it's like. Certain people claiming to be engineers have optimized on finding out what you're trying to accomplish and either blocking it or taking credit for it. They also have figured out how to punish people who do work that they are not getting credit for (i.e. authorized). This is their whole 'job' for which they get impressive titles and money for doing little actual work and having little actual knowledge. While you are sitting there coding all day they are off telling some VP about how they have you working on their project that was actually your idea and your sweat. The best policy for an engineer is the one I described.

sangnoir 11y ago
> Certain people claiming to be engineers have optimized on finding out what you're trying to accomplish and either blocking it or taking credit for it This is not universal, perhaps you ought to stop working for dysfunctional organizations > The best policy for an engineer is the one I described Again, not universally applicable. It might be the best policy for brogrammers.

sheepmullet 11y ago

> It sounds a bit arrogant to automatically assume that what you've chosen to divert your attention to has merit Why? When you are knee deep in solving problems for an organisation you will often have good insights. If you can't take the time to investigate these insights then you wind up a low productivity grunt. Unlike the OP I am upfront about needing control over my workflow. If you need to micro-manage... no problem... I'll find a new job.