MacGuyver is amazing. He can take a ball of string, some paperclips, and a piece of chewing gum and build a functional airplane. But the point that is often lost is that he’d much rather build an airplane out of airplane parts.
Being a MacGuyver Programmer is great. When you need to, you can throw together working code out of whatever is available. But just because you CAN code that way, doesn’t mean you SHOULD.
A (relatively) small amount of extra time and effort means writing code that is more organized, commented, efficient and extendable. One of the hardest day-to-day jobs of programming is convincing others that the additional time is worth it in the long run. Can I tack on an additional feature in a couple of hours? Yes. Will that mean time lost down the road when that feature isn’t properly integrated with the rest of the code? Yes. Sound familiar?