- Don't shy away from lots of work to accomplish a task. If you do it anyway, the workload will come back even heavier.
- Test critical code. That means when you don't know whether it's working properly, test it. But also don't test every little piece. That is just time-wasting.
- One step at a time. When you do a task at a particular section of your code, focus onto it. When you see bugs, typos etc somewhere else, note it, but don't waste your focus fixing that issue quickly. Keep your focus.
- Make a beautiful todo list of the ongoing tasks. Break them down and WRITE it down. Otherwise you will often lose your thread.
- Plan new features thoroughly. Use pseudocode and think about what you could have missed in your first thinking phase. Think through the concept multiple times. It will save you time in the long run, as you won't make so much critical mistakes.
- Celebrate working code pieces. Really. Do it. You have done great work, no matter how small or complex the code.
- Don't expect your code to run without bugs the first time. However if it does, you are doing something really correctly (jump to tip 6).
- When you encounter a problem, write it down. Really deal with it, so that you really understand what the problem is. Then start asking questions. What do you need to know to solve this problem. Find answers. The problem should start to crystallize into smaller parts. Ask again questions, until you know everything essential to solve the problem.
- Beware of the edge cases. Those little nasty beats...
Nico
Posted on
My learnings
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)