Hacker News new | past | comments | ask | show | jobs | submit login

I think the problem is an unwillingness(don't want to insult a co worker's code) or inability to form real criticism. If you can't pull the code base apart and say "this worked well" and "this part made too many assumptions to ever work right" or "is overly complicated for the task at hand" then you haven't taken enough time to understand the code in front of you.

This hits at one of my least favorite memes around here. The whole all the code I wrote six month ago is shit, and I will think that about the code I am writing now in six months. Yep, if you haven't developed the skills to determine what is good or bad about the code you wrote six months ago then A) It probably was middling code B) You aren't getting any better because you are unwilling to honestly critique your own work to look for areas that need improvement.

Applications are open for YC Winter 2022

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