Tried and True; Troubleshooting.

Entrepreneur, teacher, developer.
Search for a command to run...

Entrepreneur, teacher, developer.
Those are great tips! I'm familiar with xDebug and definitely think that would be a great call out. I'm not familiar with Node Inspector though or Clojure — I would have to look that one up.
If you can sum up Web3 in one word — I think most people would say "decentralized." While I do enjoy the idea of a decentralized web — I doubt that it will truly be "decentralized" as massive whales, corporations, and governments move in to invest th...

Whether it's a Zoom meeting or recorded content — I've been asked on several occasions what gear I use — and each time, I piecemeal a list and send it. So — I've decided to break down each piece of audio gear that I use and its purpose so anyone inte...

In previous articles, we stepped through making a plugin from the folder to the file and adding some practical functionality. This article will dive in much deeper and learn how to create a plugin and prepare it to release in the world for production...

In the previous article — we walked through creating a plugin by only adding a folder, a file, and the plugin header information at the top. This article will create functionality for our plugin to help demonstrate how you can build your own WordPres...

WordPress plugins can be as simple or complex as you want them to be — and they are ridiculously easy to create, like, super easy. In this article — I will walk you through creating a WordPress plugin in a way that I've come to learn, and hopefully, ...

The key to becoming a great developer is learning how to troubleshoot effectively.
Every language and platform has built-in methods for troubleshooting. For example — Javascript has console.log() for printing things into the console within dev tools so you can tell whether a function or variable is working correctly.
In PHP — you can use things like var_dump() and print_r() to do something similar.
In this article, I will go further with examples of how you can quickly and effectively troubleshoot in any situation you might find yourself in.
Regardless if you're using a JS framework or good 'ole vanilla Javascript — console.log() is hands down your best friend when it comes to figuring out problems.
Are the variable settings? Is it a string or an integer? Is it an object or an array? Is it NULL?
Just console.log() it, and it'll keep you from aimlessly guessing.

If you are using a JS framework like Vue or React — you'll undoubtedly find a ton of value in downloading and installing the following Chrome extensions.
Once installed — you'll need to close and reopen your Chrome dev tools to see the new panel. Within this panel are loads of helpful tools that allow you to see what's happening in your Vue and React app.
There are tons of fancy environment setups for getting error logs to print out on the screen. However, two extremely powerful functions allow you to diagnose what might be happening with your code quickly.
The for one is var_dump(), which can be a little misleading because it does more than handle variables. It also handles functions too!
<?php
$name = 'Duder McDuderson'
var_dump($name);
?>
Passing a variable function or object in var_dump() — the next time you refresh your webpage — it will display what's happening.
I'll often use it when setting up loops and conditional with something like var_dump('test') to check if the conditional logic works** the way I want it to.
The other function — print_r() — does the same, but in some environments, it will print the data out in a human-readable way which can be extremely beneficial when working with arrays and objects.
When you find yourself scratching your head — do not hesitate to reach for any of these built-in functions. They will help you save loads of time and get you through some frustrating moments as you're out there building out there in the wild.