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@AndréParamés: Read Susan Lammers' Programmers at Work and you'll get a pretty good idea of Gates' abilities as a programmer. He was great at squeezing performance and space in 8-bit assembly language. The last piece of code he wrote all by himself was the ROM BASIC for the TRS-80 Model 100, again in hand-optimized Z80 code. His skills may be dated but there's no doubt he had them.dodgethesteamroller– dodgethesteamroller2013-07-04 16:00:27 +00:00Commented Jul 4, 2013 at 16:00
- 7The Gates quote is about productivity, and doesn't really bear on this question much. It's a response to those that measure "productivity" with something silly like "lines of code produced per hour" and is thus arguing against those who (implicitly) thing more lines of code is automatically better.user53141– user531412013-07-05 04:30:07 +00:00Commented Jul 5, 2013 at 4:30
- 3@AndréParamés: Even if Bill Gates was not a good programmer itself, he obviously knows how to lead a large group of programmers so that they create this kind of software he likes. Thus, I think one can conclude he knows how "good" software looks like.Martin– Martin2013-07-05 11:15:34 +00:00Commented Jul 5, 2013 at 11:15
- 1@StevenBurnap His point is that everyone knows a lighter aircraft is better, but only if all other factors are identical. The analogy is easily as appropriate for on-going operational costs involved in both, as it is for progress during construction.anotherdave– anotherdave2013-07-06 15:52:39 +00:00Commented Jul 6, 2013 at 15:52
Add a comment |
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