News for hackers. Stuff that matters.
Re:The shittiest project I ever worked on (2013) by retSava on Friday May 24, 2019 @09:29AM (#20001214)
Sometimes the desired result is not known ahead, at project start, and twisting and turning is part of the process of (hopefully) ending up with something that people are happy with. It's just part of human nature and needs to be embraced. You just ensure you are paid for it.
Re:The shittiest project I ever worked on (2013) by wool_gather on Friday May 24, 2019 @12:28PM (#20003129)
This is the optimistic take. :) But there's a difference between

exploring the design space and iterating until you end up with a product that makes the customer happy

and

endlessly reworking decisions every time the next "stakeholder" in the customer's org sees a part of the bikeshed that they have an opinion on

One is a skill-engaging and -enhancing professional project. The other is the road to burnout.

Re:The shittiest project I ever worked on (2013) by retSava on Monday May 27, 2019 @04:39AM (#20020455)
Yeah, absolutely, agree on that :).

Reminds me of the Battlechess duck, point 5 here: https://blog.codinghorror.com/new-programming-jargon/