Hacker News new | ask | show | jobs
by davydm 582 days ago
1. seeing who originally wrote the file i'm working on, which can set up some expectations, eg i know a certain someone likely didn't test the code well, if at all, so i know that i'm going to spend time constraining the existing code with tests before i can even get into it properly 2. figuring out what i did today so i can fill in the absolutely pointless timesheet that i have to fill out every day, because we can't just assign hours to a trello card, no! we have to also blurb about it so someone else can gloss over it