Among your lessons learned as a productive developer, which are the best?

Re:Among your lessons learned as a productive developer, whi... by whytheplatypus on Tuesday July 23, 2019 @05:22PM (#20510339)

"write clearly -- don't sacrifice clarity for 'efficiency'"

"make it clear before you make it faster"

"make it right before you make it faster"

"keep it simple to make it faster"

From "The Elements of Programming Style" by Kernighan and Plauger

Other than that maybe that naming is one of the hardest and most important things to do.

[ Parent | on HN ]

Re:Among your lessons learned as a productive developer, whi... by notomorrow on Tuesday July 23, 2019 @06:13PM (#20510698)

Great tips. Thanks. Do you have a suggested reading list?

[ Parent | on HN ]

Re:Among your lessons learned as a productive developer, whi... by whytheplatypus on Wednesday July 24, 2019 @08:44AM (#20514622)

I've been enjoying "The Elements of Programming Style" by Kernighan and Plauger. Don't get put off by the references to Fortran, what they say applies to any language.

"Structure and Interpretation of Computer Programs" by Harold Abelson, Gerald Jay Sussman, Julie Sussman is another standard.

Martin Fowler and Robert C. Martin are both prolific.

Coding takes practice, so once you've got some ideas on what you want you want your coding to look like add them to your practice and see how it goes.

[ Parent | on HN ]