5 Ways to be a Jerk When Developing WordPress

WordPress users nowadays can learn to protect themselves from badly-coded themes and plugins with the help of the community and the thousands of best practice articles out there. However, if you – the developer – intend to make a fool out of them then those users are totally defenseless.

It’s simpler for WordPress developers to tell the good from the bad WordPress products, and they can absolutely cross out the bad ones and utilize the good ones. However, for normal WordPress users, it’s a different story.

Well, if you want to be a jerk and be irresponsible with what you’ve been making for the WordPress community, then follow these 5 practices. Otherwise, never commit any of these following and you’ll be on your way to be a great WordPress developer.

Insert outdated jQuery in your WordPress theme or plugin

An ignorant and selfish WordPress developer will not care much about whether the code they bring into a plugin or theme is up to date or not. They just need things to work the way they want and ignore everything else. Until there’s someone downloading the plugin or theme, then… crack! Oops. Something breaks.

Outdated code, especially outdated jQuery code, usually leads to conflicts with the latest version of WordPress (you can learn more about it in the WordPress codex). Don’t be that bad guy who creates low quality WordPress products to break websites and break hearts. Make sure your work is appreciated by everyone in the WordPress community. If you need to keep your jQuery updated, it’s not very difficult. Just use this line of code:

wp_enqueue_script(‘jquery’);

Actually, there are many developers who choose to use Google Library instead of WordPress jQuery. Google Library has become a standard in web development and it helps your website load faster.

Make a boasting WordPress theme with unnecessary functionality

I’ve discussed this matter quite many times before. Creating a WordPress theme which is full of functionality is not the right way to survive in the WordPress market anymore. Why? Take some minutes and review my argument here.

A WordPress theme is supposed to deal with the appearance of your website only, not how it operates functionally. So, what’s so bad about inserting functionality in WordPress theme?

It’s not necessary. The theme doesn’t load any faster than using plugins for the functionality instead. And it’s extremely annoying for users when they want to switch theme. All the functionality and customization disappear and they have to rebuild everything again.  Not to mention that you will have to invest more time in making and updating that kind of theme.

Ignore debugging while developing WordPress

debugging-wordpress

Debugging should always be in your heart whenever you develop a WordPress theme or plugin. Turning on debugging helps you effectively when there’s something wrong with your code. It will notify you with error messages so you can find and fix things easily.

Debugging also lets you know if you have deprecated WordPress functions. That’s how you’ll know when you should replace those functions.

Oh you don’t like debugging? Then why on earth do you ever want to create anything with WordPress? These dead functions are going to be removed anyway. So don’t be stubborn and keep them in your code.

Hack WordPress core

You are a true villain if you hack WordPress core when crafting your own WordPress theme or plugin. Never ever, ever, ever reinvent the wheel – this has been said a million times. And it’s true.

Hacking WordPress core is a bad idea, even when your life is depending on it. It’s not a brave act; it just shows how lazy you are regarding seeking the right way to make things work. If you dig in deep enough, you’ll see WordPress functions or plugins that can help you with the feature you want.

My final warning on this matter is that hacking WordPress core will make your site more vulnerable to security attacks, potential incompatibilities, and so on.

Add malicious code to your own theme and plugin

It’s a dirty cheat and shame on you if you leave bad script, harmful code, or spam links in the theme or plugin you created.

Many WordPress users, after happily downloading a free theme and installing it on their site, have been hurt so much when their website gets hacked. They are left with confusing questions, and you – the devil behind this – just sit there and watch them cry.

Don’t be a WordPress criminal!

(Michael Jackson singing) Now the whole world has to answer right now just to tell you once again: Who’s bad?

You are, if you have been doing any of the things above. Don’t be bad. Pour your effort and talent into building great products and a better WordPress.

Have you seen anything worse? What do you hate the most when using WordPress themes or plugins from other developers? Feel free to comment your thoughts below. And don’t forget to share the knowledge around.

 

This blog was written and published on WPDemobuilder.com in Oct 2014. Featured image’s credit: WPDB

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s