batels

6 месяцев назадdiscuss

Makes sense.

Keeping docs close to the code has worked well in my experience too.

6 месяцев назадdiscuss

I’ve seen similar setups work well in small teams, especially when people actively look out for each other.

6 месяцев назадdiscuss

This works well as a personal system.

The cases I’ve been thinking about are team-level recurring tasks, where execution and ownership need to be visible beyond a single person.

batels

6 месяцев назадdiscuss

That makes sense.

Did it still feel lightweight enough for very small, administrative routine tasks?

batels

6 месяцев назадdiscuss

That makes sense.

I’ve mostly been thinking about lower visibility recurring tasks that don’t always make it onto a board.

batels

6 месяцев назадdiscuss

Agreed, cron + email is very effective.

The only thing I’ve seen missing sometimes is an explicit acknowledgement, so later you don’t have to rely on memory.

batels

6 месяцев назадdiscuss

I agree this works well for one-off or high-signal tasks.

Where I’ve personally seen friction is with recurring, low-visibility work.

Things people fully intend to do, but that don’t produce immediate feedback.

batels

6 месяцев назадdiscuss

Strongly agree. Automation is the ideal outcome whenever possible.

What I keep running into is the gray area between "can’t be automated yet" and "shouldn’t be automated". Things like reviews, checks, approvals, or manual verifications.

The notification fatigue point is especially real. If everything notifies, nothing gets attention.

Do you usually treat non-automatable tasks as exceptions, or do you still rely on routines / trust for those?

Submissions

Show HN: Projects Calendar for GitHub – A stateless iCal feed for your projects

What I learned asking small teams how they handle recurring work

Ask HN: How do small teams make sure recurring tasks don't slip?

Show HN: DonePing – Simple Recurring Tasks

Show HN: Latameo – exploring what it's like to live in Latin American cities

comments