https://evalcode.com/handbook/Recent content in Dev Handbook on eval ( code )Hugo -- gohugo.ioenCopy, _right?_ :thinking_face:. All thoughts and opinions are my own. They do not represent my employer.https://evalcode.com/handbook/story/Mon, 01 Jan 0001 00:00:00 +0000https://evalcode.com/handbook/story/A relatable analogy that frames the rest of the handbook: expectations, estimation, negotiation, and what ‘done’ really means.https://evalcode.com/handbook/going-remote/Mon, 01 Jan 0001 00:00:00 +0000https://evalcode.com/handbook/going-remote/Office habits break when you go remote. Here’s what to replace them with and why every other practice in this handbook depends on it.https://evalcode.com/handbook/scoping/Mon, 01 Jan 0001 00:00:00 +0000https://evalcode.com/handbook/scoping/How to break a problem into features that are small enough to deliver, clear enough to estimate, and valuable enough to justify the work.https://evalcode.com/handbook/daily-routine/Mon, 01 Jan 0001 00:00:00 +0000https://evalcode.com/handbook/daily-routine/The project lead’s daily checklist for making sure the board reflects reality and nothing is quietly falling apart.https://evalcode.com/handbook/project-board/Mon, 01 Jan 0001 00:00:00 +0000https://evalcode.com/handbook/project-board/The board should answer ‘what are you working on?’ in 30 seconds. Here’s how to set it up and keep it honest.