|
Yes but was it already your job at that time?
|
|
|
|
|
yes ... full time job, meaning: earning money for it.
I cannot remember: What did I before google?
|
|
|
|
|
1976 - Data General Nova. PC was not invented yet!
|
|
|
|
|
1982. Intel emulators and PL/M and ASM-86, then VAX and lovely octal.
Amazing to realise I worked for years without a mouse.
A.
|
|
|
|
|
LOL... 
It was black and white mostly. No graphical environment to speak of....
Me...
TRS-80 Model I .... as a young kid with my father.
A Tandy computer from there .... actually updated the processor and added a RAM disk, with battery backup.
History from there.
Somewhere along the way, I got a job and soon started programming for a living.
I've always found the environment FUN and EXCITING to work in. Especially with all the changes over the years.
James
|
|
|
|
|
1979 direct after graduating: Fortran - ugh...
Since then it just gets better.
------------------<;,><-------------------
|
|
|
|
|
what is wrong with fortran?
 some citations from ... experienced developers:
real programmers are writing fortran. in any language.
if it cannot written in fortran, it is not worth to be written.
I cannot remember: What did I before google?
|
|
|
|
|
>what is wrong with fortran?
IMPLICIT NONE
(:
------------------<;,><-------------------
|
|
|
|
|
First paid job in 1977 on DEC PDP-11...
Worked with DataGeneral mainframes at college -
Input by punched paper tape created on a mechanical teletype.
At the risk of sounding a bit Monty Python:
"Kids nowadays, they don't know they're born!"
|
|
|
|
|
Commodore 64 was the first computer (if you can call it that ) I programmed on as a professional back in the 80's.
First computer language I learnt was Cobol in college. Now I handle the Microsoft Stack from UI (web/desktop) to server side (primary SQL Server). You have to learn a hell of lot more now-a-days then the
10 print "hello"
20 Goto 10
type of programming. Threading, security, web standards/protocols just to name a few.
I am still worried about being employeed in my 50's (only another 5 years away), the same went for my 40's, and come to think about it my 30's as well. Time will tell. If you can adapt and keep current with technology then you have a better chance of being employed.
I bet programming today will be totally different in 5 years time (with multitouch screens, speech recognisation etc).
Richard....
|
|
|
|
|
As a kid I received a C16... (a downsized C64, just 16KB of ram, 1984) throwed it away a few years ago.
But my first steps where there: basic, and even some assembler.
In the office, we still have a few C64 standing around using them (more and more seldom) as simulators (custom eeproms with program in basic)
Big advantage: just power them and they are working in less thant 5 seconds!
|
|
|
|
|
20 years? Hah! I started in 1969 on IBM 360 mainframes. Am now 61 and still writing code, these days in VB.NET and C#NET, and even things like jQuery. And still having fun.  But having said that, I'm not working full-time now, and probably won't be in the game professionally for much longer. But still, 40+ years, not bad.
|
|
|
|
|
1968 IBM 534 OCR, 1970 IBM 1401, 1973 IBM 360... OMG that sure makes me old.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
