|
Peter, are you THE Peter Grogono who wrote "Programming in Pascal" (circa 1980) - the book that changed my life (for the better) forever?
/ravi
|
|
|
|
|
Yes, that's me. Good to hear that I changed your life -- for the better  I wrote the Pascal book during 1977-78, before I had my own computer. The Pascal programs in the book ran on a CDC 6400 at the university where I was working.
Peter
|
|
|
|
|
Wow. It's an honor to bump into you @ CP! I think I emailed you a couple years ago to thank you for opening doors for me in a way you could probably not have imagined. I'm pretty sure I've saved your reply.
Thank you, again! ![Rose | [Rose]](https://codeproject.freetls.fastly.net/script/Forums/Images/rose.gif)
/ravi
|
|
|
|
|
|
I bought my first PC in 1984 (had been using university and work hardware before that):
- IBM-AT 80286 processor @ 8MHz, 512KB RAM
- Hercules EGA Graphics
- 20 MB Seagate hard disk
- 5¼" 360K floppy drive
- 5¼" 1.2M floppy drive
- Princeton Graphics Color Monitor
- Okidata Microline 192 dot matrix printer
- Hayes 1200 Modem
Software:
- MS-DOS 3.1
- PC Write (editor)
- Lattice C compiler
- Vitamin C GUI SDK for DOS
The hardware set me back $4500. I think the compiler was $300, Vitamin C was $50 and PC Write was $30. The box came with MS-DOS.
I misread your question as "What was your first PC?" My first computer was a Honeywell Multics system with the world's most awesome terminals I'd ever seen. Circa 1980.
/ravi
|
|
|
|
|
Mine was a TRS-80 MC-10 (baby CoCo). It had 4k of RAM, jacks for attaching a tape deck to load software that didn't exist, and could display a whole nine colors. Even for the time, it was a PoS, it made the C64 look like a supercomputer. But it was mine, and I learned to write (short) programs on it.
OriginalGriff wrote: I'm not counting Spectrums and their ilk here: if it had a cassette tape it doesn't count
Ridiculous, you're excluding most 8-bit computers because they used tape instead of (expensive at the time) floppy drives. Back in the day, those were "real" computers. This just seems like an arbitrary way to exclude anyone who got their first computer in the '80s and didn't have a lot of money (those business-class IBMs went for $3k-$5k in '80s dollars).
|
|
|
|
|
Would you believe a DEC PDP-8/I, in 1971? I/O was a 10 CPS ASR-33 Teletype with paper tape. Life got a lot better when I managed to score a 300 CPS tape reader.
|
|
|
|
|
Altair 8800 (still up in the attic)
64K Ram (a portion of that was ROM for the CUTER system)
Punched paper tape for storing programs
Front panel switch input
Video to Channel 3 NTSC
Eventually upgraded to Micropolis 390K floppy drive
I'm not a programmer but I play one at the office
|
|
|
|
|
Wow,
Timex Sinclair (admittedly, no drive, but a 40 col thermal printer!) [I returned it, BTW]
TI 99/4A (Expansion Pack, Plus Floppy)
TRS-80 Model 1
PDP-11/34a (at school, 20 paper terminals, and 3 CRTs for the cool kids, LOL)
All within 1yr.
Then I moved UP in the world: I got a Tandy-1200 HD (monochrome, green screen) DOS.
With a HD and a Floppy, LOL...
This lasted me until my first Dell in College. And I have been using various Dells since!
(Of course, Dell was called PCs Limited back then).
Kirk Out!
|
|
|
|
|
My first computer was an s100 bus z80 base system (back in the late 70's). I wire wrapped all the boards except for the graphics card (16 lines by 64 ASCII characters) which connected to a small TV. I had a 2KB monitor program called Zapple and a total of 4K of RAM. I use to know most of the z80 instruction set by the numbers since I didn't have a z80 assembler. This system eventually morphed into a CP/M system with 48KB of RAM and 2 high density 8 inch floppy drives! Talk about a fun time learning about computer hardware and software.
|
|
|
|
|
My first computer was one I designed and built myself, starting the day the 8080 CPU was released, in late 1974. There was no commercially available microcomputer in those days. By Feb. 1975 I had it up and running, with a huge 1K of RAM! I had to put a small boot program using the front panel switches, and I had an old 33ASR teletype with a paper tape punch and reader for mass storage, as well as keyboard input and printed output.
|
|
|
|
|
My first was a Philco C2 (named for the building that housed it). It had a fantastic 28k of RAM. Data and programs were loaded using 80 byte punch cards. Due to limitations, we could only load 2007 data cards. If we exceeded the data limit, I would have to do the calculation on a Friden calculator to determine which of the cards I could yank to complete the run on the C2.
The difficult may take time, the impossible a little longer.
|
|
|
|
|
My first was a Commodore Pet 2001 with no HDD, no FDD, and no cassette tape drive. I had to type programs in every time.
My second was a Commodore Pet 4000 with the integrated "datasette" cassette tape drive.
Third was a Franklin Ace 2000 (Apple IIe clone) with a 5MB HDD and 5.25" floppy. I added a Bernoulli box with two 10MB cartridges the next year.
I kept them in the garage until about 15 years ago, when my wife made me start "disposing" of all my old computer equipment.
|
|
|
|
|
OriginalGriff wrote:
What was your first "real" computer? (I'm not counting Spectrums and their ilk here: if it had a cassette tape it doesn't count )
Mine was a Xerox 820 with the dual-processor option plus an eight-inch floppy drive and an eight-inch, eight megabyte hard drive in a separate case. It was already eight years old when I got it.
http://en.wikipedia.org/wiki/Xerox_820
|
|
|
|
|
My first real computer was a 16K TRS-80 Color Computer; I know that may not fit your specs as to it being a "real" computer. I started with a cassette tape, but quickly (within a year) convinced my parents to get me a floppy drive.
I later moved to the Color Computer 3, and eventually upgraded it from 128K to 512K. I still have both of those machines, and they both work today.
My last Radio Shack machine - which would fit your definition - was a Tandy 1100HD; it was also my first "laptop" (certainly not a luggable like the Kaypro, but nothing like today's lightweight beasts). It had a 20Mb hard drive, and a 3.5 inch floppy. I still have that machine as well (though I don't know if it still works - I haven't turned it on in ages).
My next machines after that were an Amiga 2000, then an Amiga 1200. Then I got a 486 DX2/50 after Commodore bit the dust - plus I fell in love with the game, Myst, at the store - and had to have that system to play it.
As far a PC CPUs are concerned, my favorite has always been the AMD 586/133 - a weird hybrid; basically a crazy-fast 486 - at the time, it could outperform some of the lower-end pentiums (back when there was a serious AMD/Intel rivalry), for a fraction of the cost. It could be overclocked to 166 MHz fairly reliably, too.
|
|
|
|
|
Acorn Archimedes 305. A great machine for hacking about in both the hardware and software sense.
Great BBC basic with inline ARM assembler. I remember changing a magazine mandelbrot program to do 64 bit arithmetic. Lots of folks hacked the !Sprites files so icons for programs were unrecognisable on 'hackers' machines.
Matthew Broadbent of the Auckland Acorn Users Group created a sound sampler by attaching resistors to the parallel port lines. A binary chop style algorithm established the analog to digital value. I hacked the ST-506 cable to split the cylinders of a big external Hard Drive so it looked like two disks (too many cylinders).
I've never messed with my subsequent PCs like I messed with the Archimedes.
I am a set of distortions of spacetime. Jeremy Thomson
|
|
|
|
|
I have an idea for an article, a not yet another CRUD implementation for the delectation of the community. The CRUD part is minimal though as I want to concentrate on an oft ignored part of the development process.
Listen carefully as I shall say this only once*, it will be looking at design decisions rather than just code. To do this I need a simple idea that will be [a] big enough to elicit decent ideas, yet [ii] small enough to not swamp the rest of the article. So, I ask you one and all for suggestions. I am looking at a web based solution, but not one that is front-end heavy.
I have dismissed the idea of a blog as it has been done too many times already; both here and elsewhere. A micro-commerce idea might work or some twisted hack on social media.
I will give credit [if required] to whoever gives me the bestest idea.
* We've been watching more Allo, Allo than is actually healthy.
veni bibi saltavi
|
|
|
|
|
Software to do a frame-by-frame analysis of "One night in Paris"? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Just for that, you can go to the soapbox and read the article I just added there...
veni bibi saltavi
|
|
|
|
|
That's...um...disturbing
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I'd only need a "D" program for that; the "CRU" wouldn't serve any purpose.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
A project management site is too big?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
One idea I thought of was an agile type storyboard / backlog / planner / oh feck we forgot that type thing, but I thought it might be too big for the purposes I had. I'll thunk about that.
veni bibi saltavi
|
|
|
|
|
How about a Kanban board, or "sprint manager" for Agile development?
However, to be honest, I'm not actually sure what you're trying to accomplish.
Marc
|
|
|
|
|
What I am trying to get to is a sort of user story / epic to describe a problem and then to walk through the design and development decisions that leads to. I started with this as an original requirement artefact:
Requirement: We are a small software company. We produce bespoke solutions and are currently working to a very rigid Waterfall Methodology. We want to be more agile, but need a way to record our backlogs and manage our sprints.
We have multiple projects and our staff regualarly work on different clients' requirements at any time. As an example Bob does pretty much all the UI/UX work for all our software and only hands over the mundane bits to some of the juniors. There is some infrestucture stuff that we do that is shared across most of our work, but on the whole projects are self contained.
A fair proportion of our business is done on-site and so the guys need to be able to log what is happening remotely. As I see it, to start with we will need to be able to record the user stories, prioritise them and build up sprints. Once the development work starts we will need to be able to record work done and monitor progress through metrics such as velocity.
I want to then use that to show how it works in real world thinking.
veni bibi saltavi
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
