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

The article seems to have two messages: one that it's better to fully comprehend the problem before you start coding; the other that learning a powerful library will save you pages of code. Both well rehearsed truths of computer programming.

As for myself I often find that I have to fully explore the problem on my own terms before I can maturely optimize my source.



it's better to fully comprehend the problem before you start coding

Often the best way to understand a problem is to try to implement a solution.


That's a very true observation mhartl and I try to touch on it in my last sentence although it is enigmatically worded as I was trying to sneak a "Premature optimization is the root of all evil" reference into it. Alas not all wordplay is destined for upmods!


Would it be advisable to try to implement a solution on a chalkboard first? Mathematical notation and diagrams can be amazingly succinct.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

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

Search: