For me, I read every programming style book that interested me. Then I had to parse fact from fiction. So after a few years I Had a pretty good idea for what patterns were right.
Then through just one rule, I gained the most. The Single Responsibility Pattern along with refactoring tools did the trick.
Where did I wind up? The pattern that emerged was that of Functional programming. Lots of small functions that do only one thing.
How long did it take me? 20 years. How long have I been a Functional programmer? 10 years.
Thanks for the input John! I'm definitely seeing myself following a similar pattern as far as the smaller functions go.
Improves legibility and ease of reading so much just having 10 lines of code to read instead of 100. Combine small functions with descriptive method names and really on a winner.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For me, I read every programming style book that interested me. Then I had to parse fact from fiction. So after a few years I Had a pretty good idea for what patterns were right.
Then through just one rule, I gained the most. The Single Responsibility Pattern along with refactoring tools did the trick.
Where did I wind up? The pattern that emerged was that of Functional programming. Lots of small functions that do only one thing.
How long did it take me? 20 years. How long have I been a Functional programmer? 10 years.
Is it the right way to go? Absolutely.
Thanks for the input John! I'm definitely seeing myself following a similar pattern as far as the smaller functions go.
Improves legibility and ease of reading so much just having 10 lines of code to read instead of 100. Combine small functions with descriptive method names and really on a winner.