Connect
← Return to Not Good News after prostate biospy when MRI didn't look too bad
Discussion
Not Good News after prostate biospy when MRI didn't look too bad
Prostate Cancer | Last Active: 16 hours ago | Replies (290)Comment receiving replies
@jeffmarc
Wow, I did assembly programmer also. Went to school wanting to learn COBOL, but they had a requirement that I first had to take Assembly and learn to read Hexadecimal and Binary. Didn't want to learn that, but really paid off later as most staff didn't know things down to that level which was really needed looking at core dumps. Mostly IBM ESA, but also did work on Univac, IBM System 3 15D, IBM Series 1 and even some Control Data Systems (CDC). Then had to also get into Micro Computers. Before I had to support them, I made fun of the PC staff, called them Micro Brains.
Replies to "@jeffmarc Wow, I did assembly programmer also. Went to school wanting to learn COBOL, but they..."
Connect
@diverjer
The only way to really debug cobol is to read the dump, go through the hex and figure out why the code went wrong. I had people come to me for help with that.
I worked with first generation second generation and third generation IBM Computers. First generation had vacuum Tubes, A drum that was like a small disc drive and punch cards. Sounds like you had a wide range of experience with different operating systems. When writing code is just how do you do that thing in this language?.
Learning all about prostate cancer was Like learning how to use computers. So many things. Just learning to understand reading a biopsy Going through clinical trials and analyzing the results. Gets really complex, just takes time.