3 ms·

I don't know Go, but your example looks absolutely beautiful. On the other hand, I'm one of those "smaller than that" people :) I mean, I am ashamed that I lef

I don't know Go, but your example looks absolutely beautiful. On the other hand, I'm one of those "smaller than that" people :) I mean, I am ashamed that I left the time-to-string function in [1] too long. It could definitely be split up (and I find value in that, I just haven't had time / a reason to revisit that code). [1] https://github.com/mdpopescu/public/blob/master/SocialNetwork/SocialNetwork.Library/Services/TimeFormatter.cs https://github.com/mdpopescu/public/blob/master/SocialNetwor...

Denzel 9y ago
Thank you, I really appreciate that. I understand exactly how I feel. I think your way of attacking it is the right way -- pragmatism. You realize it can be improved/split but (1) you haven't had time, (2) there's been no reason to revisit the code, and (3) it's serving its purpose. That makes sense to me. It takes time. Time and many passes to refactor code. The idea being that as a developer becomes more experienced: the amount of time and the number of passes should begin to decrease. At least that's the idea.