4 ms·
The closer I'm getting to a release version of my side-project, artjutsu, the more I realize that the code is just gonna be an ugly ugly mess. I could take the
by sreyaNotfilc 8y ago
The closer I'm getting to a release version of my side-project, artjutsu, the more I realize that the code is just gonna be an ugly ugly mess. I could take the time to make it beautiful, but that's not helping anyone. Not at the moment.
I feel that I'd rather have some un-easy code that is not optimized so that I can have something cool for people to use. Besides, if its successful, I could go look back and make it optimized and beautiful.
Getting things done is what matters (at least for me at this point).
- avgDev 8y agoI keep telling myself I will refactor....but I rarely feel like it because I would rather work on a new exciting project. In the end, I still learn a lot, and I usually will refactor when a bug is discovered.
- sreyaNotfilc 8y agoSame here. I'm currently working on a part of the site where it should be refactored, but I chose not to because I just want to get the functionality to work. Once its good, I'll find the similarities and then refactor. I'm also an artist, musician, and an athlete. I see similarities with those things and coding. In order to improve, you have to go through the "fog". That is, go with a concept , get messy, and see it through. In the "fog" I tend to second guess myself and feel I'll never get out of it. But in the end things tend to work itself out and I'm better for it. After 10 pictures drawing the same thing, the 11th one is almost always better. Same with coding. I find myself looking 3-4 steps ahead and eventually write better code because of it. All just from working on and seeing through projects.