[mrmincent]

I like the first half of describing the issues faced during the week - it’s something I’ve been thinking of doing for my team, and the format is easy to digest.

I really don’t understand the point of the second half in publicly disclosing what each individual has done though. I hate the idea that team members would feel like they might have to rush stuff out so they look as productive as someone else, or that they’d feel not as good as others.

[tptacek]

This is a cultural thing at Fly.io, which is on more prominent display in the "Fresh Produce" section of our community site. It's been tricky to get infra work out in front of our users in the same way platform developers have been able to, which is messed up, because infra people here do a huge amount of the work.

Rather than asking infra developers to do somersaults to make their work fit the mold for the "Fresh Produce" topic, we're just going to do some of that writing for them. We're going to keep doing this, and I expect it's going to make more sense as the weeks move on.

We certainly didn't submit this to HN; I think it looks super weird here, especially with just the first week of content on it.

[yla92]

I submitted it. I just stumbled on it while checking out the openings and about LiteFS Cloud today.

I personally liked the way it's done (very transparent and interesting at the same time) and thought HN crowd would be interested in these too ! :D

[tptacek]

How dare you!

[usrme]

I like the spirit of the second half to demonstrate what the team is up to, but I too wondered about potentional one-upsmanship problems. I'll definitely start following this to learn more though.

[iamkonstantin]

It reads more like a retrospective for each team member?

It wasn’t clear if it’s opt-in to have your status update posted publicly but I can imagine (and hope) it’s okay not to partake.

[aranw]

For you the second half probably doesn't make much sense but if these documents are also shared internally it would be really useful for others at the company to see what the team and individuals have been up too

[hackernewds]

that seems micromanage-y and fraught with lack of psychological safety

[aranw]

But what if they are just used as internal updates? Surely you share updates with what you've done in some way?