The Capstone Strikes Back
At the time of this post, I am currently in part two of three sequential Capstone courses going from Fall 2023 to Spring 2024. I am prompted to cover my experiences with clean code and code smells so here it is.
A good practice that I try to follow when coding is to use version control, like GitHub, in a smart way. I think of it as a really organized diary for my code. Every time I make a small change, I save it and write a quick note explaining what I did. This helps me see how my code has evolved over time. Also, when I’m working on different features or fixes, I like to create separate branches. It keeps everything tidy, especially when collaborating with others. I expect to exercise this when it comes to employment in the real world.
On the flip side, a bad habit I try to avoid is making my code too complicated. It’s like putting all my things into one big box – it gets messy! I believe in keeping my code neat and breaking it into small parts, each doing just one thing. If my code becomes too tangled or does too many things at once, it becomes challenging to fix issues or make changes later. Plus, it makes it harder for others to understand what I’m trying to accomplish.
Leave a Reply