Most computer programmers aren't really aspies are they?
From my experience, all of the good ones.
Most of the best ones I've known had AS traits. The NT ones, for the most part, don't give the attention to detail the work really needs. I also saw a lot of "close enough for the deadline" code go out the door, only to have it come back and bite us.
As for management, remember they're only trained to reach a consensus, not a conclusion.
Depending on the companies you have worked for, projects may be monitored through the use of 'Gantt charts'. Basically these are fancy schedules formatted to show, in linear fashion, all the steps involved getting through a manufacturing project (software release, hardware, whatever). Managers eat these for lunch because: 1) they don't need to understand or sweat any of the details 2) They can present them up the management chain - they look good, and reassure those who have an even lesser understanding 3) It's easy to point fingers at individuals who are creating a bottleneck and slowing things down, or perceived to be.
How do we know the product is ready to ship? In the eyes of NT corporate kiss-ass types (including managers and worker bees), "it has to be ready because we stepped through the Gantt chart". This reminds me of the old joke, "there has to be money in my account, I still have checks".
This has all sorts of dire repercussions for AS workers. We know that there are problems that haven't been sufficiently resolved. The product will ship and result in months of dealing with bugs that crawl out of the woodwork, resulting in all sorts of unexpected interruptions and crises which are aggravating. Finally, throughout the development process, we are expected to put our nose to the grindstone and "just complete" the steps. As many of you know, this process is not inherently linear. You come up against issues which can't be resolved according to a calendar because they are either too involved, or require the type of thinking where you drop the issue for a week or two, and return to it afresh later, often with a more mature perspective.
It's my theory that hi-tech work life has been increasingly infected by the Gantt chart rot. It used to be that AS types could find refuge in R&D, off the beaten manufacturing track. With increasing emphasis on specific profit margins, this is becoming increasingly difficult because we all have to demonstrate value to a specific product, at a specific time, which is expected to generate a certain rate of return, during a certain quarter of the business cycle. Yuck.
Welcome to my world, except they're called 'work breakdown structures' rather than gantt charts. And they're totally BS. We usually just start with the date the project has to ship then work backwards to fill in the rest the 'milestone' dates- and get blamed when we miss them.
I used to be a computer programmer, in a small software company. As far as I know I was the only one who would display AS like tendencies. I would like my source code written in a neat orderly fashion (whether it worked or not!), of course going through the development and testing of program. When I got stuck in debugging, I would get frustrated and shout a lot, which disturbed the others!
But I would like to think that a higher proportion of programmers are As whether diagnosed or not. Up tp 50%.
The course I'm doing this year at school is a programming/web design/robotics/sysadmin/office/desktop publishing/general design course, and we use gantt charts for everything. Project management and the design process are a big part of the course. It sucks.
It's taught by a really great teacher who I have a lot of respect for, but I just can't get the hang of the design process. Planning is a good thing, but with the robotics project I have spent two weeks (of a five-week project) just writing a brief, doing research, planning and project management (including a Gantt chart and a task list), and concept design. That's too much planning for me, I just want to grab a robot kit and go build something awesome.
I worked out the mechanics for a simple walking robot in 20 minutes after school. A really cool idea and a basic understanding of how to make it work, that's all the planning I need. This project managment stuff just gets between me and my work, especially when programming.
I personally think the medical field and a few others are suffering in the US because people are doing it for the money, not because they want to help people... anyways
I have a degree in computer and electronics. I have worked for two companies since I got my degree. I did very well as far as doing the job and getting it done on time. For both places I was often the only one that could get work done as fast as managment wanted. But I suffered because I didnt make friends. I guess having a good paying job means you have to go out with coworkers and get drunk.
I did fairly well at the first place. The reason for this was that I was able to meet deadlines when others often couldnt. This company does airline cargo. An hour late on work could mean millions of dollars lost so time really was money there. Because I was able to outperform basically everyone I was left alone. That was until people in the same field in another branch of the company noticed I was making them look bad, over a year went smoothly but only 3 months of those people made me quit, sadly it was a very well paying job, I could almost pay all my bills with 1 weeks paycheck... In the end this ended being more of an age issue. I was half the age of the people above me who couldnt do what I was, as well as in charge of several people twice my age. Add the fact I cant stand the idea of kissing anyones butt with ego problems and you get me hating my job.
well as always way off topic, I really wish I didnt do that all the time.
Going to college at a tech school with nothing but people that are geeks I fit in well but I would have to say that there was very few if any others there on the spectrum. The school had a rule that for graduation pictures and the mock interviews and whatnot they do everyone had to dress proffesional(IE a suit and tie) I of course didnt listen, and was the only person in over 10 years to refuse to wear one.
Brian003
Velociraptor
Joined: 10 Sep 2007
Gender: Male
Posts: 402
Location: University of Michigan Ann Arbor
My supervisor is not, but I wish he was. Then he'd be less annoying.
Hello, I'm new here: I'm just quoting you to post here.
I tried Computer Programming my sophomore year in College.
Was probably the worst(And most boring) school class I had ever taken in my life. It was okay at first but it got into writing codes for crabs game and I got out fast.
The only reason I was interested in Computter Programming was because I like games. Programming is nothing like games though(As I found out). Man, I don' even see how Aspies can like programming, itsjust so boring; it seems like something a computer should do automatically .
Heh... well in order for the computer to do anything automatically (which really is the idea behind computers ultimately), someone has to invent the automation. If that invention part were easy then very few people would really be able to earn a living programming computers, because everybody would just do their own programming, the way that people mow their own lawns or write their own newspaper ads. Give it another hundred years or so and that may be the case, like the characters in Star Trek who program the holodeck via a simple conversation with the ship's computer. That's an example of the automation catching up to your notion of programming being done automatically and you notice in the show, none of the characters ever ask anyone for help programming anything, they pretty much all do their own programming "work" because there's no point in asking someone else to "come in here and tell the computer to dim the lights".
From my experience, you often can tell from the code (and structure) a software developer writes.
Aspie code is more often very ... em ... dense. We tend to tinker with the details more often than a typical CS student.
Well, at least i do. I once rewrote a program a fellow developer (NT) wrote. Well the software worked beforehand - most of the time anyway - and after i tinkered with it, it was twice as fast and the code size was about 10% of the original. Thinking back, in the course of the development, i once spent a whole week on a single line of code that replaced a 100+ line function.
I only met 3 or so other aspies in the trade, but we shared another distinction from the NTs: We all hated paperwork and the design-phase; when the boss stopped explaining the new project, we sat down for a coffee, made up the software design in our heads and started programming. We were mostly finished by the time a group of NTs with a similar task finished design phase, so we were free to tinker with the code until deadline
There are two of us in a department of twenty or so. I'm not a programmer, I test software, they've found out I'm good at spotting things that aren't working properly without even knowing what is wrong, I just know it ... The other guy codes our hardware abstraction layer, he's a bit more NT than me (he's a father for starters), but he has more problems with tapping than I do with my knee shake so swings and roundabouts..... we've got plenty of good coders who are perfectly NT though, you don't have to be an Aspie to care about good code......
chrisc
Brian003
Velociraptor
Joined: 10 Sep 2007
Gender: Male
Posts: 402
Location: University of Michigan Ann Arbor
I don't know: I sometimes wonder why I am so horrible at technical skills and at school in general.
When they say that most people who have Asperger's are good at technical skills this is definitely a distinct stereotype.
I am the type who needs to study 10 hours to get a B on like a history exam in like Government 101.
For Programming 101, When I took that class it was probably one of the worst experiences I have ever had in my life: Nothing the professor said made any sense; the book didn't make any sense, and even the special instructor in the computer lab totally confused because she said I should stop taking "everything so literally."
Engineering= BAD.
I honestly think the thing I am best at is ummmmm making other people hate me or like me. It is kind of hard to explain.
heh... odd thing to say, given that computers ultimately are incapable of not treating their instructions literally. Though when we talk about the code or the behavior of the computer, everything is described in metaphors... "viral", "parent", "slave"... "visitor pattern", "bridge pattern", "pipes and filters".
Now there's a talent I wish I had.
Similar Topics | |
---|---|
Tories: Lunch is for wimps and sandwiches aren't real food |
Yesterday, 7:05 pm |
Grace Hopper - Pioneer of Computer Programming |
24 Oct 2024, 10:47 pm |
Why do people recommend working in IT/Computers for Aspies? |
21 Nov 2024, 10:26 am |