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

I didn't see any mention of in a quick look through the linked website, but the book "The Pragmatic Programmer" is one of the best resources you'll find for making the most out of text-based tools. PP goes a little beyond that, too, it's not the book's sole focus, but it's a major one, and the book is a classic: https://www.amazon.com/Pragmatic-Programmer-journey-mastery-...





I agree, but I found some of the relevant practices really hard to adopt. For example, how do you setup your tooling to put documentation in one place so it can be used for a wide variety of purposes, like code comments and relevant customer docs? Is that realistic from both the dev and user-facing perspectives?




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

Search: