Timeline for Does programming in general become easier to read, write and understand as you gain experience?
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2018 at 20:41 | history | edited | Robert Harvey | CC BY-SA 4.0 | deleted 1 character in body |
| S Aug 9, 2018 at 20:16 | history | suggested | H.Dbouk | CC BY-SA 4.0 | Some spelling mistakes here and there |
| Aug 8, 2018 at 20:23 | review | Suggested edits | |||
| S Aug 9, 2018 at 20:16 | |||||
| Mar 3, 2014 at 3:17 | comment | added | miguel.martin | Programming in general gets easier. You gradually understand the language and it's syntax, much like English. Your short answer should be "Yes". Of course there are certain aspects that you wont have a clue on how to implement/design, much like learning new words in the English language (e.g. applying them appropriately) or learning new concepts in mathematics. | |
| Feb 23, 2012 at 18:05 | comment | added | Mark Freedman | Excellent answer. Really describes the ongoing growing process in this field. Not everyone takes the same route, but this is a solid example. It also shows how interesting this field can remain, as you peel back the onion. | |
| Feb 20, 2012 at 8:51 | comment | added | daGrevis | "It never gets easier, you just go faster." /Greg LeMond/ | |
| Feb 19, 2012 at 22:01 | comment | added | Gangnus | I think, it is a good post. Of course, some details are adapted to the level of the qustioner. But they should have ben adapted. | |
| Feb 19, 2012 at 16:01 | comment | added | Ben Voigt | If you "need your powerful IDE", you're a code monkey and not a programmer at all, let alone a developer or software engineer. | |
| Feb 19, 2012 at 8:43 | vote | accept | Bugster | ||
| Feb 19, 2012 at 8:43 | comment | added | Bugster | Amazing answer and thanks to everyone else that answered, this helps alot. +1 to all great answers but this one sums it up. | |
| Feb 19, 2012 at 1:28 | comment | added | Arseni Mourzenko | @Ben Brocka: I edited the answer to be more clear on both points you mentioned. Thanks for your comments. | |
| Feb 19, 2012 at 1:26 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 | Reformulated two points according to the comments by Ben Brocka. |
| Feb 19, 2012 at 0:53 | comment | added | Zelda | I'll also note that "months gathering requirements" with no development is only going to happen in basically an idealized Waterfall model. If you're not iterating you're killing yourself and the project. | |
| Feb 19, 2012 at 0:51 | comment | added | Zelda | I certainly hope the "functional programming" bit is just an example of "use the right tool for the job" rather than implying that functional programming is actually better for general use. | |
| Feb 19, 2012 at 0:11 | comment | added | jfs | "functional programming is a much better alternative" is debatable. | |
| Feb 19, 2012 at 0:04 | comment | added | jfs | Walking on water and developing software from a specification are easy if both are frozen (it shows that "You don't start writing code. You spend months gathering requirements" is a bit unrealistic) | |
| Feb 18, 2012 at 20:35 | history | answered | Arseni Mourzenko | CC BY-SA 3.0 |