Timeline for Able to read Code but struggling majorly to write it [closed]
Current License: CC BY-SA 3.0
31 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2018 at 18:49 | comment | added | brichins | @RobertHarvey An excellent follow-up and (partial) refutation of the study, I wasn't aware of it. I'm glad more research has followed from that study; it's interesting that the evaluation test is still a somewhat predictor, though it seems they no longer have a good explanation for why. | |
| Mar 19, 2018 at 19:21 | comment | added | Robert Harvey | @brichins: Not that the author of the "double-hump" story has since printed a retraction, of sorts. See eis.mdx.ac.uk/staffpages/r_bornat/papers/… | |
| Mar 10, 2014 at 15:46 | comment | added | Tulains Córdova | it's easier to watch movies than making them | |
| Feb 28, 2014 at 0:18 | history | closed | gnat amon Kilian Foth CommunityBot | Not suitable for this site | |
| Feb 27, 2014 at 23:38 | comment | added | David Conrad | If you were learning to play the violin, would you expect to become good at it just by reading about it, without picking up a violin and playing it? | |
| Feb 27, 2014 at 22:17 | comment | added | michaelok | Sounds like you are stuck on the IDE. Sometimes those can be overwhelming since they have a plethora of bells and whistles. Start with a simple editor like TextMate on OS X or NoteTab++ on Windows. Gives you 80% of what you need: create a file. Then use command line to compile or create a batch script. As you require more functionality, gradually move up. Some guys, like DHH (creator of RubyOnRails) still don't use an IDE so they certainly aren't required and sounds like the are slowing you down. And start coding: blog.codinghorror.com/quantity-always-trumps-quality | |
| Feb 27, 2014 at 19:50 | history | protected | CommunityBot | ||
| Feb 27, 2014 at 19:06 | comment | added | brichins | I found this to be a very interesting article while trying to figure out how to code and teach others the basics of coding: The Camel has Two Humps. Some people just get it immediately, others never will - but most of us can learn. If you can read and understand code, you're off to a great start :) | |
| Feb 27, 2014 at 18:53 | answer | added | Shaz | timeline score: 5 | |
| Feb 27, 2014 at 18:44 | comment | added | Superbest | Practice makes perfect. | |
| Feb 27, 2014 at 17:16 | comment | added | gnat | possible duplicate of How can I really master a programming language? | |
| Feb 27, 2014 at 16:06 | comment | added | Michael Shopsin | Programming requires both coding and someone to help you when you get stuck. I would not have gotten very far as a programmer in high school or college without some friends and classmates to help me out many times. Find someone in your dorm or class to help you out. | |
| Feb 27, 2014 at 15:33 | comment | added | Izkata | IDEs really can be imposing, they have so much stuff... I prefer a simple text editor like vim. Maybe that would help you, too. | |
| Feb 27, 2014 at 14:58 | history | edited | gnat | CC BY-SA 3.0 | personal and meta stuff removed |
| Feb 27, 2014 at 14:47 | answer | added | SeanWM | timeline score: 1 | |
| Feb 27, 2014 at 12:17 | history | edited | haylem | CC BY-SA 3.0 | making this language agnostic, seems to me like it's a more general thing than Java related, though I addressed that a bit in my own answer |
| Feb 27, 2014 at 11:57 | answer | added | haylem | timeline score: 15 | |
| Feb 27, 2014 at 11:27 | answer | added | Roy | timeline score: 3 | |
| Feb 27, 2014 at 9:47 | comment | added | Andreas | For a couple of weeks now I've been reading, reading and reading some more. - Reading is a start, actually coding is a lot better. Try writing a program in psuedocode on paper, then translate it to java. It's a bit easier if you already know what you have to do. | |
| Feb 27, 2014 at 9:43 | answer | added | Emil Lundberg | timeline score: 1 | |
| Feb 27, 2014 at 9:25 | comment | added | Philipp | Read less and program more. Find simple projects and do them. Don't worry about doing it perfectly, just get them to do what they are supposed to be doing. Then think about how you can do better. | |
| Feb 27, 2014 at 9:02 | answer | added | tobias_k | timeline score: 0 | |
| Feb 27, 2014 at 5:14 | review | Close votes | |||
| Feb 28, 2014 at 0:18 | |||||
| Feb 27, 2014 at 1:54 | answer | added | Rob Kielty | timeline score: 15 | |
| Feb 27, 2014 at 1:40 | history | tweeted | twitter.com/#!/StackProgrammer/status/438851166223749120 | ||
| Feb 27, 2014 at 0:54 | vote | accept | user3339333 | ||
| Feb 27, 2014 at 0:43 | review | First posts | |||
| Feb 27, 2014 at 2:21 | |||||
| Feb 27, 2014 at 0:39 | comment | added | Kai Qing | It helps to have a goal. If, for example, you wanted to make a game, you could download a framework or library and follow introductory tutorials. If something less complex, you can begin by searching for examples of these programs, deconstruct them and modify them to fit your needs or interests. | |
| Feb 27, 2014 at 0:35 | answer | added | Robert Harvey | timeline score: 45 | |
| Feb 27, 2014 at 0:33 | answer | added | Xelad1 | timeline score: 6 | |
| Feb 27, 2014 at 0:25 | history | asked | user3339333 | CC BY-SA 3.0 |