It is often very difficult to explain to non-developers how your first point could possibly be true. Even if you have regular discussions regarding the value of experience and the possible damage that could be done by a bad or inexperienced developer. I find that it is easy to agree at a surface level that those concepts make sense, but if someone has not actually had the experience of writing software, they have trouble really understanding this concept. Most people still see most jobs as doing x unit of work over y unit of time. So the more time that someone is willing to spend each day the better. We all know that a bad developer can actually produce negative gains for the team, but it is a hard concept to fully explain.
I wonder if comparing it to home improvement type work would be a good universal analogy for most people. Would you rather hire the inexperienced person to come do your plumbing or the 30 year professional. The former doesn't give you a proper estimate but will work endlessly at a lower rate on the problem. This person eventually completely messes up and a water pipe in your ceiling leaks for days. Or you could have hired the other person who would almost certainly have completed it within the estimated time frame with professional quality and never caused the pipe leak.
