While this is true, sometimes you work on a very large project, the end goal of which you will never see and don't really understand. The abstractness of the wo

While this is true, sometimes you work on a very large project, the end goal of which you will never see and don't really understand. The abstractness of the work you are doing can be challenging for people who like to be excited about the end product. For instance, a while ago, I was working on a large industrial project. Between me and the customer were a layer of business analysts who figured out what the system did, and a layer of systems engineers who worked out the specifics of the system in terms of components with interfaces, and logic flow charts for what those components did in different situations. For one assignment, I needed to make a value returned by a webservice change when a GPIO was toggled to indicate a button had been pressed. I didn't know what the button did, or what the result meant, and communication with the systems engineers far away was through JIRA tickets. I didn't even ask because the management didn't like off topic comments on the tickets. I think it was a custom feature for an oil tanker, but who knows what I made... While that way of working was very productive, and produced reliable software built to validated designs - with lovely code because we could really focus on it - it was really hard for me personally to feel any passion there.