Architecture before code

Computer programming is exciting in some sense like a computer game or puzzle it gives us the instant gratification kick. This could hurry us to the coding part earlier than it could be optimal. We can easily narrow down solution approaches and limit our thinking to the approach we have taken in code. Therefore, it is a good practice to take a step back and think about the problem and architect the answers on maybe traditional pencil and paper or drawing boards.

Spending time to think about solution abstractly before getting down to write code can help us do better at design and architecting scalable solutions.

Writing code might be the last activity in development process you want to schedule