4 ms·
I've always had a fear of writing spaghetti code that it had prevented me from actually coding. I think that has been a big hurdle for me starting out. Reading
by nova2wl 14y ago
I've always had a fear of writing spaghetti code that it had prevented me from actually coding. I think that has been a big hurdle for me starting out. Reading articles like this though definitely helps me out.
- mattmanser 14y agoI get this from time to time, analysis paralysis. I go build some tiny and completely unrelated to get me to enjoy programming again. Usually works.
- gtrak 14y agoI always expect to mercilessly refactor what I write, though it's good to remember users don't care if your code is top notch, it's just something you do to make your own life easier, to simplify adding features. The ego aspects just gets in the way, especially if you're the only person working on it. In my experience, I'm always more productive with some code and building blocks to arrange than a blank canvas, and as you gain more experience it's easier to see corners before you code yourself into them.
- weaksauce 14y agoStart writing. Commit often to a good source control system(git or mercurial but I prefer git). Refactor your code when you see an abstraction. The hardest thing about any task is just starting it.
- pacaro 14y ago+1 to this. For me learning to "Refactor your code when you see an abstraction" came only when I had to work in an environment where failing to do this caused pain (writing Win16 OLE/COM code in C) I don't advocate masochistic practices as a means of self improvement per se, but the same habits can be built using intentional practice wherein you choose (for the purpose of the exercise) to take strong constraints on the style of your code.
- gte910h 14y agoI'm a professional software product developer who writes messy code all the time (true spagetti code isn't really possible today, it's a thing done only in assembler). After awhile you realize the pain of doing messy everywhere, and do it only where it makes sense (Prototypes, quick fixes, first implementations, etc). But you know what runs worse than messy code? No code at all.