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 @02:33PM (#31706903)
I think the answer to all of this is 'it depends'.

Is there already a ticket and are you working to update the app? Then update the documentation. No ticket necessary.

Are you redoing the whole set of docs to make the steps for new engineers to create their stack? Then please lets have a ticket to define the scope and audience.

Trust me that I do understand that there are many orgs that have arbitrary hurdles in place, like who can create / prioritize a ticket. My experience is, if engineers are empowered / encouraged to create and prioritize their own tickets, then its not a hurdle at all.

Re:How big tech runs tech projects and the curious absence o... by astrostl on Saturday June 11, 2022 @03:13PM (#31707307)
> if engineers are empowered / encouraged to create and prioritize their own tickets, then its not a hurdle at all

Many people - now including me - are plainly telling you that it is a hurdle for them. No amount of reframing this is going to alter someone else's experience.

Re:How big tech runs tech projects and the curious absence o... by sanderjd on Saturday June 11, 2022 @05:21PM (#31708544)
You seem to keep trying to change the subject to "should there be tickets in general?", which nobody is saying there shouldn't. The topic is "should there be a ticket required for every change, which requires tickets for updating typos in internal documentation, because that requires a change and you propose that a ticket be required for every change. That is stupid, to require a ticket for that. These other examples are not stupid to use tickets to track them. But they aren't the subject of the thread.
Re:How big tech runs tech projects and the curious absence o... by ipaddr on Saturday June 11, 2022 @03:51PM (#31707670)
Skip the ticket completely and get out of the way