>>106890295
>how do I even start to think like a coder?
>"break the problem down into smaller problems"
This is exactly how you start to think as a coder.
Instead of looking at the complete picture of the project, look at the small steps in between.
>I always run into a massive invisible barrier
You probably run into issues with your code, because you used an incorrect syntax, and this makes it seem like the entire thing is "not working", when in fact it might be just a small fix that needs to be done.
You say you code in PHP, so I'm going to assume you're making a website.
Instead of testing in the main PHP file, once you encounter an issue, you should isolate the code, place it in a new file, and focus on getting the output that you're after.
Use the "die()" command to check the output of every single line in the code.
Go through it, one by one, and find out where things are going wrong.
Then use Google to find old StackOverflow threads, or even consult with ChatGPT about the problem.
Troubleshooting in PHP can be a pain, as I've come to learn from my own experiences as a PHP developer, but the steps for troubleshooting are the same as with any other coding language.
There's some small tips to getting better error reporting set up though, so try placing this at the top of your new debug.php file:
ini_set('display_errors', '1');
ini_set('display_startup_errors', '1');
error_reporting(E_ALL);
The most important thing, is to remember to step away at times when it gets too much.
Struggling with an issue for hours on end isn't enjoyable, and eventually it'll burn you out completely. I think that is what has happened here.
Be sure to take breaks often, and then come back to the project once you're ready for it.
You might even come up with some new ideas, which can help you troubleshoot, in the time that you spend not worrying about the code.
