The Reusable Mindset

Let’s talk about code reusability and the reusable mindset. The first step is to identify repeating code patterns where you can separate the implementation from the code. The next step is abstract the code, building it in such a way that it can accept an input(s) to pass in or configure the implementation. Then this black box code that you’ve abstracted handles everything for you based upon the input you provide and delivering an expected behavior every single time.

For our code, imagine moving the meta box add/register, render, and save functionality into a module that generates your custom meta boxes. Imagine passing in a configuration for each specific meta box you want to create, identifying things like the metadata, view file, meta box title and id, default values, and sanitizing function.

This technique reduces your time, costs, testing, and maintenance. It speeds you up while removing the complexity away. Build it once. Make it a module. Then for each meta box, build a configuration and view file. That’s it. Bam, done.

The entire point of this lab is to teach you the reusable mindset to empower your efficiency, productivity, and effectiveness.

What’s the Difference Between Boilerplate/Snippet and a Module?

A boilerplate is a snippet or scaffolding to give you a starting point. Then you edit the code for your specific implementation. You edit each implementation.

A module is reusable. You build it once. Then you reuse it. You don’t touch the code in it. Rather, you pass it what it needs to do the work.