So far, of all the patterns I’ve encountered, Reflect as you work seems to be the one that can be most easily tracked in a more concrete form! This is very interesting to me because many of the other patterns deal with almost abstract topics, whether it be considering how you yourself grow, or how to approach learning, it is usually hard to determine your growth, but Reflect as you work makes a tangible ‘map’ that someone can reference!
Reflecting as you work, to put it simply, is the process of making some sort of way to track what kinds of things you are doing. It seems like it could be a map of your skills and process, or it could be a variety of other things. But essentially, as long as you are making a way to visualize the types of skills you have, it is a way for you to go over each of those different skills and see if things are working, or if they are counterproductive. An example that was made was that if someone made a map of these skills, they can go over them as time goes on, and though this process or that approach might have worked in the past, it might need to be updated, or transformed all together.
Overall, this is something that I have never really thought about doing, but it seems incredibly helpful. No doubt, if I made a map of my own skills to reflect on, it would make it blatantly obvious to see which things I am lacking, or even better, which things to improve on. Already, I have an idea that my algorithm skills are a bit lacking, but I am sure that there are other things that I can improve upon as well. With the creation of a visualizer, I can much more easily reflect on the type of work I am doing, and overtime, I can also see if the things I am doing are good, or a bit flawed. I know for a fact, that if I looked back at my older works, I’d be complete horrified by some of the ways I fixed problems, and I know that in the future, it will be the same! This process of reflection is usually just internal, but with a concrete tool to use, it would probably be so, so much easier.
Bored Coding 