|
Similar... Commodore PET - BASIC then Assembler, then C64.
College was VAX/VMS BASIC, VAX/VMS Assembler, COBOL, PASCAL, RPG...
Then I hit the working world and started using VAXVMS FORTran and FMS (forms).
Self taught on VB and largely stayed there.. when I have to program, its VB.NET now.
Largely administer OSISoft tools, so not a lot of programming.
|
|
|
|
|
I remember using VAX at college for COBOL programming. BASIC was where I lived for quite a few years, although I did tinker with machine code on the VIC-20 and C64. The Amiga had enough BASIC compilers to live without assembler 
I've done C# for the longest period but there's been C, C++, VBScript, VBA, Pascal (at school), various versions of BASIC, a weird language called Omnis, a proprietary one called Protel, Swift, a bit of Java every now and again, plus all the usual javascript and CSS frameworks.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
Cool! A Commodore guy.  I started on the Tandy machines. My first was the TRS-80 MC-10. I checked out a book called "100 games in Basic" and typed every one of those things in. The tough part was on the MC-10, you had to use a pencil to type on the keyboard, because the keys were so small. 
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
Yeah, Commodore were sensible enough (perhaps because of their typewriter experience) to put a half-decent keyboard on their machines. The Sinclair computers were capable machines but the keyboards were (IMO) awful.
Funnily enough, I've recently bought both a Commodore Amiga (A1200 this time around) and a Commodore C64. It's weird using them again, although I have to say that using the Commodore 64 again gave me a bit of a warm feeling. With the Amiga, I'd originally had the A500 with Workbench 1.2/1.3 - the newer version on the A1200 isn't as nice.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
I soldered together my first computer and wrote machine language programs almost 15 years before I ever started to study anything.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Wow!  That is hardcore! 
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
It just means that I had to finish school first and then did not want to see a school for a while. That's why I signed up for an outfit that calls itself 'Luftwaffe' for a few years.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Donathan.Hutchings wrote: Are you self taught or do you have a CS degree in programming?
I've never actually heard of a "CS degree in programming." I have multiple CS degrees, but I only had one "programming" class, and it was a segue into a compiler-creation class. Programming is merely a tool you can use to finish solving a problem. The theory and math are all done outside of the keyboard and compiler constraints. In graduate school, we used the computer mostly for creating charts, diagrams, and thesis papers.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
Self taught 50 years ago: LEO III[^] assembler and intercode, followed by various other languages, many of which I have forgotten (COBOL, Fortran, Pascal, RPG, Sparc assembler, etc.), and some which I can remember bits of (C, C++, C#, Java, Python etc.). I did once attend an in-house COBOL course.
|
|
|
|
|
Donathan.Hutchings wrote: Are you self taught or do you have a CS degree in programming?
Both. The CS degree exposed me to a lot of data structures and programming concepts. It also tried to expose me to some languages, but their choices were mostly useless (who needs to know CDC-6500 assembly). I taught myself basic, Z80 assembly, C, C++, OO programming & OO design, C# and pretty much everything else that I've ever used in a business environment. To this day, I still rely heavily on stuff I learned from both avenues.
As for what hardware, let's just say I've written code to run on systems with actual ferrite core memory and leave it at that
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
patbob wrote: As for what hardware, let's just say I've written code to run on systems with actual ferrite core memory and leave it at that
CDC-6500 and ferrite cores - another Michigan State University grad???
|
|
|
|
|
Nope, points further south -- Purdue. Serial numbers 2 & 3 as I heard. Still in service until sometime in the 1990s (and now trying to get a second life in the Living Computer Museum[^] according to what I heard). Must be some kind of record for the longest in-production use of a computer or something. And they probably made us learn assembly for it because, well, they had it 
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
I started out as self-taught then went to university for CS degree. Dabbled with BASIC as a child. Taught myself C++ in my late 20's. Learned how to "code" with VBA. Took years of CS classes at a local university where I learned all about the fundamentals such as architecture, algorithms, and data structures (mostly in Java). Got a job. Got my feet wet in .Net with VB. Now I do most of my work in C# and SQL with a little bit of JavaScript mixed in to spice up some internal web sites.
I can tell you that I learned a lot more outside the classroom than in it but the classroom teaches you why things are they way they are so that you don't waste your time fighting up-hill battles or attempting to re-invent the wheel (re-engineering the wheel is fine, though).
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
"Self taught" and "class taught" are not mutually exclusive.
Even when taking classes, one must go beyond what's being presented by an "expert", whether that expert is teaching in a classroom, online, or in a book.
|
|
|
|
|
Self taught but I started with Excel macros - Excel 1 converting 100s of lotus 123 macros.
This leaves me without the technical grounding that a formal CS education would have imparted. I find this shortcoming quite frustrating as there are whole areas of c# that I don't use because of a lack of that grounding.
I do do excellent commercial work with the tools I do understand and enjoy exploring the boundaries of my knowledge so it is reasonably wide ranging these days.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Always went to school after-the-fact, just for documentation.
A little BASIC with the TI-99/4A
A little more BASIC with some sort of monster IBM at the community college (my girlfriend was going, and I had to drive her...figured I might as well take the class, too. Oddly enough, that's exactly how I joined the Army, too.)
Then Propero Pascal on the 520ST, some GEM, then nothing for a few years.
Then Turbo Pascal, Delphi, and finally C# in 2007.
Oh. And about 45 minutes of C somewhere in there.
|
|
|
|
|
I have CS (sort of), but I had already 10 years of learning when I started it... However some of the formal explanations I had helped me to see things orderly, but there is nothing - beyond that - in a degree prepare you to the real thing...
If one things that pushing thru the 2 (3? 4?) years of CS will let you live-out the rest of the 50, 60 - one just dreaming...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Self taught, although no gaps.
I did go through some courses at the Open University for a while, but nothing is more demoralizing and demotivating than school so I stopped doing that before it meant the end of my programming career.
Before going to school I was always working on some project or article here on CP.
During school I did almost nothing except not like programming anymore.
After school I started picking up the pace again and I'm now writing books and last year I wrote my own JavaScript LINQ library.
All better ways to learn than going to school 
|
|
|
|
|
Self-taught but took an OU CS degree a few years ago just for fun. It wasn't fun - never doing that again.
|
|
|
|
|
Self taught.
There were only three courses where I have learned something new:
- Assembler for the 6502 8-bit processor during apprenticeship (while knowing 8080 and Z80 assembler already)
- 8087 floating point instructions at university (while knowing 8086 assembler already)
- Fortran at university (while knowing Basic, C, and Pascal already)
|
|
|
|
|
Total self-taught. Built my first desktop computer in 1978 and started by writing 8080 hex code. Progressed through to assembler, BBC Basic, Pascal to VB.Net. I could never get my head around all the C variants! Still keeping the Alzheimer's at bay at 66 by writing programs for myself and family.
|
|
|
|
|
I too am fundamentally self taught . I started on simple Basic on a ZX81, quickly moved to assembler and games programming on the 6809 (which was a great processor). About 5 years later, at age 30 I went to college to get some sort of formal qualification. In the programming subjects I knew way more than the lecturer but learning some discipline was invaluable.
|
|
|
|
|
Mostly self-taught - I don't think an A-level in computing counts.
Started at home on a ZX-Spectrum.
School had several BBC Micros[^] and a couple of primitive DOS-based PCs for GW-BASIC / QBasic.
College had slightly more advanced Windows 3.11 PCs, with Pascal and a version of MS Office with the predecessors to VBA.
University also covered the basics of Pascal.
I got free copies of Delphi and an early version of Visual C++ from magazine cover discs, and tinkered with those for a bit.
Then I got a proper job, which started with VB5, Office 97, and FrontPage. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Self taught - have Chemistry and Math degrees, but learned PDP-11 assembler to write elemental analysis routines for and Inductively Coupled Argon Plasma Spectraphotometer in the lab where I worked. Then went on to x86 assembly, Delphi, C, C++, VB 6.0, Powerbuilder, MUMPS, Forth and C#. I got no stinkin' CS degree on my wall!
Anyone who cannot cope with mathematics is not fully human. At best he is a tolerable subhuman who has learned to wear shoes, bathe, and not make messes in the house. - Lazarus Long
|
|
|
|
|
I used to give week long, crash courses for computer languages to corporate programmers that needed to learn a new language.
Some highlights and lowlights:
- Highlight: Introducing C++ to a bunch of C programmers with an average of 10 years of C!
Unfortunately, the training company had selected some course from MS for transitioning COBOL programmers to C++. We covered that whole week of material in a few hours then made up our own class. They brought some samples of their nastiest (most efficient) C code that did things that C++ does not allow due to scope violations. I learned a thing or two. They had keggers every Friday, but I had to pass on the beer since I had a 3 hour drive home. - Lowlight: Not realizing until Thursday that a bunch of IBM mainframe assembly programmers that were learning C did NOT understand how the stack works! I was flabbergasted; they were really confused about the concept of local variables. I came to understand that their programs all worked on global variables. They would: load up a bunch of registers and then call a library, unload a register or two, load up some more registers and then call a library, etc.
- Lowlight: Realizing that one of my students had no concept of breaking units of work down into functions/subroutines. Their background was in an environment that I knew. I knew it supported functions (VBScript/VBA type language). Their programs only had a single main() function!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
