FoxPro was a database...not a programming language....

I started out learning Basic (never finished) then tried Pascal (never finished learning this one either) and then got my first job in IT back in '91 and rarely did any actual programming after that except reuse what was already done by others....modified for what I was working on.....why re-invent the wheel....

I was actually taught Algol when I was a physics research student at Bristol, and even used it a bit.

Basic, then it was Fortran.

1401 Autocode

Likewise

Assembly on an Interdata model 70. The CPU architecture was a loose clone of the IBM 360. Once I caught the computer bug I learned Benton Harbor BASIC on the Heathkit H8

Assembly IBM SOAP 1958

RT-11

Unless you count the machine code I entered from the front panel of a PDP 11/35.

Assembler on an NCR-315

1972:
FORTRAN IV using optical-mark (pencil) cards on and IBM 11/30 mainframe (room-sized). I made a block-line printer 'howl' (and that startled the computer operator) using just one short-and-sweet FORMAT statement with a 3-line program.

Assembly on a Univac III

It was BASIC on a VIC 20,(5K of memory) then GWBASIC on a TRS 80 II with an expansion 32K, I remember finding out about GOSUB routines, and stacking them up at the beginning to speed things up, happy days; then Turbo Pascal, currently Python 3, but very rarely these days.

Back in those days (mid 70's),the computer found it's way into my business and I became a "User" only, with word processing and later on CAD, although that has changed a little since my switch away from MS Windows to Ubunutu a few years back.

I'm 83 and find sitting in front of a keyboard and monitor still generates a thrill, my word processing is now done with Libre Office and QCAD plus Solvespace covers my CAD needs, but I leave the clever stuff to others.

Incidentally I still have the TRS, now a home for aged spiders, and a TRS COCO 2 if anyone remembers them.

Cheers,

Hal.

PL/1 although I was also doing Algol60 and Watfor at about the same time. I recently found Iron-Spring PL/1 (beta) on Linux so it's Deja Vu all over again. I had almost forgotten how pleasant a language designed by linguists (Hursley) could be for coding. It is wonderful to once again use a pointer as a locator without having to specify the type of the object located. It makes implementing a container class duck soup without all that Templates and spewing more code for each object you might want to put in some container. Despite the fact that PL/1 had no explicit object hooks, I wrote OOP style code in PL/1 and it was fast and clean. Anyone know if there exists a language today which realizes the value of Areas/Offsets for relocatable workspaces for objects ? Realize that an entire area can be relocated in ram or ramLocation1>disk>ramLocation2 without any address translation. What a breeze for buffer pooling, checkpoint/restart, spill, and similar reasons ! And count/flow, glorious on-conditions, data-directed I/O, and VSAM, and ... There you go. You went and got me started about all these shiny new languages getting worse over the decades.
_____________
thewildotter

I first programmed in assembler on a Scientific Data Systems (later XDS Zerox Data Systems) often doing hand assembly. It had no stack only ONE link register for ONE subroutine return address pointer. 64K 16 bit memory MAX usually had to manage with 4K and an ASR 33 teletype making a heck of a noise. We used shoehorns to cram in as much as we could. Really out of date by what is done today.