Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
I personally would just take time out of the day to look at some code that's not yours (doesn't have to be a coworkers could be online) and get use to figuring out what it does without be told prior to reading it. You'll eventually get better at it, and debugging other people's code is just the same as debugging yours-unless their code is just plain awful and has no structure whatsoever- the "detective" skills of debugging come with time and practice. Wish you the best!
-
MrPlow1718ySometimes it's helpful to take out a piece of scratch and a pen and map the data flow. Start at the logical beginning, and follow each step, noting what is happening to the data.
Also, if you know what a function or method should be doing, write some pseudocode out and then see his you would accomplish the same. That can help when trying to determine the logic flow. -
iceman9318ySoon you will want to use other libraries with poor documentation (like Firebase) and you will have to study other peoples code
Related Rants
-
linuxxx105HUGE FUCKING DILEMMA FOR ME. I will probably get the chance of choosing a company phone soon (as in, next few...
-
vortexman10018Got a job interview today at my favorite company. Wish me luck.
-
AleCx0417Dear diary: It is 2020 and I still don't know shit about docker :3 I don't know how bad this is.....
I'm very bad at reading someones code. For example when someone on uni asks me to help him with code I just write it from scratch, I can't find the mistake or even understand thoughts of this person. I'm afraid that when I'm going to work in team I'll be useless. Can I even do something with this?
undefined
halp