Re:United Airlines Bug Bounty: An experience in reporting a ...
by ryandrake on Sunday November 22, 2015 @08:26PM
(#10612343)
The mentality is: typing in code = assembling the widget, while setting up source control and an issue tracker = decorating the assembly line.
Re:United Airlines Bug Bounty: An experience in reporting a ...
by kbenson on Sunday November 22, 2015 @08:22PM
(#10612331)
Yes. Any change from the norm can be pointed to add a reason for failure/delay/cost overrun. There needs to be management buy-in and possibly even requirements for projects to reverse this inertia.
Which is why there needs to be pressure on management.
Re:United Airlines Bug Bounty: An experience in reporting a ...
by bnj on Monday November 23, 2015 @12:30AM
(#10613021)
I'm in the position of trying to push towards changes just like these- introducing better issue management, team communication. Anyone aware of useful resources on rolling out institutional changes like that?
It's just so damn hard to get people to change.