Yeah I find myself switching between these two perspectives, so I don't think that one of them characterizes me directly. Actually, very often when building an

Yeah I find myself switching between these two perspectives, so I don't think that one of them characterizes me directly. Actually, very often when building an MVP it makes a lot of sense to just say “let's allow people to do that to keep it simple and just assume that they either don't do it or that later they can explain why they felt the need to do it.” For instance if you can take inputs from one system and push outputs to another system, and those have overlaps, you might assume that your users never create cycles where your software starts pulling in the stuff that it pushed out, so you never check the sorts of loops to make sure that you're making progress, and maybe someday someone configures an infinite loop in it... In practice non-technical users at a small company don't trigger this and are surprised if you build things that read from Y and push back into X, “how is that even possible”.