need help with feeling unmotivated
so as all of you know programming can be complex and we may have number of problems that are more than the number of atoms in the entire universe. I have a project now it has 27 red errors 5 warnings and zibillion blue mesaages. i really dont feel like going over them but i kinda have to. what do you do in such situations to push you into doing ir
8 Replies
Well, the best way is to not let it get to this spot. You see an error, you fix it, you don't wait until 32 of them amass
Failing that, just take them one at the time
it was going like that
then i changed my mind hence some parts of code
then this happened
almost everything red underlined hate it
Means you changed something with no regard for the code that uses it, and now that code is broken
So, next time, take more care
Right now, the best you can do is fix the errors one by one
Or rollback the changes
I know that thats the case. how do I push myself into doing it?
everyones life energy is sucked into oblivion when their entire text is red
Are you using vs code?
What did you change?
Is it something like renaming?
Based on the change, resolving something may actually clear multiple errors but really can't say without context of what changed and the errors.
Either way, like previously stated... your choices are to revert or start fixing things one by one
Far as motivation goes... motivation is rarely sufficient
Motivation is fickle
What isn't fickle is, say, schedule. Even the simplest of schedules
Every day, 19:00 o'clock sharp, spend at least 15 minutes working on it
You might not achieve anything
You might spend two hours instead and fix it
Also, recontextualizing it might help. For example, I like tracking down the sources of warnings and exceptions. It's a puzzle
Sure I might get frustrated, but I'll go for a walk, come back, and try again.
Or I'll drop it for a week and come back to it
Like I would with a boss in a game that I cannot beat lol
Maybe think further about the colors. Errors/reds are just immediate messy things you need to resolve to get the jobs done. Warnings/yellows can wait. Information/blues are there to tell you that in some places you might have to think twice and improve your coding styles. Then depending on what kind of project you are working on, you can build up different strategies to attack them one by one.
In your current situation, just focus on the 27+5 items, and leave the rest for another day.