> On a whole, what are the hardest/most boring parts of building web based software? What are the easiest/most enjoyable parts? in general, for me, the best pa

> On a whole, what are the hardest/most boring parts of building web based software? What are the easiest/most enjoyable parts? in general, for me, the best part is the problem solving and building out the thing you created in your mind's eye. the hardest and most boring parts are everything else. > How important is developing with efficiency and scalability in mind? depends on your goals and what you're building. for you, you should be more concerned with building something that works, and learning about things in the process. > What should I dedicate most of my learning time to? decide that you want to build something, and build it. take baby steps, build a small version of your final goal, and add to it. > How do I know if I am producing spaghetti code? I can’t tell good code from bad code. spaghetti code is like art. its hard to define, but you know it when you see it. in the past, it was used to refer to code that makes use of GOTO type statements, where its tough to track the flow of the program. that still exists, but its much less prevalent. now its more used to refer to "bad" code in general.