engine - 12:16 pm on Jul 14, 2011 (gmt 0)
It's about job satifaction, imho, not about what you're actually doing. Of course, if you hate what you're doing, then that's time to move on.
When developing one part of a site you may not see the overall picture, but you may glean satisfaction from knowing that your part of the development achieved success in the project as a whole.
When I was a kid, the computer programming class was the first of its kind. We wrote very simple programs run on mainframe computers with punched tape, 300 baud modems, etc. We ran the tape through the reader, waited, and the answer printed back on the remote terminal from the mainframe, 'hello world.' It was exciting.
Over time, we moved on to more sophisticated programs, and were focused on creating part of a program for a team. This required a different level of dedication as the end result was not all my own work. If someone else had written bad code the program didn't run. So we all worked together to analyse other students code.
Subsequent to that, I too moved into hardware as I always enjoyed making things. Similarly, as a student, I either made the whole thing myself, such as a radio transmitter or receiver, or we got involved in part of the design and manufacturing of a complete system, where one would make the main amp, another would work on a pre-amp, another would work on the oscillator, another on the receiver, etc. It was great to see the whole thing come together to make the end result. As a student, it wasn't quite job satisfaction, it was project satisfaction. For me, it was about knowing that my part worked, and the overall project worked, too.
If you're questioning it already, and that feeling doesn't go away relatively quickly, then it's possibly the wrong path.