You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
10+1, and I'd upvote it more if I could. Every serious developer needs to be able to read ASM for this if no other reason.Mason Wheeler– Mason Wheeler2010-12-17 15:54:03 +00:00Commented Dec 17, 2010 at 15:54
-
3The corollary to this is optimization. Knowing how the complier translates your code into assembly can help you to make it dramatically faster!lambacck– lambacck2010-12-17 17:54:02 +00:00Commented Dec 17, 2010 at 17:54
-
3+1 Assembly is one of the only languages that force you to understand how a processor actually works. It helps you in your development with high level language. Must read: blogs.msdn.com/b/ericlippert/archive/2010/09/30/…user2567– user25672010-12-17 19:52:42 +00:00Commented Dec 17, 2010 at 19:52
-
Knowing the underlying computer is INSANELY helpful, whether for debugging, optimization, or sheer curiosity. Seriously, learn to read at least one or two families of assembly language. Even if you never read it or write it after learning it, it will affect the way that you understand things in the future. Now, if you would rather write in no other language, that might be a bit much...Michael Trausch– Michael Trausch2010-12-17 23:26:15 +00:00Commented Dec 17, 2010 at 23:26
-
1@Mason: I don't know if "every serious developer" needs to be able to read ASM. If you are writing JavaScript or using a programming language built atop a thick framework (like .NET or Java), I wouldn't regard being able to read ASM as essential to being a serious developer. That being said, having an understanding of how the computer executes instructions on a very low level can be quite helpful, even in higher order programming languages and environments.Scott Mitchell– Scott Mitchell2010-12-18 00:01:15 +00:00Commented Dec 18, 2010 at 0:01
|
Show 3 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you