That actually makes a lot of sense and goes with how ill code something larger as well.
Get a rough version working, sometimes horrible code. See how it functions. Reassess it and optimize it. Go bug hunting, which will often result in more optimizing, then finish all the error handling I probably skipped and only logged. More bug hunting, then review my code like a code review before submitting it for a code review.
That actually makes a lot of sense and goes with how ill code something larger as well.
Get a rough version working, sometimes horrible code. See how it functions. Reassess it and optimize it. Go bug hunting, which will often result in more optimizing, then finish all the error handling I probably skipped and only logged. Then review my code like a code review before submitting it for a code review.
That actually makes a lot of sense and goes with how ill code as well.
Get a rough version working, sometimes horrible code. See how it functions. Reassess it and optimize it. Go bug hunting, which will often result in more optimizing, then finish all the error handling I probably skipped and only logged. Then review my code like a code review before submitting it for a code review.
That actually makes a lot of sense and goes with how ill code as well.
Get a rough version working, sometimes horrible code. See how it functions. Reassess it and optimize it. Go bug hunting, then finish all the error handling I probably skipped and only logged. Then review my code like a code review before submitting it for a code review.