This is something that programmers (including myself) are often guilty of. We see an implementation and understand what features based on that implementation ar

This is something that programmers (including myself) are often guilty of. We see an implementation and understand what features based on that implementation are difficult/infeasible. Then we say things like "it isn't possible with our architecture" and "It is understandable that the website works in $x way." The flipside is true too: developers are very understanding of bugs/shortcomings that are borne out of the specific implementation. With all this knowledge, it is easy to say things like "people shouldn't use this tool for that" or "users should know this is flaky" At some point you have to fight for the user instead of defend the code.