Debugging

I wouldn't say print("test") is that badass as depicted.

I like doing it as stupidly as possible.

works in JS.

debug = function (msg, status) {

let currentStatus;

if(status === 0) {
currentStatus = "[+]";
} else if(status ===1) {
currentStatus = "[*]";
} else if(status === 2) {
currentStatus = "[!]";
}

console.log(currentStatus + " " + msg + "\n");

}

Nothing wrong with simplicity 🤷‍♀

Powerful debugging tools often have side effects as well. Some make your code slow, or interact with code in unpredictable ways... so if some dump or log statement works for your purposes, why not.

One trick I find essential though is to add some kind of test to the CI/deployment which fails if debug statements are present.

Is there other way with php?

I don't do print("test"). I do print("aaaaa"). Most people some know it's power

@Ranchu

let currentStatus = ['[+]', '[*]', '[!]'][status];

@AlgoRythm This is great.
Actually thanks, I'll use it

Print("ass")
...
Print("butts")
...
...
Print("big butts")
...
...
...
Print("asses")
...
Print("ass butt")

I agree with you

@Jemis Thanks for sharing this post!

Great info

Think of it like a beginner guitarist learning how to strum a chord. This isn't a rock star solo, but it's the foundation for learning to play a song. https://fnafonline.io

printf(“i am here”); you know for the control flow

When tackling a complex issue, don’t just rely on one tool—leverage a combination of IDE features, network analyzers, and other debugging aids. The key is to be methodical and use each tool to its fullest potential to pinpoint and resolve issues.

When tackling a complex issue, don’t just rely on one tool—leverage a combination of IDE features, network analyzers, and other debugging aids. The key is to be methodical and use each tool to its fullest potential to pinpoint and resolve issues.