1. When I was working with big iron (IBM 3090), I went to a customer to upgrade some software. We started friday 4 pm when the production line stopped for the weekend. The customer had a big party the same night, so we wanted to finish the upgrade in a snap. Needless to say, some issues came up and the time schedule slipped a bit. The customers team lead became increasingly tired and bored. At some stage, he needed some support for his head, so he leaned against the wall. Do I have to write, what was on the wall? Correct. The Big Red Button. So after IML and the whole fuss, we completed the upgrade around midnight.
2. Another customer, still IBM 3090. This customer operated around the clock, so there was always somebody in the data centre. One evening, the staff played cards. One of the guys lost a round and got very upset. He threw his cards on the table, yelled "WHAT!", simultaneously throwingh his arms to the sides. Unfortunately, he was sitting close to the wall on which the BRB was placed and of course he hit it.
When you have read Code Complete, you should proceed to
"Writing Solid Code" and then
"Debugging The Development Process", both written by Steve Maguire.
Also, I highly recommend reading "Structured Computer Organization" by Andrew S. Tanenbaum or some similar book on computer architecture. Why? Because you can be a very skilled programmer, but if you don't know what the engine below the code actually does (or is supposed to do), you may work on wrong assumptions.
And then of course the whole Disc World series by Terry Pratchett to relax...
I really dont think the USER cares about the command line. He/she starts an APPLICATION (or a program, as we used to call them) and that's it. During the eighties, I installed several PC's on which the one and only application was started in autoexec.bat. So the user never had to relate to c:\>
My point is, the command line is not a very good reason to abandon any OS from the users point of view. The view of a geek is another story.
By the way, command line history is available in DOS (nowadays), but you have to activate it. Put "doskey.com" in your autoexec.bat and you can use the up-arrow to browse the previous commands. Personally, I find that much more convenient that using escape-k in ksh.
Yes we do - even in Europe! However, it seems to me that many of us are lazy when it comes to pushing the shift button. So it may not have anything to do with being illiterate. It may have something to do with
1. difficulties hitting the right keys on the keyboard 2. not being a native English speaker (the internet crosses any border - and so does/.) 3. focusing on contents rather than form 4. not giving a damn
I think everybody understood "gb" in this context.
... communicating. Nothing more, nothing less. Speach or SMS. Fine. For gaming I think a PC is a better choice. It has a proper screen, pointing device and sound. Why should I want to play games on my phone? Of the same reason that I should want my pencil to make coffee!
Devices do have a purpose, or so I thought. Oh silly me. I'm just SOOOO boring and old fashioned.
I started wondering too. The only thing I use computers for is serious programming, writing, accounting, and internet browsing (and I dislike the graphics on the sites).
I think this product solves a problem, which does not exist.
But hey, maybe a 3D display can add another dimension to programming.
Once upon a time, I bought a safe for my guns. I even locked the door in the safe. Still, somebody broke in and stole my guns. So, now the manufacturer is liable for the harm done? I mean, the safe was not safe afterall!
Hey, get real. I bet MS or anybody else don't make security holes on purpose, just as the company that made my safe did not intend it to be breakable - oh, sorry, that safe was NOT made by Oracle.
Slashdot Mirror
How low can you go?
1. When I was working with big iron (IBM 3090), I went to a customer to upgrade some software. We started friday 4 pm when the production line stopped for the weekend. The customer had a big party the same night, so we wanted to finish the upgrade in a snap.
Needless to say, some issues came up and the time schedule slipped a bit. The customers team lead became increasingly tired and bored. At some stage, he needed some support for his head, so he leaned against the wall. Do I have to write, what was on the wall? Correct. The Big Red Button. So after IML and the whole fuss, we completed the upgrade around midnight.
2. Another customer, still IBM 3090. This customer operated around the clock, so there was always somebody in the data centre. One evening, the staff played cards. One of the guys lost a round and got very upset. He threw his cards on the table, yelled "WHAT!", simultaneously throwingh his arms to the sides. Unfortunately, he was sitting close to the wall on which the BRB was placed and of course he hit it.
When you have read Code Complete, you should proceed to
"Writing Solid Code" and then
"Debugging The Development Process", both written by Steve Maguire.
Also, I highly recommend reading "Structured Computer Organization" by Andrew S. Tanenbaum or some similar book on computer architecture. Why? Because you can be a very skilled programmer, but if you don't know what the engine below the code actually does (or is supposed to do), you may work on wrong assumptions.
And then of course the whole Disc World series by Terry Pratchett to relax...
I really dont think the USER cares about the command line. He/she starts an APPLICATION (or a program, as we used to call them) and that's it. During the eighties, I installed several PC's on which the one and only application was started in autoexec.bat. So the user never had to relate to c:\>
My point is, the command line is not a very good reason to abandon any OS from the users point of view. The view of a geek is another story.
By the way, command line history is available in DOS (nowadays), but you have to activate it. Put "doskey.com" in your autoexec.bat and you can use the up-arrow to browse the previous commands. Personally, I find that much more convenient that using escape-k in ksh.
Yes we do - even in Europe! However, it seems to me that many of us are lazy when it comes to pushing the shift button. So it may not have anything to do with being illiterate. It may have something to do with
/.)
1. difficulties hitting the right keys on the keyboard
2. not being a native English speaker (the internet crosses any border - and so does
3. focusing on contents rather than form
4. not giving a damn
I think everybody understood "gb" in this context.
... communicating. Nothing more, nothing less. Speach or SMS. Fine.
For gaming I think a PC is a better choice. It has a proper screen, pointing device and sound. Why should I want to play games on my phone? Of the same reason that I should want my pencil to make coffee!
Devices do have a purpose, or so I thought. Oh silly me. I'm just SOOOO boring and old fashioned.
I started wondering too. The only thing I use computers for is serious programming, writing, accounting, and internet browsing (and I dislike the graphics on the sites).
I think this product solves a problem, which does not exist.
But hey, maybe a 3D display can add another dimension to programming.
Once upon a time, I bought a safe for my guns. I even locked the door in the safe. Still, somebody broke in and stole my guns. So, now the manufacturer is liable for the harm done? I mean, the safe was not safe afterall! Hey, get real. I bet MS or anybody else don't make security holes on purpose, just as the company that made my safe did not intend it to be breakable - oh, sorry, that safe was NOT made by Oracle.