Well just convert everyone who is not Win2k to Win2k or NT4. Then you as the admin can access everyone's harddrives using the c$, d$ shares... then have a script that backsup everyones data to the HD... OR.... use a centraly located profile and logon/logoff scripts to map a drive from your file server to their machine where all of their "user data" is stored to be backedup.
C# isn't a replacement for Java.....NET overall is. Every language in.NET is designed to work on every OS.... IF and that's a BIG IF the.NET framework is designed for each OS. Right now it's only for Win. And I don't see MS actually making it for anything else other than Windows. They have only build themselves a safety net that IF *nix takes over (and that another IF) that they will still be left in the market.
Personally I think *nix has a long way to go to take over the desktop. And until it does take over the desktop it won't take over the server market completely either. It is much easier to manage everything in the same environment. Don't believe me? Remember Novell and Win3.x/95? I'm sure I'll have a nice long article for your guys soon.
Ok, so in ten years the OS is going to be replicating files across many users desktops... Typically we have a File Server/Client setup these days with clients typically on a 100mb pipe... (10 years ago what was everyone using... about 10mb, so network speed hasn't increased that much), then compare the size of files today versus files 10 years ago. I bet you the size of the files has grown faster than the speed of the network. An now you want to multiply the size of the file and send it across a already loaded net? Nice idea, but there are some other improvements that need to be made first.
Also stay away from books that beat a topic to death and go off on a tangent to make it thicker. Example, a friend of mine, Bob Summers, wrote the "Official Microsoft NetMeeting 2.1 Book" and its 350 pages.... do I really need to read 350 pages on NetMeeting... the book goes to far into how NetMeeting actually works from a low level than on how to actually use it.
They started using this in the CS Department at VT in '94. Not only does it compare you to your fellow classmates but it compares to its history of programs it's read... so you can't use the same code someone else used years ago if the project ever came up again. It caught about 60 out of 300-400 people the first time it was used. What ever happend to "working as a team"? hehe.
You must put alot of initial design in a OOP to make it re-usable. Start with making functions more universal. Where there's a will there's a way. It's just going to take more time initially to code a reusable program than one just designed to solve one particular task.
I left school early to, and I'm still kicking ass except in a mixture of MS and AIX world. The kids are not informed because the Faculty is not informed. Take a moment and go through the computer science faculty pages at your school, mine being http://www.cs.vt.edu (Virginia Tech) and take a good look at the expreience the faculty has. It will usually read as follows.
19xx Bachelors Degree - Somewhere
19xx+1 Masters Degree - Somewhere
19xx+4 Doctoral - Somewhere
19xx+5 - 19xx+10 - DoD/Navy research
19xx+y Assistant Professor - Somewhere
19xx+z Professor - Somewhere
19xx+a1 Grant studay of something that has no real world application
19xx+a2 Got another million dollars to research something that will probably be pointless.
And then these are the people who are educating the programmers/analyst who, 99% of them, will be out in the real world and have to have some usefull skills. Please teach something practicle in school and quit making students re-invent the wheel on every project. Let them be creative.
My father-in law recently put a addition on his house and in each room of the addition on each wall he ran flexible plastic tubes and a junction box to underneath his house. Now if any new technology comes out that he needs to wire for he can just slide the wires in the tubes and the drop out in the basement. Fiber is expensive but one day may be common place now he can upgrade easily for anything.
Slashdot Mirror
Well just convert everyone who is not Win2k to Win2k or NT4. Then you as the admin can access everyone's harddrives using the c$, d$ shares... then have a script that backsup everyones data to the HD...
OR.... use a centraly located profile and logon/logoff scripts to map a drive from your file server to their machine where all of their "user data" is stored to be backedup.
Simple answers to a simple problem.
C# isn't a replacement for Java.... .NET overall is. Every language in .NET is designed to work on every OS.... IF and that's a BIG IF the .NET framework is designed for each OS. Right now it's only for Win. And I don't see MS actually making it for anything else other than Windows. They have only build themselves a safety net that IF *nix takes over (and that another IF) that they will still be left in the market.
Personally I think *nix has a long way to go to take over the desktop. And until it does take over the desktop it won't take over the server market completely either. It is much easier to manage everything in the same environment. Don't believe me? Remember Novell and Win3.x/95? I'm sure I'll have a nice long article for your guys soon.
Sounds like you and I work at the same place.
Ok, so in ten years the OS is going to be replicating files across many users desktops... Typically we have a File Server/Client setup these days with clients typically on a 100mb pipe... (10 years ago what was everyone using... about 10mb, so network speed hasn't increased that much), then compare the size of files today versus files 10 years ago. I bet you the size of the files has grown faster than the speed of the network. An now you want to multiply the size of the file and send it across a already loaded net? Nice idea, but there are some other improvements that need to be made first.
Books have to be paper.... laptops are too hard to read and flip from one section to another quickly and batterys die.
.NET" by David S. Platt, great book and not completely dry.
Books need to have some humor, example "Introducing Microsoft
Books need to have more examples. Personally I learn by example, by taking what someone else has done and riping it up, to make it do something else.
Finally topics on protocol design, distributed computing, client/server, server/server, client/client, load-balancing.
Also stay away from books that beat a topic to death and go off on a tangent to make it thicker. Example, a friend of mine, Bob Summers, wrote the "Official Microsoft NetMeeting 2.1 Book" and its 350 pages.... do I really need to read 350 pages on NetMeeting... the book goes to far into how NetMeeting actually works from a low level than on how to actually use it.
They started using this in the CS Department at VT in '94. Not only does it compare you to your fellow classmates but it compares to its history of programs it's read... so you can't use the same code someone else used years ago if the project ever came up again. It caught about 60 out of 300-400 people the first time it was used. What ever happend to "working as a team"? hehe.
You must put alot of initial design in a OOP to make it re-usable. Start with making functions more universal. Where there's a will there's a way. It's just going to take more time initially to code a reusable program than one just designed to solve one particular task.
I left school early to, and I'm still kicking ass except in a mixture of MS and AIX world. The kids are not informed because the Faculty is not informed. Take a moment and go through the computer science faculty pages at your school, mine being http://www.cs.vt.edu (Virginia Tech) and take a good look at the expreience the faculty has. It will usually read as follows. 19xx Bachelors Degree - Somewhere 19xx+1 Masters Degree - Somewhere 19xx+4 Doctoral - Somewhere 19xx+5 - 19xx+10 - DoD/Navy research 19xx+y Assistant Professor - Somewhere 19xx+z Professor - Somewhere 19xx+a1 Grant studay of something that has no real world application 19xx+a2 Got another million dollars to research something that will probably be pointless. And then these are the people who are educating the programmers/analyst who, 99% of them, will be out in the real world and have to have some usefull skills. Please teach something practicle in school and quit making students re-invent the wheel on every project. Let them be creative.
My father-in law recently put a addition on his house and in each room of the addition on each wall he ran flexible plastic tubes and a junction box to underneath his house. Now if any new technology comes out that he needs to wire for he can just slide the wires in the tubes and the drop out in the basement. Fiber is expensive but one day may be common place now he can upgrade easily for anything.
Lemme get this straight... he build cases that you can buy new for $20 but bought brand new monitors that cost way more than $20...
I HOPE that for this meeting you have washed your hair, shaved, lost the ratty shorts and the faded t-shirt.