After a couple internships and part-time jobs, I'm thinking maybe programming as a career isn't for me.
*I'm a very detail oriented thinker, I have to see implementation level details first before I understand the big picture. Unfortunately, I often can't see the field for the trees. As someone who's working primarily on web dev/ application dev projects, this causes a lot of problems for me, because:
- I often focus on implementation level details that don't matter.
- I have trouble communicating with team members about big picture concepts. Often info-dump implementation details that they don't care about while missing 'the point'. Often can't process 'the point' without understanding implementation details.
- The code that I write is often very self contained and doesn't interface with the overarching system well at all
- My solutions technically solve the problems I'm given but aren't necesarily best for the goals of the project
- Have a hard time writing architecture unless I've already finished the implementation, at which point its probably too late
- Often slower because of all of the above
This detail oriented thinking is a problem I have in life and it isn't something that I can do much to change*. I've already seen coworkers who just 'get it' leaving me in the dust.
What should I do here? Should I just quit the field? Are there any books or resources that can help? Are there any specific programming jobs that benefit from this kind of thinking? I'm thinking maybe IT would be better for me.
I'm graduating in December and I really want to be sure this is the right field for me before diving in head first.
*
*I'm a very detail oriented thinker, I have to see implementation level details first before I understand the big picture. Unfortunately, I often can't see the field for the trees. As someone who's working primarily on web dev/ application dev projects, this causes a lot of problems for me, because:
- I often focus on implementation level details that don't matter.
- I have trouble communicating with team members about big picture concepts. Often info-dump implementation details that they don't care about while missing 'the point'. Often can't process 'the point' without understanding implementation details.
- The code that I write is often very self contained and doesn't interface with the overarching system well at all
- My solutions technically solve the problems I'm given but aren't necesarily best for the goals of the project
- Have a hard time writing architecture unless I've already finished the implementation, at which point its probably too late
- Often slower because of all of the above
This detail oriented thinking is a problem I have in life and it isn't something that I can do much to change*. I've already seen coworkers who just 'get it' leaving me in the dust.
What should I do here? Should I just quit the field? Are there any books or resources that can help? Are there any specific programming jobs that benefit from this kind of thinking? I'm thinking maybe IT would be better for me.
I'm graduating in December and I really want to be sure this is the right field for me before diving in head first.
*
Because I'm on the spectrum...