Forgot your password?
typodupeerror

Comment: Sounds like an interesting read. (Score 1) 83

by scottbomb (#46326457) Attached to: Book Review: Sudo Mastery: User Access Control For Real People

This part got my attention: "Just gotta check out the man page.... And that's where I stopped, every time. I've yet to truly understand Extended Backus-Naur Form, and my eyes would glaze over." - Finally! I'm not the only one! I've always had this problem too. At least now I know what it's called. The formatting used has never made sense to me. Thankfully, we have the internet where I can google examples when trying to learn a new command.

Comment: Re:You Don't (Score 3, Informative) 384

So you go back to step 1: the problem is badly described. The Systems Development Lifecycle dictates that you, as the new help solve the problem. Start at wherever there is trouble. In the scenario you describe, it looks like we need to go back to step one fix the root problem: it is badly described. We cannot build any system to high user satisfaction that is badly described. One can only start over and build from scratch. If that's not possible, we will have to break the problem down into manageable parts and dig deeper for root causes and solutions.

Comment: Re:You Don't (Score 4, Insightful) 384

Maybe you should have presented YOUR solution. Telling the boss "no I won't do it" will get you nowhere. Telling him "Look at my better way of doing it" will get their attention. The best lesson I've learned in business is to never take a problem to my boss unless I bring with me a solution to solve it. If you can't solve the problem, find someone who can, or else the boss will. Business needs are not going to change.

Simplicity does not precede complexity, but follows it.

Working...