Hacker News new | ask | show | jobs
by sdesol 19 days ago
I think that would be implied by "how did you arrive at the code". I think the conversation will revove around how did you "guide" things.
1 comments

Not really, I don't think I've ever care about the how. I want to mostly know the trigger of a change (a bug, possible feature, or just tidying) and what are the impacts if that changes is included in the codebase. That is often just a paragraph or two.

The workflow is mostly worthless, unless it can generalize and evolve into a process. And that is more worthy of a blog post or a presentation.