Programming is 100% design, there really is no separate "implementation" phase. If the design has a flaw, whatever the reason: it is a bug. A big part of deve

Programming is 100% design, there really is no separate "implementation" phase. If the design has a flaw, whatever the reason: it is a bug. A big part of development is "discovering the requirements." It is typically the hardest part for real world projects, and when that fails, it is perhaps not a bug in the code, but it still a development error that needs to be fixed. If a developer got a piece of paper that said "blue" but the real world requirement was "green", and it was not possible for the developer to find out together with any stakeholder, then there is a development process error, that needs to be fixed. In any event, it needs to be fixed, so pointing to someone else wont really help.