What was the "Next Big Thing" when you started programming?
-
Eee 4k! We used to dream o' 'aving 4k! There were twenty four o' us living in shoebox in middle o' road...
You got a shoebox? How lucky is that? We got a potato sack!
-
Hexadecimal. Seriously. :)
Boy! You ARE old! (lol?)
-
Colour was the next big thing when I started programming although a lot of people couldn't really see the point in it :~ When I started programming commercially we were really into COM+, it was the answer to everything, apparently (it wasn't so much like .net as like remoting). What it really did for us was to add another point of failure and an extra layer of network bottleneck between the clients and so created applications that were much harder to debug than the Client Server they replaced. We also had Thin clients when NT4 Terminal Services edition came out, soon to be replaced by rich clients when .Net took over. There was XML, nothing makes an application run so badly as something that takes some data from a database creates an enormous xml document transforms that document repeatedly into other documents and then spouts out some xhtml at the end (but hey we only need 2 stored procs now) There's OOP for websites where we used to create massive hierarchies of objects so we could make one method call and then dispose of the objects only to create them again when the user clicked submit.
> Colour was the next big thing when I started programming although a lot of people couldn't really see the point in it I remember that was the big deal about the Apple II. It was the first relatively affordable personal system that had built-in color. Remember, games back then were text-only, like "Adventure". Why would you need color for a computer game? Also, remember that the first Macintosh was black-and-white. Steve Jobs was known for once saying, "There will never be a color Macintosh".
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoI wrote my first program in 1973 (as a kid mind you). I used an IBM 1500 system with light pens and TV-like CRT screens that could only render characters. The radical idea here is that you could have your program run immediately after it was input, and you could interact with it in real time. I loved to write games. I recall very smart people wishing for screens that would be graphic rather than alphanumeric - but memory at the time was very expensive and such a system would not be economical. This was almost heresy at the time. Most "serious programmers" only used Hollerith Cards run on batch. Your output from the compile / run cycle would be printout onto a large sheet of paper. You could pick it up after about 10 minutes, and fix any errors by retyping the offending cards and inserting them back into the deck. Yuck! Slow! By about 1980, most "serious programmers" had moved to screens and keyboards. I was then exposed to a Xerox Sun (the forerunner of the Mac). All of us knew that this was the future. The mouse and graphic-based screens were a no-brainer for anybody that did scientific programming. Unfortunately, the marketing people did not see it that way, so we had to wait until the Macintosh in 1984. By that time I was entering the workforce and most companies still used green screens attached to mainframes. It was not until 1989 was I able to convince the company I was working with to use Windows 2.11 instead of the mainframe. This was considered dangerously radical - but I managed to keep it under the corporate radar until it was done. It was a huge success that spawned a lot of copy cats. Since that time, I have seen little real change. The capabilities and refinements of personal computers has increased perhaps a million-fold since then, but the basic principles have not really changed since the early 1980's with the Xerox Sun. Unfortunately, software is so bloated today that most of the hardware improvements have been largely negated. The start-up times are still agonizingly slow. Like the Lewis Carroll's red queen, we're an industry that spends a lot of energy going nowhere. Just my two cents worth.
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoRISC, Concurrent Euclid, VAX/VMS (which I used for fourteen years[^] :cool:) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
You got a shoebox? How lucky is that? We got a potato sack!
A whole sack!? :omg: /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I wrote my first program in 1973 (as a kid mind you). I used an IBM 1500 system with light pens and TV-like CRT screens that could only render characters. The radical idea here is that you could have your program run immediately after it was input, and you could interact with it in real time. I loved to write games. I recall very smart people wishing for screens that would be graphic rather than alphanumeric - but memory at the time was very expensive and such a system would not be economical. This was almost heresy at the time. Most "serious programmers" only used Hollerith Cards run on batch. Your output from the compile / run cycle would be printout onto a large sheet of paper. You could pick it up after about 10 minutes, and fix any errors by retyping the offending cards and inserting them back into the deck. Yuck! Slow! By about 1980, most "serious programmers" had moved to screens and keyboards. I was then exposed to a Xerox Sun (the forerunner of the Mac). All of us knew that this was the future. The mouse and graphic-based screens were a no-brainer for anybody that did scientific programming. Unfortunately, the marketing people did not see it that way, so we had to wait until the Macintosh in 1984. By that time I was entering the workforce and most companies still used green screens attached to mainframes. It was not until 1989 was I able to convince the company I was working with to use Windows 2.11 instead of the mainframe. This was considered dangerously radical - but I managed to keep it under the corporate radar until it was done. It was a huge success that spawned a lot of copy cats. Since that time, I have seen little real change. The capabilities and refinements of personal computers has increased perhaps a million-fold since then, but the basic principles have not really changed since the early 1980's with the Xerox Sun. Unfortunately, software is so bloated today that most of the hardware improvements have been largely negated. The start-up times are still agonizingly slow. Like the Lewis Carroll's red queen, we're an industry that spends a lot of energy going nowhere. Just my two cents worth.
Back in those days, one program could easily weigh 20-30 pounds! (not including job control)
-
Back in those days, one program could easily weigh 20-30 pounds! (not including job control)
Also, heaven help anyone that dropped that box!
-
Back in those days, one program could easily weigh 20-30 pounds! (not including job control)
I am sure that many pranks were based on dropping fake card decks. I seem to recall that some people would make corrections to their cards with tape. Best yet, old decks also became a ready supply of geek bookmarks when they were no longer needed. I think I still have one in the bottom of a drawer somewhere.
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoLet's see... PL/I was the first language I wrote a "Hello world" program in (It was supposed to "replace COBOL") I worked on paper cards for an IBM system 360/75 running OS 360 MFT and HASP 4.0... A 300mb drive was the size of a washing machine, tape was king at a density of 6250bpi (that's bits per inch)... The smallest machine I worked with in College came built into it's own desk, had 16k bytes of Plessy Microsystems ferrite core memory and a single 18" platter 5mb disk. That was when DOS 1.0 was still in Bill Gates' dreams... The first PC language I learned was Intel Assembler for the 8088...
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoI like this question ... There's a song, "Everything Old is New Again". If you can find an MP3 snaffle it. * [] 'When' I started - Networked operating systems (like what evolved to AmigaDOS, CTOS, SNA 6.2) and died with the internet. Networked data models (like what relational systems killed off) and O/R ORM-s and Object Graphs reinvent. Hand-held devices like my HP calculator, small computers. Useful languages like Algol-68, Simula, Smalltalk, awk, SNOBOL -- May be 4GL ideas that made solutions tractable -- BUT still employers want you to code in (um) 2nd level assembler languages. I 'get' it. Language technology only ads 3% to our development productivity (depending on 'how' its measured).
* I'll debate that because 4GL-s also add value to the business analysis (that gives you 60% of project performance -- Anyway you measure it).
The biggest "next big thing" was that management would learn something about software development (because at that time, there were no developer managers, just people wanting a H-RESULT :laugh:). ... I'm older now. I've worked my way through 2 masters degrees on technology and management so I might be wiser (grunt:suss:). The intractable software development problem is NOT technical or technology. If I can comment; an architecture professional told me the 'same' profile of the same story for builders. In contrast chemical engineers 'prescribe' below 10% +/- deviation on projects. If your project exceeds -- It dies. I'm sure everyone knows what happens when the costs on phase I go past 10%? The "next big thing" for me? They all failed to deliver the promise. If I find smart people, we can fulfil that promise (from 40 years ago). When Apple was new. DEC was new. HP was old, IBM was old. 3M was old then. There was NO 'Microsoft', 'Google', 'Yahoo', 'no PC-s'. W
-
Upgrading from 16k to 48k Colour Monitors I heard talk of a strange devie called a mouse, but it seemed so far away. Affordable hard drives instead of twin 8" Floppies. 5 1/4" Floppies.
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
I wrote my first program in BASIC on an IBM PCjr running DOS 2.10. Being a kid at the time I didn't have any concept of the next big thing, although I remember having to load disk after disk into the 5 1/4" drive when playing King's Quest. When I wrote my first program commercially my co-workers were desperate to get off Visual InterDev and into this new .NET thing.
Mike Devenney
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoI started programming in high school. We built a SOL20, programmed in BASIC loaded from a cassette player. Five minutes to load the interpreter--if it didn't fail to load. Going to college, they just got rid of the keypunch machines. I bought an Atari 800 and was able to dial up at 300 baud to write my FORTAN programs. I was programming in style. No more waiting for days at the distribution desk for my printout. PC's were brand new when I entered the work force. I like to joke with co-workers that I'm older than the internet. :) One intern suggested I was older than computers. He thinks of computers as PCs, so in that sense I am. As I work in a government facility it comes in handy I can fire up a PDP-11, update DOS programs and revive Windows 3.1 machines. W00t!
-
Hexadecimal. Seriously. :)
Not that ancient actually :) just got my start at the tender age of 13. I was lucky enough to find the Computer Education Research Laboratory at the University of Illinois in 1973. Their mainframe was a CDC Cyber 73, which for whatever reason, used an octal number system. Just what a growing teenager needed to stay out of trouble in the 70s. :)
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoThe world wide web. Of course, I didn't realize it'd ever be this big of a thing :) But that was when I was in college. The big thing when I learned programming was... the personal computer. I was so envious when a friend of mine got one of those new IBM 5150 Personal Computers.
patbob
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango