News for hackers. Stuff that matters.
Re:My Response to “Are we overcomplicating software developm... by bluGill on Friday January 20, 2017 @01:01PM (#13445580)
Process is about controlling people, so of course my examples are controlling people. The trick is they are process controlling people in areas where they need to be controlled. Contrast this to processes that control people in ways they don't need to be controlled.

Is someone checking that are login to your computer at exactly 8am every day? That a process that controls people but isn't needed for most programmers. The process makes perfect sense in context of assembly line workers: if even one person is late the entire line cannot start.

One thing that I didn't say but should have is that process should not be the first thing to fall back on. You might have to deal with the guy who pushes broken code all the time, but there are other solutions other than process that you should explore.

Re:My Response to “Are we overcomplicating software developm... by ktRolster on Saturday January 21, 2017 @12:17AM (#13448950)
Most of your post is still about processes, justifying why they are good. I don't think you get what it means, still: "people over process."
Re:My Response to “Are we overcomplicating software developm... by bluGill on Monday January 23, 2017 @03:23PM (#13465628)
looking back, I accept your criticism. I'm an engineer, ultimately I understand things like processes better than people.

I stand by agile saying people over process, but I have no clue how to actually explain it.