Let's talk about the next part of Computational Thinking, which is Pattern Recognition.
A big part of the daily developer work is dealing with patterns. Sometimes it's more about patterns in data such as (75% of people who bought a croissant also bought a Latté), other times you focus more on patterns in your code.
A common pattern could be that the user input always need to be validated before it can be saved. You first implement this code in the insert method, but turns out that the same code is also needed for update as well.
Detecting these patterns can help you to make more informed decisions about how to write code. This also sometimes involves higher abstractions, as in making sure that the code for validating user input is only written once and can be called from multiple places.
Can you relate to this? Is there more from your side that goes into pattern recognition? Comment below!
21 Lessons helps Junior Developers to level up their skills step by step via their weekly newsletter. Do you want to get out of Tutorial Hell or you're wondering how you develop the skills to write sophisticated programs yourself? Sign up and receive weekly articles and recommendations right in your mailbox.
Top comments (0)