Re:United Airlines Bug Bounty: An experience in reporting a ...
by jfoutz on Sunday November 22, 2015 @08:15PM
(#10612313)
yes, absolutely. 2 freaked me out the most. I managed to get enterprise github installed, taught people how to use it, set up the client on their computers, pointed them at tutorials, and pestered them regularly. For all that effort, over the 6 months the adoption rate was pretty much just 1 developer in one department - me.
It's just so damn hard to get people to change.
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?
1. They don't have a formal QA process or an independent QA team.
2. They don't have source control (or it's very rudimentary, like storing ZIP backups of source code on a network server).
3. Their issue tracking system is an excel sheet on a shared drive.
4. 75%+ of the code was written by someone not currently working for the company. 10%+ of the code is considered "untouchable" because it works and nobody remaining knows how it works.
5. Compiling the final executable takes more than 1 manual step, resulting in screens full of compiler warnings.
6. Management is resistant to any effort to fix any of the above because software is a COST and not an investment.
(EDITed because I can't seem to count to 6)