After my first contact with a computer in the 1980's, I taught myself to program in BASIC and Z80 assembler. I went on to study Computer Science and have enjoyed a long career in Software Engineering.
I have found that before tackling a significant piece of work it can be useful to identify areas that poss a particular challenge and prototype them in isolation (away from the rest of the code base). I have done this recently, captured the code and shared my thoughts with my colleagues. The result is, more often than not, a much better solution
@tracygjg good point, I agree with you prioritizing tasks before tackling them into coding is an excellent way to identify challenges and also help you with the amount of time needed for each part.
I have found that before tackling a significant piece of work it can be useful to identify areas that poss a particular challenge and prototype them in isolation (away from the rest of the code base). I have done this recently, captured the code and shared my thoughts with my colleagues. The result is, more often than not, a much better solution
@tracygjg good point, I agree with you prioritizing tasks before tackling them into coding is an excellent way to identify challenges and also help you with the amount of time needed for each part.
Yes, same here, when I started to "draw" first than code, even if it is a CRUD, it make things easier to solve later, and to pass to my colleagues