News for hackers. Stuff that matters.
Re:How big tech runs tech projects and the curious absence o... by mr-ron on Saturday June 11, 2022 @01:14PM (#31706118)
It can add value if done right. Just as you typically want to make a design doc / rfc before working on a project, you often want to describe what you are doing before you do it.

This can protect the engineer / team against scope creep, as well as determine the context of why work was done when you may need to understand more context (in the case of a bug for example).

Also it increases accountability and transparency. It is common that teams want to know what other engineers are working on and why.

Re:How big tech runs tech projects and the curious absence o... by carlisle_ on Saturday June 11, 2022 @01:28PM (#31706257)
We’re still talking about updating documentation right?
Re:How big tech runs tech projects and the curious absence o... by azemetre on Saturday June 11, 2022 @02:05PM (#31706618)
I'm explicitly referring to internal docs for the engineers that no one outside the team sees or cares (unless they want an example of docs). They're mostly markdown files or adding annotations to various code. I still think it's inane and seeing all the justification for "believe in the process" it's no wonder how little truly gets done in the name of agile/scrum/control.
Re:How big tech runs tech projects and the curious absence o... by mr-ron on Saturday June 11, 2022 @01:31PM (#31706287)
I think we started there but have extended into a different discussion as to 'why is jira important to engineering teams'.
Re:How big tech runs tech projects and the curious absence o... by carlisle_ on Saturday June 11, 2022 @01:58PM (#31706530)
I think you made that leap, but I was responding to the specific example. I don’t think anybody is contesting the use of tickets in engineering, but I’ll certainly oppose the idea that Jira is important.