A Recipe for Designing Your Work Week as a Software Engineer
summary
Create a spreadsheet table with column headers for each responsibility (reporting, telemetry, meetings, learning, mentoring, buffer), assign concrete hours or percentages that sum to your weekly hours, then convert those hours into 25-minute pomodoros and allocate counts per column. Track time by marking tasks after each pomodoro so you know midweek—by Wednesday—if a stream has zero progress and needs reallocation. Use this simple plan and daily logging to correct focus, not to enforce rigid rules.
AI-written summary · about
related talks
47mUnleashing Your Super-dev-powers
51m"Time Management for Developers"
41mHabits of an effective programmer
45mGrowing Engineers with Weekly Investment Time
58mOptimizing the Programmer: Get More Done Faster
55mZen-Driven Development - Protect Your Sanity
59mHacking your work life __ balance to take over the world
01h 03mThe Effective Developer - Work Smarter, Not Harder.