batels

3 ms·

1.
Show HN: Projects Calendar for GitHub – A stateless iCal feed for your projects
2 points by batels 6mo ago|0 comments
2.
What I learned asking small teams how they handle recurring work
1 points by batels 9mo ago|0 comments
3.
by batels 9mo ago
Makes sense. Keeping docs close to the code has worked well in my experience too.
4.
by batels 9mo ago
I’ve seen similar setups work well in small teams, especially when people actively look out for each other.
5.
by batels 9mo ago
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.
6.
by batels 9mo ago
That makes sense. Did it still feel lightweight enough for very small, administrative routine tasks?
7.
by batels 9mo ago
That makes sense. I’ve mostly been thinking about lower visibility recurring tasks that don’t always make it onto a board.
8.
by batels 9mo ago
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.
9.
by batels 9mo ago
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.
10.
by batels 9mo ago
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 manua
11.
Ask HN: How do small teams make sure recurring tasks don't slip?
7 points by batels 9mo ago|17 comments
12.
Show HN: DonePing – Simple Recurring Tasks(doneping.com)
3 points by batels 9mo ago|0 comments
13.
Show HN: Latameo – exploring what it's like to live in Latin American cities(latameo.com)
2 points by batels 10mo ago|0 comments