This is one of the most short-sighted views I have ever seen. Yes every situation is not the same, but Skill gernerally equals time.
If the guy is better than you at something, then he most likely put alot more time into it than you. And yes this is what the game teaches. It also teaches groupwork, how to survive and be democratic in a group.
All of these things help you out in daily life, thought locking yourself in a room playing a game kinda defeats all that though wouldn't you think?
The concepts that the game teaches is not wrong though, and the writers opinion is that of a young high school kid with no expierience in life.
Go back to the direct model, bring back Waitt, and try to be cool again.
The stupidest thing I've ever seen is a company change thier name from cool to fucking lame. Biggest reason I wanted a "Gatway 2000" was because it sounded cool, sounds like a good computer, "Gateway" by itslef sounds lame and bland.
You start going proprietary parts, you sell in retail outlets, you join up with fucking e-machines, all that ruins your reputation as a good computer maker and just makes you king of the bargin bunch. Meaning you don't make no money but sell alot of computers alla COMPAQ.
REally sad to see this, I used to like Gateway 2000.
Every company and situation is different, there is no "one size fits all".
- Will standardizing on 1 language save your company time and money? Yes, probably, as long as the majority of your employees already are trained in the language.
- Will standardizing on 1 language safegaurd you from future pressures and shortcomings of that one language. No, of course not.
The bottom line I guess is what is best for your company and situation. If that 1 language can do what you need, and all you'll ever need and the majority of your employees know it anyway, then why not.
The problem I see here is the same problem many people in today's IT world has. Its that they value being comfortable and being stable today much much more than they do having stability, and a better paying job tommorow.
The smarter you are, the more expierience you have the more you are worth in the long run. If you do decide to stay at your current company the only valid reasons I could see would be because you like the company and think they will do better in the future OR your too old to move because of retirement issues.
Staying for reasons entirely of pay is one of the most short sighted things you could ever do unless of course your still making poverty level pay, which I don't think you are. From an employers point of view I'd say having an employee who comes to work for pay first is much less desireable than having an employee who comes to work because he loves his job.
In my opinion thought she's already proven that it wouldn't be worth training her because she's so quick to quit.
As an employer I'd only put extra effort into training someone I felt would stay for the long run. Not somebody who jumps ship when the going gets rough.
Use what other webdevs use statistics. You should always try and make sure your users can access your website, without users what sense is there to even bother making a website? Whatever the majority of your important users are currently using for software is what you should be coding your site for.
You could also analyse your visitors along with the statistics found here.
If you want speed speed speed, have many users, want hardware that lasts long and have multiple requests to your file server, and can afford it:
Go SCSI
If you want cheap speed, hardware that wont last long, and a small number of users and requests from the file server:
Go SATA
The biggest difference being cost. In other words if you can afford it go SCSI. If you can afford it then you'll finally understand the benefits of SCSI, because you'll see it with your own two eyes.
If you can't afford it then well..... you just answred your own question.
If you want speed speed speed, have many users, want hardware that lasts long and have multiple requests to your file server, and can afford it:
Go SCSI
If you want cheap speed, hardware that wont last long, and a small number of users and requests from the file server:
Go SATA
The biggest difference being cost. In other words if you can afford it go SCSI. If you can afford it then you'll finally understand the benefits of SCSI, because you'll see it with your own two eyes.
If you can't afford it then well..... you just answred your own question.
Any worker worth her weight in gold will make sure that she is the best at her job, and whatever she does. It is naive to think that ALL your training is the responsibility of your employer, by now you should have realized the nature of IT and how fast things change. You need to keep up with the pace or you'll be left behind.
If your actually of the prehistoric belief that everyone must teach you everything in life then be prepared for a life full of limitations, and missed opportunities. Because that simply is not how it is now.
The problem I think is how you were taught in college. What they should have taught you is how to "teach yourself". Because above all, that is what defines a "real" IT person vs. one who simply is waiting to be outsourced.
Slashdot Mirror
Wow, Nice, I never saw one so neat before!
What happens if I have to change 1 wire? I need to rewire the whole rack?
No wonder IT people are losing their jobs.
This is one of the most short-sighted views I have ever seen. Yes every situation is not the same, but Skill gernerally equals time.
If the guy is better than you at something, then he most likely put alot more time into it than you. And yes this is what the game teaches. It also teaches groupwork, how to survive and be democratic in a group.
All of these things help you out in daily life, thought locking yourself in a room playing a game kinda defeats all that though wouldn't you think?
The concepts that the game teaches is not wrong though, and the writers opinion is that of a young high school kid with no expierience in life.
Go back to the direct model, bring back Waitt, and try to be cool again.
The stupidest thing I've ever seen is a company change thier name from cool to fucking lame. Biggest reason I wanted a "Gatway 2000" was because it sounded cool, sounds like a good computer, "Gateway" by itslef sounds lame and bland.
You start going proprietary parts, you sell in retail outlets, you join up with fucking e-machines, all that ruins your reputation as a good computer maker and just makes you king of the bargin bunch. Meaning you don't make no money but sell alot of computers alla COMPAQ.
REally sad to see this, I used to like Gateway 2000.
Every company and situation is different, there is no "one size fits all".
- Will standardizing on 1 language save your company time and money? Yes, probably, as long as the majority of your employees already are trained in the language.
- Will standardizing on 1 language safegaurd you from future pressures and shortcomings of that one language. No, of course not.
The bottom line I guess is what is best for your company and situation. If that 1 language can do what you need, and all you'll ever need and the majority of your employees know it anyway, then why not.
The problem I see here is the same problem many people in today's IT world has. Its that they value being comfortable and being stable today much much more than they do having stability, and a better paying job tommorow.
The smarter you are, the more expierience you have the more you are worth in the long run. If you do decide to stay at your current company the only valid reasons I could see would be because you like the company and think they will do better in the future OR your too old to move because of retirement issues.
Staying for reasons entirely of pay is one of the most short sighted things you could ever do unless of course your still making poverty level pay, which I don't think you are. From an employers point of view I'd say having an employee who comes to work for pay first is much less desireable than having an employee who comes to work because he loves his job.
In my opinion thought she's already proven that it wouldn't be worth training her because she's so quick to quit.
As an employer I'd only put extra effort into training someone I felt would stay for the long run. Not somebody who jumps ship when the going gets rough.
Use what other webdevs use statistics. You should always try and make sure your users can access your website, without users what sense is there to even bother making a website? Whatever the majority of your important users are currently using for software is what you should be coding your site for.
m
You could also analyse your visitors along with the statistics found here.
http://www.upsdell.com/BrowserNews/stat_trends.ht
If you want speed speed speed, have many users, want hardware that lasts long and have multiple requests to your file server, and can afford it:
Go SCSI
If you want cheap speed, hardware that wont last long, and a small number of users and requests from the file server:
Go SATA
The biggest difference being cost. In other words if you can afford it go SCSI. If you can afford it then you'll finally understand the benefits of SCSI, because you'll see it with your own two eyes.
If you can't afford it then well..... you just answred your own question.
Damn formatting *&^^%$$
If you want speed speed speed, have many users, want hardware that lasts long and have multiple requests to your file server, and can afford it: Go SCSI If you want cheap speed, hardware that wont last long, and a small number of users and requests from the file server: Go SATA The biggest difference being cost. In other words if you can afford it go SCSI. If you can afford it then you'll finally understand the benefits of SCSI, because you'll see it with your own two eyes. If you can't afford it then well..... you just answred your own question.
Any worker worth her weight in gold will make sure that she is the best at her job, and whatever she does. It is naive to think that ALL your training is the responsibility of your employer, by now you should have realized the nature of IT and how fast things change. You need to keep up with the pace or you'll be left behind. If your actually of the prehistoric belief that everyone must teach you everything in life then be prepared for a life full of limitations, and missed opportunities. Because that simply is not how it is now. The problem I think is how you were taught in college. What they should have taught you is how to "teach yourself". Because above all, that is what defines a "real" IT person vs. one who simply is waiting to be outsourced.