Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I understand your point, but perhaps that would have simply been an opportunity to refine your approach to code design. If such a situation leads to excessive deliberation and overgeneralisation, your code base must be riddled with unnecessary overthinking and overgeneralisation.


Or maybe it was just a long, sequential algorithm where breaking it up wouldn't have been an improvement.


I have been programming for more than 30 years. Except for code generated explicitly to be only consumed by machine, I've never come across a function consisting of 2000 lines of code that should not have been broken up. Something is wrong there, and if you show me the code, I'll tell you what's wrong with it.


Glad you can see that without even looking at the code.


Some things you don't have to see to know whats going on. Function with 2000 lines of code? Have fun rationalising this.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: