Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 4
    is this only your opinion or you can back it up somehow? At OP ("lowest") level, "stepping on the brake, saying no" in my experience rarely turned out okay. Neither for project, nor for career. Looking back I can clearly recall cases when I missed a thing or two when "saying no" against the vision of senior colleagues / lead / manager Commented Apr 4, 2014 at 14:25
  • In terms of human resource, putting people behind work tickets without proper handling of their work value concerns is likely to end up in a disaster. Happy workers work more for less, there is economic proof of that. Stepping on the brakes is a learning opportunity for both the junior and the management. Stepping on brakes is how startups can be so competent in so little time, we don't have friggin tickets. It may rise conflict, but conflict is part of the goddamn life. Caring about quality should be listened to and enforced, so I'm on the step on brakes side. Commented Apr 4, 2014 at 20:22
  • 2
    I recommend this reading which treat about low-level devs empowering joelonsoftware.com/articles/TwoStories.html Commented Apr 4, 2014 at 20:35