To infer from that what Programmer B's "routine" development strategy is requires assumptions based on facts not in evidence.

Are we discussing the validity of code reuse or an approach to developing demos? If you place too many constraints, the analogy becomes meaningless and we end up debating a specific situation bearing no relation to anyone else's reality.

Makeshifts last the longest.