Who it is for
A weekly planner for software engineers
Software engineers use Cutline to protect long coding blocks from meetings: work calendars from Google or Outlook show in the Grid as read-only blocks, focus time is planned in the gaps, and finished hours show where the week really went.
The engineer's problem
Coding needs long stretches of focus; most calendars are optimised for meetings. One 30-minute call in the middle of the afternoon turns a four-hour block into two blocks too short for hard problems. Paul Graham called this the maker's schedule.
A week that protects code
- Link your work calendar (Google or Outlook) so standups and reviews sit in your Grid.
- Plan deep work in the biggest gap each day, ideally the morning.
- Batch reviews after lunch, when energy dips.
- Track focus hours by category: deep coding, reviews, meetings.
See it laid out in the Software Engineer template.
What to measure
| Number | Why it matters |
|---|---|
| Deep coding hours per week | What ships tracks this |
| Meetings vs focus | When meetings pass focus, something gives |
| Longest uninterrupted block | Hard problems need long blocks |
Questions
Can my team see my Cutline blocks?
Only if you choose: add your Cutline week to your work calendar as a subscribed calendar, or share a Cutline calendar with them.
Does it work with Jira or GitHub?
Not directly. Put the ticket or pull request link in a block's notes so it is one click away.
None
Free forever for planning, XP, streaks and the Arena. Reserve your @name now.