Issue #354

tl;dr: Monday to Wednesday are high energy, productive days for James, but Thursday is an inflection point where he's tiring. James discusses how he's trying to rectify this: (1) Purposefully trying to work 10% slower. (2) Being stricter with notifications so there's less context switching. (3) Limiting checking messages to within working hours. (4) Deferring non-essential requests and tasks into the following week. (5) Pomodoro technique.

tl;dr: The process for permanently removing unreachable objects from a repository’s history has a history of causing problems within GitHub, especially in busy repositories or ones with lots of objects. In this post, we’ll talk about what those problems were, why we had them, the tools we built to address them, and some interesting ways we’ve built on top of them. 

tl;dr: "Sudoku is an example of a constraint problem. Most “solving sudoku” tutorials use either backtracking or constraint propagation. These same techniques apply to all constraint problems, and since such problems are so widespread, it doesn’t make sense to custom build an algorithm for every single one. Rather, we want general-purpose constraint solvers we can apply to arbitrary problems."