Yeah, I did Fortran in college - using punch cards (c.1977).
I still have a few boxes of punch cards and some 9-track tape reels in the basement. Or attic. I forget.
I played around with QuickBASIC quite a bit in the 90s, mostly writing astronomy programs.
By then I was writing my astronomy programs in C. My original astronomy programs were written in Fortran. You know, 300-element harmonic equations -- the stuff Fortran is really good at. So after hours you could go in and mount up your tape and say something like
//EPH42 JOB (JPW1138) 'JAY EPHEM RUN' CLASS=A, MSGCLASS=0, MSGLEVEL=(,1)
// EXEC PROC=FORTCLG
//FORT.SYSIN DD DNSAME=JEPHEM, UNIT=2401, VOLUME=SER=JPW04,
// DISP=(OLD,KEEP)
//GO.SYSIN DD *
+420320.00 -0924513.21 19790822 230000-06
/*The first five cards you'd have in your desk with rubber band around them because you're going to use them a jillion times. But you had to go over to the 029 and punch the data card, the one after GO.SYSIN. You'd be a steely-eyed missile man if you could decipher what the data format is and what it means.
Then you dropped the cards in the hopper "face-down, nine-edge forward," or sometimes "face-down, top edge to the back." Those were our mantras. You have to add the last card, a pre-punched stack of which was always available on the reader. (You were supposed to put them back after your job was entered, the IBM equivalent of "take a penny, leave a penny.")
Then you push START. The reader ingested your cards and gave them back in the tray to the side. Or, if they were too well used, the reader would eat one and jam, forcing you to take the reader apart and fish out the lacy corpse of a some DD card that took you 17 ABENDed jobs to get right and which you now need to repunch.
Then if everything went right up to this point, the tape would spin wildly one direction, then the other, stop, and cautiously inch its way forward for a couple seconds. Then silence for several seconds. Well, "silence" in a machine room means no sound other than enough fans blasting to deafen a bomber pilot. The line printer would clatter to life and on your wide fanfold sheet, neatly lined up on green and white yardlines, would be a row for each planetary body -- its rise/set times and azimuths, zenith azimuths, phase, right ascension / declination and altitude and azimuth angles for the input.
I laboriously translated all those 300-element harmonic equations into C at one point. That was a lot nicer, since running the program was so much more convenient. And the computer was faster.
I eventually put a Sunview window around it so you could see an actual
display of the night sky, and an overhead model of the solar system with the planets where they were in their actual geometrically-correct orbits (mapped onto the ecliptic). That's how I discovered there was a bug somewhere in Saturn, because it retrograded for a bit as you spun time fast enough to watch the planets orbit. Not as if I really want to proofread hundreds of floating-point coefficients to figure out which one is wrong.
And I sort of left it there and went on to other things.
Today I can usually accomplish what I need to using Excel.
Which is probably quite a lot, considering most people around me end up using it just to format a table of static data.