Don’t Just Write WordPress Code

Don't Just Write WordPress Code • WPShout

One of the first and most powerful lessons I learned while teaching myself to code a decade ago was to read/listen/watch widely. I believe it is one of the most powerful choices you can make in learning to code (or in almost any endeavor). Because broader minds (ones which have been exposed to more things) are often *way* better problem-solvers than narrower ones. Because the solution space they can conceive is just so much bigger. But that’s enough “David’s Life Philosophy” for now.

The reason I’m going on about that because it was precisely this same lessons I saw when reading this nice little essay from Justin Tadlock over at the Tavern. I think the specifics of Justin’s story are both useful and interesting too. But it was his close that meant I had to share it with you:

Another benefit of working with other platforms from time to time is that you learn ideas that you can bring back into the WordPress ecosystem. For example, it is interesting to see how the Sage starter theme implements Laravel Blade’s templating engine. These ideas can help shape WordPress’ future.

Some ideas can be pushed into core WordPress. Others can improve team workflows within agencies.

Continuing education benefits the WordPress community as a whole. Don’t limit that education to WordPress-specific ideas. Learn from the outside and bring it back.

Keep reading the article at WPShout. The article was originally written by David Hayes on 2020-02-20 15:16:31.

The article was hand-picked and curated for you by the Editorial Team of WP Archives.


This article was written by David Hayes and originally published on WPShout.

Disclosure: Some of the links in this post are "affiliate links." This means if you click on the link and purchase the product, We may receive an affiliate commission.

Leave a Comment

You have to agree to the comment policy.

Scroll to Top