|
|
|
|
|
by corry
1913 days ago
|
|
I’d say it really depends on WHY you want feedback. And perhaps who you are / what the code is doing for you (fun side project to build your skills vs MVP of your new funded startup). If it’s just to improve your craft, I’d say there are lots of ways to learn without peer review. Studying other code based, open source, etc. But if you’re a founder building your first project, the quality of your code is like concern #999 in the list. As long as it works and the clients are happy, you have better problems to focus on (like how to grow users). Much of HN doesn’t want to hear that, but many (most?) $100m startups were stitched together with duct tape for the first n years. And you know what? It works out fine. You deal with the technical debt later as you need to. |
|