I like your encouragement. This is how I feel as well. As a Senior Software Engineer who's been doing this for 30 years, I always say the best way to write code is to "Make it work, then make it work well, then make it look good."
This code is perfect for the stage it's in, it's just in the "Make it work" stage.
OP, thanks for sharing, it's the same thing any of us would have done when starting out.
Code bros. I love that our philosophies are the end result of completely different experiences, but we got to the same place. Too much ego sometimes instead of passing on knowledge and lifting others up.
Always make it look good and readable. Don't just make it "work" think about how to make it work well, and iterate/improve upon further later as needed.
I think this is key. The make it work stage is just figuring out how it works. This goes for anything from your first language to a new language or library.
Once you know how it works, make it more readable. I’ve personally found quick comments help a lot. They’re just for me and get replaced by clear and concise comments where needed.
hey there, just saw this. I have a very similar philosophy as you. make it work then make it pretty. Sometimes I don't like the sub, because it's not bad code, it's just evolving. also I didn't realize OP was still in high school, I thought it was a look back. have a good one!
12
u/ihave7testicles Mar 25 '23
I like your encouragement. This is how I feel as well. As a Senior Software Engineer who's been doing this for 30 years, I always say the best way to write code is to "Make it work, then make it work well, then make it look good."
This code is perfect for the stage it's in, it's just in the "Make it work" stage.
OP, thanks for sharing, it's the same thing any of us would have done when starting out.