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

You should probably scope and clarify your rule of thumb. For example, writing a function that renders readable error messages to a UI will be far more than 20 lines of code.



It’s an average. Novel problems: low SLOC/day. Common or “solved” (but not implemented) problems: high SLOC.

EDIT: “Autocorrect” got me.


So? That means it will take more than one day to write, by this metric.


If you have your list of possible errors, it really shouldn't take that long to write a `errorObj -> string` function.




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

Search: