|
Just found this quote from Bill Gates in 1999:
"Your most unhappy customers are your greatest source of learning."
(http://en.wikiquote.org/wiki/Bill_Gates[^])
Does that mean Microsoft is learning lots with Win8? 
You looking for sympathy?
You'll find it in the dictionary, between sympathomimetic and sympatric
(Page 1788, if it helps)
|
|
|
|
|
Exactly! I agree.
Bill Gates is the technology advisor of Microsoft right now, and he knows how to learn and move forward! 
Favourite line: Throw me to them wolves and close the gate up. I am afraid of what will happen to them wolves - Eminem
~! Firewall !~
|
|
|
|
|
No! It means that even Bill Gates does not take Bill Gates seriously...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
I think they need a better hearing aid.
Have you ever just looked at someone and knew the wheel was turning but the hamster was dead?
Trying to understand the behavior of some people is like trying to smell the color 9.
|
|
|
|
|
OriginalGriff wrote: Does that mean Microsoft is learning lots with Win8?
Probably. Never in its history has Microsoft been doing so much backpedalling as they've been doing over the past few years.
|
|
|
|
|
yeah - it turns out the last "l" was a typo.
|
|
|
|
|
Ouch!
And regrettably, too true...
You looking for sympathy?
You'll find it in the dictionary, between sympathomimetic and sympatric
(Page 1788, if it helps)
|
|
|
|
|
I'm still waiting for them to see the light and get rid of the Ribbon UI...
|
|
|
|
|
Still mourning MS-DOS, eh?
|
|
|
|
|
If they'd learned anything from this, there would have been no need for Windows 2000, nor anything since.
Will Rogers never met me.
|
|
|
|
|
i have been around programming a little while and i think its a little bit too hard for me! and sometimes extremely boring.
i have no networking background so, i thought it would be a good idea to ask people who've been into both programming and networking. basically i just wanna know which field is harder to get on with and master ?
|
|
|
|
|
You also asked this question on Yahoo Answers, so there's a 90% chance that you're either:
0) a total noob in every sense of the word, or
1) a bad troll that goes for easy targets and still fails
Because those are their key demographics.
|
|
|
|
|
Both can be very challenging, but programming is potentially more difficult. Still, being really good at configuring and protecting networks can be every bit as difficult. Of the two, being a mediocre programmer is somewhat harder than being a mediocre networking guru. Both, however, require better typing skills than you appear to possess.
Will Rogers never met me.
|
|
|
|
|
YES!
|
|
|
|
|
After you remove all of the specifics related to each field, they both are careers fundamentally focused around problem-solving.
Networking can be simple, it depends on the size of networks that you deal with, the number of nodes, types of physical transports, routing and security protocols.
Programming, what part do you find difficult?
Programming is a much broader subject, however, you don't need to know all of it. Just focus on the set of skills required for your job.
Don't aim towards mastering either of these fields, because there is too much to learn to ever master them. However, both fields are so broad that if you find yourself bored in one sector, give a different aspect of the field a try.
To actually give you an answer to your question, I think networking may be more difficult to get going at first, because there is quite a bit of up front knowledge that you need to perform fundamental tasks. Once you have entered and practiced a bit, you'll start to rely more on your trouble-shooting skills to find and fix problems.
Programming is probably easier to enter. With as much sample code that exists on the Internet it's not difficult for many to fake it and get a program to appear to work, and yet not know why. To become a good programmer you're still going to develop some strong problem-solving/trouble-shooting skills to succeed.
Above all, look for something that you enjoy. You're less likely to succeed if you don't enjoy what you do.
|
|
|
|
|
Nothing is easy untill you are having knowledge about it. Networking, once you get enough knowledge will be easy for you too.
Favourite line: Throw me to them wolves and close the gate up. I am afraid of what will happen to them wolves - Eminem
~! Firewall !~
|
|
|
|
|
Setting up, configuring, securing, and maintaniing a large enterprise network is more difficult than software development.
|
|
|
|
|
PIEBALDconsult wrote: Setting up, configuring, securing, and maintaniing a large enterprise network is more difficult than software development.
So companies who have hundreds of developers and manage with say 5-10 IT professionals are doing it wrong then? Per what you said it would be more reasonable if there where hundreds of IT professionals and only 10 software developers.
|
|
|
|
|
Not necessarily; too many cooks spoil the infrastructure.
|
|
|
|
|
Amount of effort needed and difficulty are not really correlated at all. Software development companies hire lots of developers because they are producing the item that is being sold at the end, whereas network administration is an overhead that is to be minimised.
|
|
|
|
|
Finding errors in existing code is easier than finding errors in an existing network.
Defining a standard is easy for both, but enforcing, detecting, and correcting non-compliant parts of the network is difficult.
BobJanova wrote: Amount of effort needed ... hire lots of developers
I agree that throwing more bodies at the problem won't help, will probably make it worse, and may have been the initial cause. But the question says "just in terms of difficulty".
In fact, hiring more developers doesn't make the job easier either, at best it can only make meeting deadlines easier.
|
|
|
|
|
Setting up, configuring, securing, and maintaniing a large enterprise application is more difficult than networking.
Fixed it for you 
All things are relative.
|
|
|
|
|
You must be doing it wrong.
You've probably never worked on a large enterprise network -- where the number of servers, switches, routers, load balancers, etc. approaches a half million spread across a dozen data centers world-wide. The size and complexity of which is the culmination of mergers among several large enterprise networks with differing standards. My job for the last two years has involved using the available tools to gather, correlate, and aggregate whatever data we can get (and there's not nearly enough) to detect and predict potential problems. Fortunately I never have to enter a data center and actually trace cables. :shudder:
Software is easy, but all the applications are at the mercy of the hardware.
|
|
|
|
|
I'm just going to point out that, as I find it highly unlikely that you're configuring the network devices using bits, you are relying on soundly developed software to configure the network. Solarwinds, server OS, firewalls, VPNs, ASAs, crypto, switch OS, router OS; whatever you're touching is basically a chunk of silicon without effective software.
That being said, my apples are better than your oranges. Mainly because they're mine.
I would like to point out, though, that if you find software design and development to be easy, most likely you _are_ doing it wrong.
|
|
|
|
|
The software tools are good, the hardware tools are good, it's the wetware tools that are a mite problematic.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
