Programming

17668 readers

142 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

Decision logs (vitonsky.net)

submitted 9 months ago by vitonsky to c/programming

8 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] vitonsky 1 points 9 months ago (1 children)

Sure, decision logs is just a step to fix a problems with decision making. Logs highlight a problems in decision making process and let you analyze a problems in your team. You still need an strong architect who may say "hey team, why your arguments so weak? it looks you are low skill engineers. make arguments more objective, or you will be fired" and then really fire weak engineers in team.

[–] [email protected] 2 points 9 months ago

Logs highlight a problems in decision making process and let you analyze a problems in your team.

Yeah good point.

In that process-heavy project I joined, I could quickly see the problems; about 2 or 3 days. That meant when I was submitting code or reviewing the backlog I knew what kind of challenges I could make, and what would just be a waste of time. In others, it could take way longer - months! - to learn how the team actually deals with challenges and design.