both are improbable....
I first learned to program computers in the 70's by programming our Fire Control Computers on the submarine I was stationed on... you know, the ones controlling the 224 40-kiloton warheads on 16 ballistic missiles... never did get them to launch! However, they were 24 bit and laid out in octal (they hadn't invented hex yet), with the full panel of flashing lights representing the various registers (think Lost In Space)... anyway, you could clear the register with a clear button, and then set each bit with a set button under each bit light... you had to set up the instruction (STA/Q- store data in A at address in Q register), set up the data, and set up the address. The first thing to do was write a small program that did the STA/Q, incremented the Q for the next address, and then stopped so you could add the next data word to the A register. Once you got that small (I think I remember it was only 7 instructions) program done, it got easier. The goal was to drive the printer, as my LPO (leading petty officer) had been in the Fleet Ballistic Missile program since its inception, and could tell missile test pass/fail just by the sound of the printout. So I programmed it to so when he came into Fire Control in the morning, pre coffee, and saw the DCC not normal light on (Digital Control Computer), you enter 00 to get the computer to normalize or printout the reason it can't. When he heard the printer printing, his eyes got big and he woke right up, as he'd never heard that print pattern before. When he read the message, "FVCK YOU SCHNEIDER, I'M ON STRIKE" (there was not one U on the whole printer platum), he chased me off the sub!!! Of course, we were in port and not covering targets, or I'd never been allowed to take the computer offline... anway, it took me a whole month just to format that one print line data and program it in to the computer, so the month guess of programming a whole 64K bytes is at the very best, AGGRESSIVE...