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

I think it's OK to not know the implementation details of code you aren't responsible for maintaining.



To an extent. You should still know the performance details. As an example, a project a colleague was working on was generating Excel files as a report format. He didn't need to know why the library couldn't handle anything over a (forgot the exact number) 32MB, but he needed to know that detail. It failed to execute on some data files as a result, something that could have been checked and worked around (temporary fix: multiple Excel files; permanent fix: better report format).




Consider applying for YC's W25 batch! Applications are open till Nov 12.

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

Search: