All things related to Computers

[Nom De Plume]

Oh, dearie, dearie, me. I suspect I know a lot more about computers and operating systems than you do, Neferti. I got my first Apple II way back in 1983. I bought an Apple IIe in 1984 and then my first PC in 1987. I could go on boasting but hey, what would be point? Your ideas on how the world of computing works is very different to mine but hey, I'm a professional IT Systems Engineer and you're a?

MY first PC at home was one I had "built" to my specifications by a local (Canberra) computer place. If I remember correctly, it cost me $1,500 in 1984. It had DOS as there was no such thing as Windows. I did not go out and purchase an "Apple". However, I have a so-called "technical mind" and I did NOT need to be told by any "Systems Engineer"what type of personal computer I required.

WHY do I scare you, Brian?

[Redneck]

Oh, dearie, dearie, me. I suspect I know a lot more about computers and operating systems than you do, Neferti. I got my first Apple II way back in 1983. I bought an Apple IIe in 1984 and then my first PC in 1987. I could go on boasting but hey, what would be point? Your ideas on how the world of computing works is very different to mine but hey, I'm a professional IT Systems Engineer and you're a?

Oh dear Bwian being a wanker again!

Rather sad !!

[Nom De Plume]

Oh, dearie, dearie, me. I suspect I know a lot more about computers and operating systems than you do, Neferti. I got my first Apple II way back in 1983. I bought an Apple IIe in 1984 and then my first PC in 1987. I could go on boasting but hey, what would be point? Your ideas on how the world of computing works is very different to mine but hey, I'm a professional IT Systems Engineer and you're a?

MY first PC at home was one I had "built" to my specifications by a local (Canberra) computer place. If I remember correctly, it cost me $1,500 in 1984. It had DOS as there was no such thing as Windows. I did not go out and purchase an "Apple". However, I have a so-called "technical mind" and I did NOT need to be told by any "Systems Engineer"what type of personal computer I required.

WHY do I scare you, Brian?

You don't scare me in the slightest, Neferti. Why are you frightened that someone might known more than you? I have been in IT professionally since 1987. Take my word for it, your experience isn't unique nor is all that exemplary. My experience is very different to yours, that's all and all your boasting is just that, boasting.

[Nom De Plume]

In IT, if I want to understand how TCP/IP works, I consult a university trained Systems Engineer. If I want TCP/IP to work, I consult a TAFE trained Systems Administrator. He can connect up the devices and get them to talk to one another but is at a loss when that doesn't work, whereas the Systems Engineer can figure out the reasons why it isn't working.

If you are a professional IT Systems Engineer why do you need to consult anyone?

'cause I don't know everything, Black Orchid and I am quite willing to admit my ignorance when asked a question which I don't know the answer to.

[Nom De Plume]

professionally since 1987. Take my word for it, your experience isn't unique nor is all that exemplary. My experience is very different to yours, that's all and all your boasting is just that, boasting.

When you pull your fucking head out of your arse and read what I said for the VERY FIRST TIME ... you might realise who is "boasting" and it isn't' me, myself I. I have the "receipts" here. I don't do "hardware" I do "software".

[Nom De Plume]

In IT, if I want to understand how TCP/IP works, I consult a university trained Systems Engineer. If I want TCP/IP to work, I consult a TAFE trained Systems Administrator. He can connect up the devices and get them to talk to one another but is at a loss when that doesn't work, whereas the Systems Engineer can figure out the reasons why it isn't working.

If you are a professional IT Systems Engineer why do you need to consult anyone?

'cause I don't know everything, Black Orchid and I am quite willing to admit my ignorance when asked a question which I don't know the answer to.

If I employed a Systems Engineer I would expect him to know everything related to his field of expertise.

[Redneck]

Just Bwian trying to feed his oversized ego!

Tsk Tsk



Best ignored is my advice!

[Nom De Plume]

He did a Bas (LOL) and got a credit for "computer studies".

[Nom De Plume]

In IT, if I want to understand how TCP/IP works, I consult a university trained Systems Engineer. If I want TCP/IP to work, I consult a TAFE trained Systems Administrator. He can connect up the devices and get them to talk to one another but is at a loss when that doesn't work, whereas the Systems Engineer can figure out the reasons why it isn't working.

If you are a professional IT Systems Engineer why do you need to consult anyone?

'cause I don't know everything, Black Orchid and I am quite willing to admit my ignorance when asked a question which I don't know the answer to.

If I employed a Systems Engineer I would expect him to know everything related to his field of expertise.

Then you would be foolish, System Engineers like all professional people tend to specialise in particular technologies. I specialise in Unix and Linux with a smattering of Windoze thrown in. Give me a system which is malfunctioning and I will fix it so that it works properly. However, I admit I know very little about databases. I am not a DBA nor have I ever claimed to be one. Unlike Neferti, I know a lot about hardware and software and the interactions between the two. I can script and at a pinch, I can program. I know all about security and firewalls.

[Nom De Plume]

He did a Bas (LOL) and got a credit for "computer studies".