"We've read your code"

Re:"We've read your code" by swanson on Monday September 20, 2010 @10:37AM (#1708950)

I actually keep some crusty old code on github intentionally. Since github sorts your profile page based on last commit, it shows up near the bottom of the list anyways. By having gross old code, I can show how much I have improved and advanced myself.

Looking at code that I wrote a few years ago (like when I was first learning OO and Python) and comparing it to more recent projects is like night and day. It helps me to not feel so inferior on those days when I read too much HN and get too hard on myself -- and I would think that an employer would be interested in seeing growth and improvement.

[ Parent | on HN ]

Re:"We've read your code" by InclinedPlane on Monday September 20, 2010 @02:12PM (#1709882)

What would you say are the most important differences between your bad, old code and the way you code currently?

[ Parent | on HN ]

Re:"We've read your code" by swanson on Monday September 20, 2010 @02:35PM (#1709975)

Following conventions/best-practices. Not duplicating code unnecessarily. Using features of the language to my advantage instead of forcing the language to fit my program structure.

And also just an overall improvement in the quality of the code - less room for bugs, less 'hacky fixes', easier to maintain/extend/modify

[ Parent | on HN ]