Comment Re: No, really, don't bother. (Score 1) 667
I am in an industry-leading company. There is no reason to use assembly.
Here's what I do for a living:
* XML
* Database
* Multi-threading
* Web-site design
* Real-time processing
* Data mapping
* Minor calculations
* Web services (straight XML or SOAP)
Assembly isn't worth anything in this environment. I also expect that the bulk of developers are very similar. Remember that the bulk of business code used to be written in COBOL? That's the type of software I'm talking about. We happen to be a J2EE shop, so we're working in Java. Our code is deployed to multiple architectures (x86/W2K, x86/Linux, SunOS, AIX).
I would be interested to hear how knowing assembly helps you with advanced algorithms and data structures. It seems to me that a higher-level language will help a lot more! Not to mention good OO design and component-based architectures.
Now, a bit of back-tracking. I'm not saying that assembly is worthless. There will be areas that it makes sense - but I really doubt that the majority of software developers have any use for those skills. Most developers are not:
* Writing low-level device drivers (graphic, network, etc)
* OS Kernel hackers
* Microcoders (I expect this to be the largest congingent in the list)
Face the facts, most developers must concentrate on a business problem at hand and efficiency at the chip level isn't a concern. In general, if you're worried about the computer's efficiency you better check your algorithm and/or design - there is probably one with a better fit!
In 14+ years of professional development, I haven't had to worry about assembly. In 20+ years of software development, the only place I worried about assembly language was on the trusty Apple IIe, my ONE class in assembly (not sure it helped), and now my hobbies with microcontrollers. That's it!
Here's what I do for a living:
* XML
* Database
* Multi-threading
* Web-site design
* Real-time processing
* Data mapping
* Minor calculations
* Web services (straight XML or SOAP)
Assembly isn't worth anything in this environment. I also expect that the bulk of developers are very similar. Remember that the bulk of business code used to be written in COBOL? That's the type of software I'm talking about. We happen to be a J2EE shop, so we're working in Java. Our code is deployed to multiple architectures (x86/W2K, x86/Linux, SunOS, AIX).
I would be interested to hear how knowing assembly helps you with advanced algorithms and data structures. It seems to me that a higher-level language will help a lot more! Not to mention good OO design and component-based architectures.
Now, a bit of back-tracking. I'm not saying that assembly is worthless. There will be areas that it makes sense - but I really doubt that the majority of software developers have any use for those skills. Most developers are not:
* Writing low-level device drivers (graphic, network, etc)
* OS Kernel hackers
* Microcoders (I expect this to be the largest congingent in the list)
Face the facts, most developers must concentrate on a business problem at hand and efficiency at the chip level isn't a concern. In general, if you're worried about the computer's efficiency you better check your algorithm and/or design - there is probably one with a better fit!
In 14+ years of professional development, I haven't had to worry about assembly. In 20+ years of software development, the only place I worried about assembly language was on the trusty Apple IIe, my ONE class in assembly (not sure it helped), and now my hobbies with microcontrollers. That's it!
