|
Mine was in VB copying and pasting a tutorial for a whack a mole game, which I then replaced the mole with my friends head.
As for my computer skills, I think I did the head picture by cutting it out in paint, I knew a tiny bit about ms dos but literally nothing compared to the vast overwhelming knowledge I know now. Which will be literally nothing compared to the vast super overhwelming knowledge I'll know in five years etc etc.
Simon Lee Shugar (Software Developer)
www.simonshugar.co.uk
"If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
|
|
|
|
|
I had nearly forgotten: My Uni course was a "thin sandwich" - 6 months Uni, 6 months industry - and my first industrial training was this the Atlas Computer Division of the Rutherford Labs, a UK government research institution.
At the end of the training a report on my work was sent to the college: "Was determined to find out 'all about computers' and showed great ingenuity in doing so"
It wasn't a compliment.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Hey Griff, I was at Rutherford 83-87. Any overlap?
|
|
|
|
|
No - I was there the summer of '78, working for Rob Witty on Dimensional Flowcharting.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
I didn't get interested in programming until I had already been using computers for several years. And I didn't even start programming on a PC, I started on a TI-84+. When I started programming on a PC, it was z80 asm, for TI-84+. By the time I finally started writing programs for PCs, I was pretty computer literate, in a Windows-centric way.
|
|
|
|
|
.NOLIST
#define EQU .equ
#define equ .equ
#define END .end
#define end .end
#include "ti83plus.inc"
.LIST
.org 9D93h
.db $BB,$6D
xor a
ld (CURCOL),a
ld (CURROW),a
ld hl,text
B_CALL(_PutS)
ret
text:
.db "Hello, Harold!",0
.end
end
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
I found something very strikingly similar on wikibooks about TI83 Assembly
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
|
|
|
|
|
Thats probably where I stole it from - but I made it more efficient: the original used "ld a,0" which is one M state and 3 T states slower, and uses a whole extra byte in memory!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
So, you're a TASM user? That's getting quite rare, Brass and SPASM are so much better that almost everyone switched.
|
|
|
|
|
No - I haven't touched Z80 in years - and most of mine was IAR Z80 cross assembler/C compiler (Gawd damn it's rotten, black heart, may it rot in silicon Hades)
I stole that because I needed a Z80 environment you would be familiar with: my code was all home brewed on custom hardware and probably wouldn't have made a whole lot of sense to most people:
disp equ 4000h
#ORG 8000h
text: defs "Hello Harold!"
defb 0
textl equ $-text
#ORG 0000h
INI:
ld de,disp
ld b, 30
LOOP:
push de
push bc
ld hl,text
ld bc,textl
ldir
pop bc
pop hl
ld de, 80
add hl, de
ex hl, de
djnz LOOP
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
A 80x30 textmode screen memory-mapped at 4000h? Makes enough sense, very different from a TI-84+ (and its highly annoying display) though obviously.
|
|
|
|
|
Yeah, with a separate attributes plane mapped at 0x5000 - so a massive hole in the memory preventing the EPROM being bigger than 16Kb... and no MMU in those days!
I loved the HD64180 when we started using that because of the 1Mb memory space and a built in MMU. Bliss!
And the SIO came in handy too.
I was still using that in some new equipment designs in 2000, in its 32MHz form (purely because of the legacy Z80 code base, I moved to Arm processors as quickly as I could)
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
I also loved the Z80 because it was easy to memorise all the opcodes. I progressed to RML380Z from a home brew 8080 machine which I had to program in hex. Those were the days.
I may not last forever but the mess I leave behind certainly will.
|
|
|
|
|
My first program was written when some company brought a box and some cards with holes in them into school and said they could have it if one of their kids could write a program for it. I hadn't even heard of the word computer back then. No idea even what language I wrote it in, the ultimate in cut and paste, if you can call it that with a hole punch!
|
|
|
|
|
I started off with a Timex Sinclair computer in 1980 or so with a black and white t.v. set as the display and a cassette drive as the "mass" storage
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
|
|
|
|
|
Not very.
Wrote my first program in Pascal on a Multics time-sharing system using punch cards (1980) before graduating to a VAX in 1981.
/ravi
|
|
|
|
|
Ravi,
I'll have you know that I worked on that CPU long before you accessed it via time-sharing. I worked for GE and brought these 645 CPUs up just after they had been manufactured. The CPUs didn't even run (typically) without swapping out several (discrete component) boards and correcting several wiring errors (no LSI in this era). My first real programming experience was to write a small (4 punch cards) program (manually punched using a keypunch in multi-punch mode) that could be booted and the program could be hardware single stepped through its execution and would check out the memory segmentation LRU logic to determine which segment descriptor to discard in order to load a new descriptor. This program was later used to debug a replacement LSI implementation of the discrete component logic circuts (trust me, the engineers first try was totally hosed).
I'll give you a "not very", and raise you a "really not very".
Dave.
|
|
|
|
|
Nice!
/ravi
|
|
|
|
|
d@nish wrote: I could not even start a computer
I still don't know how to start a PDP-11 (running RSTS/E), but I quickly learned how to crash one. (1983)
Then on my first few jobs I was a System Manager for some VAX and Alpha (and Stratus) systems, so I became proficient at that.
Today I work with a bunch of virtual Windows Servers on VMware and I wouldn't be able to start them myself.
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
I was in 5th grade and we used HP Educational Basic punch cards. Had no idea how they worked, some guy would come in with a card reader and a Teletype to remote to a main frame at the nearby college.
I do remember is that to get closer to the front of the line one could surreptitiously remove a card and replace it to a different location in the program stack of the kid in front of you. This way the card reader would reject the program stack prior to executing the program.
It was broke, so I fixed it.
|
|
|
|
|
That was in 1978 with a TRS-80 in a Radio Shack. I knew nothing, but that did not stop me from looking into the manual and trying things out.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript.
|
|
|
|
|
I was given a copy of an IBM FORTRAN reference manual in the late 1960s from one of my Boy Scout merit badge mentors and until my first programming class in college, I thought FORTRAN was a IBM computer model...found out quickly in class that it was a computer language
Steve
_________________
I C(++) therefore I am
|
|
|
|
|
I was playing around with flip-flops (the IC's, not the footwear), timers and logic gates before I ever wrote my first program. I cut my programming teeth using BASIC on a PDP-11 and had a pretty thorough understanding of how the machine worked at the ripe old age of 13. I ditched BASIC in favor of 6502 assembly language on the PET and C-64, and then other processors, so I was working always close to the hardware (it was the nature of the work I was getting.)
Marc
|
|
|
|
|
AmigaBASIC, modifying a demo. I only knew that Big Fat Agnus, Paula and Denise were respsonsible for the output, and the result of the tinkering was predictable[^].
I should really get a 512 kb RAM upgrade.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Quote: I should really get a 512 kb RAM upgrade.
My first PC was a Step386 with (wait for it) 4 Megabytes of memory, the "Bleading Edge". Paid $1,000.00 for each chip.
Dave.
|
|
|
|