In the past, he has worked as the manager of a team. However, after asking if he liked it better, Paul admitted he enjoyed working as a team member and leader rather than the leader only. In the position he is now, he is in charge of a team, but he is more involved with the development process and can work on the projects as well. He stated that when he was the manager, Paul was helping the team advance but not as much as if he was also working on it himself. He said there is a sense of pride when you are able to work on a project, not just in charge of a team. For him, it is far more rewarding working with others on a project. I have found this concept true with projects. If the team is uncooperative, then the process is neither fun nor susceptive to learning. Also, if one cannot help with the project, it is even worse because contributing to a project is often more rewarding and an overall better …show more content…
Teamwork is key to success as well as a better experience creating software. Talking with Paul also made me realize that complete leadership is not for everyone. Despite being a leader now, before when he was fully the manager, he was not the happiest. He wanted to be more involved in the process as a developer and executer. That is completely understandable, especially to someone who loves to work on a project more than manage a group. Overall, the experience was rewarding being able to talk to Paul about his past and present working with software and developing it. I knew and finally understand what his job entails. The interview reaffirmed that software engineering is where I would want my future career. There is so much potential in the field as well as various aspects to consider. The field is not limited to only software but also what can be improved with code in general, how much it can accomplish, and how much it is used. It is fantastic how versatile it can