3 ms·

Does this second person live in the cockpit 24/7? This guy got in an unoccupied plane.

by hueving 8y ago

bobthepanda 8y ago
Do programmers just ship code to production without a second person to review code?
- stephengillie 8y ago
  Are all peer reviews/pull requests equal? A lot depends on the size, maturity, and customers of the group shipping code. One-person side/hobby projects wouldn't have a 2nd person to review the code. A previous employer initially had a "Deploy to Production" script that ran every 60 seconds, copying the Development folder to the Production folder - to make easier their testing in Prod. But large publicly-held companies with more customers will often have auditors that require better controls over dev/test/UAT/Prod, and between developers and operators. Separation of Duties is essential to protecting Business Operations from disruptions caused by a single individual. There should be some sort of lockout that requires 2 humans to put an airplane in the air - at least for major airlines, and could be mandated by law. This could range from a 2-key fuel shutoff for the engines, to different keys on the outer plane door and the inner cockpit door, to mandatory wheel boots on idle airplanes. And part of this would be a very good key management system, possibly with many physical keys managed by an airport or airline "key desk" - or maybe through electronic key-cards, RFID chips or key-fobs, or a smartphone app.
  - sandworm101 8y ago
    Such lockout systems are a safety risk themselves should they err and limit functionality in the air.
  - paulie_a 8y ago
    And even at Large publicly held companies the guy trying to implement a fix that matters is going to over ride those controls and get it out, the auditor might complain later but who cares. I know some devs that will do it at midnight while smoking weed at Fortune 50 companies. Sometimes you ignore the normal process and get it done and basically work around any locks/restrictions
- jandrese 8y ago
  You probably don't want to hear the answer to this one.
- crankylinuxuser 8y ago
  Yes. My previous job did precisely that. We were responsible for probably 80% of the academic internet. And those Mloc perl5 programs were terrifying to work with.
- nickserv 8y ago
  What do you mean "ship" to production? Isn't the normal thing to do to modify the code directly on the production server using FileZilla on port 21?
- paulie_a 8y ago
  All the fucking time. While there is an attempt to avoid and standard deployment procedures hopefully. Sometimes in an emergency you just get shit done and fixed for a client. I heard a mantra regarding this from a pretty big consultant at a major company: be bold be brave, deploy I guarantee your financial information has passed through that product.

Does this second person live in the cockpit 24/7? This guy got in an unoccupied plane.

bobthepanda 8y ago

Do programmers just ship code to production without a second person to review code?

stephengillie 8y ago
Are all peer reviews/pull requests equal? A lot depends on the size, maturity, and customers of the group shipping code. One-person side/hobby projects wouldn't have a 2nd person to review the code. A previous employer initially had a "Deploy to Production" script that ran every 60 seconds, copying the Development folder to the Production folder - to make easier their testing in Prod. But large publicly-held companies with more customers will often have auditors that require better controls over dev/test/UAT/Prod, and between developers and operators. Separation of Duties is essential to protecting Business Operations from disruptions caused by a single individual. There should be some sort of lockout that requires 2 humans to put an airplane in the air - at least for major airlines, and could be mandated by law. This could range from a 2-key fuel shutoff for the engines, to different keys on the outer plane door and the inner cockpit door, to mandatory wheel boots on idle airplanes. And part of this would be a very good key management system, possibly with many physical keys managed by an airport or airline "key desk" - or maybe through electronic key-cards, RFID chips or key-fobs, or a smartphone app.
- sandworm101 8y ago
  Such lockout systems are a safety risk themselves should they err and limit functionality in the air.
- paulie_a 8y ago
  And even at Large publicly held companies the guy trying to implement a fix that matters is going to over ride those controls and get it out, the auditor might complain later but who cares. I know some devs that will do it at midnight while smoking weed at Fortune 50 companies. Sometimes you ignore the normal process and get it done and basically work around any locks/restrictions
jandrese 8y ago
You probably don't want to hear the answer to this one.
crankylinuxuser 8y ago
Yes. My previous job did precisely that. We were responsible for probably 80% of the academic internet. And those Mloc perl5 programs were terrifying to work with.
nickserv 8y ago
What do you mean "ship" to production? Isn't the normal thing to do to modify the code directly on the production server using FileZilla on port 21?
paulie_a 8y ago
All the fucking time. While there is an attempt to avoid and standard deployment procedures hopefully. Sometimes in an emergency you just get shit done and fixed for a client. I heard a mantra regarding this from a pretty big consultant at a major company: be bold be brave, deploy I guarantee your financial information has passed through that product.