It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
That part's on you. Unit tests will help you sometimes, other times you'll have to trace the flow of execution yourself (or write tests), still other times grep is your best friend. But every situation is different and the only way to learn is by doing.
Thanks! From there how do I find the file that the issue is in?
That part's on you. Unit tests will help you sometimes, other times you'll have to trace the flow of execution yourself (or write tests), still other times grep is your best friend. But every situation is different and the only way to learn is by doing.
More on tests as documentation:
Avoid the Code Crawl by Reading Tests
Brandon Martinez
Without docs or good tests, it's going to be a matter of search, trial, and error, as Dian is saying.