Disclaimer: This post is going to be pretty short as it’s more of a rant than an actual post.
So, one thing everyone knows about developers is that we all run into errors, bugs and problems with our codes a lot. Like someone said, as a developer, you spend 80% of your time fixing bugs and errors and I’ve come to almost believe that statement.
As we all know there are mostly two types of errors you would always come across as a developer, namely:
- Syntax Errors: Where there is an error with the syntax of your code and it throws errors telling you where the error originated from and what’s causing it. (Emphasis on the ‘telling you’)
- Logical Errors: Where the program runs successfully without throwing any errors but it does not give the desired results. (These are errors you always want to be extra careful of)
I will be ranting more about syntax errors today as, in my little (not up to 6 months) career in tech, I’ve already grown tired of peeps coming across syntax errors in their code and not knowing how to solve it, like — the error code and the big G exists for a reason bruh.
When you come across a syntax error, your program does you well by giving you a run down of what’s causing the error, so kindly read through it and try fixing it by following through with what the error code tells you. The error code almost always points to what’s causing the error.
In the case where you don’t know how to solve the error, the big G is always there to help you out. There’s always a probability someone has encountered your problem and they have documented how they got to solve the problem, that should also provide a pointer on the solution to the problem for you.
Most times, when you get to ask people the solution to an error you are getting and they don’t have a ready response, they would also have to consult the big G before getting back to you.
So, to put a stop to my rants I would say —
READ THE F’ING ERROR CODES BRUH!