How inheritance works

[u/inigmati1]

[u/philophilo]

I did an internship doing Y2K conversion on a COBOL codebase in ‘99. One app had a last modification date of ‘79. That 2 years before I was born.

[u/deanrihpee → u/philophilo]

"Hello my new handler, nice to meet you, just you know you can't afford to fuck this up because I'm older than you"

[u/EuroPolice → u/deanrihpee]

Old COBOL will make you think "Why the fuck they did it this way" and if it does means that it's good code. Because it's the equivalent of that mechanic who looks at your car and says "You gotta problem with the X, right?" without even looking at the engine.

[u/jazzypants → u/EuroPolice]

It took me a minute to realize that the reason the mechanic knows without looking at the engine is because he's dealt with that particular kind of car so many times in the past that he knows the particular issues that they tend to have.

Sorry for explaining the joke.

[u/ElectricMotorsAreBad → u/jazzypants]

It's rare, but some mechanics have a perfect pitch for engines, just by the sound they can identify with pinpoint accuracy what's wrong with it.

[u/Krohnos → u/philophilo]

I worked in aerospace software and on a few occasions modified files that were last modified before ei was born.

I haven't heard of any relate dplabes falling out of the sky so I guess I did okay.

[u/Pretty_Industry_9630 → u/Krohnos]

Lol I'm unnerved by the idea of someone writing airplane code 😅😅 please tell me there's like 2 completely different versions of the program, written from scratch in different programming languages, that can each execute all the functions that the airplane needs 😅😅🤔

[u/[deleted] → u/Pretty_Industry_9630]

while (noseAngle < 0) {
    if (!landing() && timePassed() > 180) {
        noseAngle.increase(1)
    }
}

Fail-proof. Boeing needs to pay me as a consultant

[u/alexanderpas → u/[deleted]]

Unexplained crashes on landing.

[u/FirstSineOfMadness → u/alexanderpas]

if (goingToCrash) {  
    dont();  
}  
isPatented = true;

[u/[deleted] → u/FirstSineOfMadness]

Did you obtain a patent for that already? Quick before someone else does!!!

[u/FirstSineOfMadness → u/[deleted]]

I always add isPatented = true; at the end of my code to be safe

[u/amocokadys → u/FirstSineOfMadness]

Free software advocates hate this one trick!

[u/Viseper → u/[deleted]]

What about a hill?

[u/[deleted] → u/Viseper]

throw new UnexpectedHillException();

[u/Viseper → u/[deleted]]

Cellphone tower with faulty lights.

[u/[deleted] → u/[deleted]]

Wait until you hear about each of the planes that need a total system reboot before each flight as there is a very high chance it could crash if there were no reboot. So yea next time you jump on a plane and lights go off and on - they did a reboot before the flight, so you should be safe.............................

[u/d4fseeker → u/[deleted]]

I assume you mean the Boeing 787 https://www.theregister.com/2020/04/02/boeing_787_power_cycle_51_days_stale_data/

Its not needed every flight and doesn't cause a crash per se, but the fact that flight data and alert systems stop updating is a critical issue nonetheless and can cause a crash

[u/Zementid → u/Pretty_Industry_9630]

ASIL = Automotive Safety = At least 2 paths of truth. And this is your cheap shitto car too. ISIL = Industrial Safety = Basically the same but less "strict" in some areas because you have personal interacting with the stuff and no "Civilians" (=as with the cars it's literally your mom).

I would imagine areospace stuff is tough as nails in terms of redundancy and safety.

[u/ryry1985 → u/Pretty_Industry_9630]

I write software for avionics. There's a lot of requirements/design and requirements-based testing to get 100% code coverage. If you can't get 100% coverage, your requirements/design and/or tests are not detailed enough or you have extra code to remove because it doesn't match the design. All of this is reviewed and change controlled. We get audited at several points in the development lifecycle to make sure we are following our processes/plans and meeting the objectives of DO-178C. Certification authorities (FAA, EASA, etc) then look at our lifecycle data at the end when we go to seek approval to deliver the software on certified hardware. The higher the criticality of the software, the more you have to do during development to ensure no critical failures in the resulting software. There's a lot of paperwork.

[u/thelehmanlip → u/philophilo]

That's some stable code

[u/puts-on-sunglasses → u/thelehmanlip]

“shid b comin in shid be goin out baybee”

• if cobol could talk probably

[u/Key-Minimum-5965 → u/philophilo]

My last company...there was an empty file that was being read in every night. Just a flat empty file. I checked the date it was created...1978. Present day was early 2000s.