I loved that Turbo.com and COM files 30 years ago!
later I started to use Turbo Pascal 5.5 with OO support and a good IDE.
And of course, there was Peter Norton's Guide to the IBM PC. The bible, back then.
FWIW I have had all of these at every place I've worked, including my current job. Places like that are out there. If you're unhappy with your current job, there's never been a better time to move.
And COBOL. Vast, vast plurality of the business economy ran on COBOL. We also had mainframe assembler for when speed was required, but COBOL had the advantage of portability to both mainframe and minicomputer. Anything fast on the mini was written in C.
When I started we had a PC to use for general office tasks ( documents, e-mails and such ) and a 3270 or 5250 green-screen terminal for actual work. The desks groaned under the weight and the heat was ferocious. Overhead lockers were jam-packed with code printouts on greenbar and hundreds of useful documents. "Yeah I have that in here somewhere" and Bob would start to burrow into stacks of pages on his desk.
Cubicle walls were covered with faded photocopies of precious application flowcharts and data file definitions.
Updates to insurance regulations would arrive in the post and we were expected to take ownership and get them implemented prior to compliance dates. There was no agile, no user stories, no QA teams, no 360 reviews. Just code, test, release.
You knew who the gurus were because they kept a spare chair in their cubicles for the comfort of visitors.
Good times.
Not really. Back in 1992 I was doing mostly C and second was perl, with shell scripting thrown in the edges.
Together with starting pair programming in 2004, that is the biggest improvement in my work life.
There were other profiling tools before then, but they were extremely pricey.
The awful part was C++. There were only two popular programming languages: C++ and Visual Basic. Debugging memory corruption due to stray pointers and so on in C++ was a nightmare. Then Java came out and everything became easy.
The great part was everyone had offices or at least cubicles. No "open floor plan" BS. There was no scrum or daily standup. Weekly status report was all that was needed. There was no way to work when you're not at work (no cell phone, no internet), so there was better work-life balance. Things are definitely much worse now in these regards.
All testing was done by QA engineers, so all developers had to do was write code. Code bases were smaller, and it was easier to learn all there is to learn because there was less to learn back then. You released product every 2.5 years, not twice a week as it is now.