epoch Prime

[pier4r]

(01-06-2018 08:37 PM)Dieter Wrote:  And that's why proofreading usually is done by another person.

Tips if your are "solo".

1. Rubberducking. Tell out loud to a rubber duck what is your code doing. Or even better, register yourself as if you would release a youtube video explaining your code. (the registration can be just an audio). Seems stupid, but do it! it works. There are people that share development sessions on twitch. It seems crazy, but the motivation of showing some work to someone else is enough to keep them going.

2. Point and read. Point (with a finger) the code/writing and read it.

3. change font (size, typeface) when you proof read, or the background color. It seems crazy but it works.

4. paper debug. Like the old days. give an input to your code and go through it manually.