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*
- But waht are the basics? Assembly, binary code?SiberianGuy– SiberianGuy2011-09-05 13:52:38 +00:00Commented Sep 5, 2011 at 13:52
- 5Whilst your general point of "know as much as you possibly can" is a sound one, I would question the idea that you will "NEVER be able to solve the really hard, strange, difficult and complicated problems that come your way" if you don't understand pointers. This somehow implies that all difficult problems can be solved using these "magic" pointers, which is not the case. The concepts between pointers are useful to know, but they are not directly essential to many fields of programming.Dan Diplo– Dan Diplo2011-09-05 14:10:39 +00:00Commented Sep 5, 2011 at 14:10
- 4@Idsa: no, even more basic, many programmer's nowadays don't even know how transistors and logic gates works in the goo' ole' chips, and they surely should have known how electrons moves about and the effect of quantum uncertainty on miniaturization; I haven't even started on quacks, liptons, and bison! and the Hiccups bison particles!Lie Ryan– Lie Ryan2011-09-05 15:34:21 +00:00Commented Sep 5, 2011 at 15:34
- 2Basics.... things like how stuff is stored. The difference between a byte, a word, how signed and unsigned work. How pointers work. What a character is. How things are coded in ASCII (and these days, Unicode). How a linked list can be created in memory using simple structures only. How strings REALLY work. From these little things, bigger things grow.quickly_now– quickly_now2011-09-06 01:29:51 +00:00Commented Sep 6, 2011 at 1:29
- 5Know as much as you possibly can is a good principle, but I think you have the cart before the horse. Good developers strive to learn whatever they can because they're good developers. The yearning for knowledge is a trait of a good developer. It is not the cause of a good developer. Going out and learning as much as you can will not make you a good developer. It will make you a walking encyclopedia, nothing more. If you're a good developer, THEN you can APPLY that knowledge you attained to solve problems. But if you weren't already a good developer, the knowledge won't get you much.corsiKa– corsiKa2011-09-06 18:01:52 +00:00Commented Sep 6, 2011 at 18:01
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
default