In soviet rus...
Personally, I thought the reasoning behind the opinion was fairly obvious. Our entire economy is based on it.
You create something, it's yours. You own it.
I would try linux again if they applications were there but they just arent. You can browse, IM etc... but I do more than that.
I felt this way until a year or so ago when i switched to Ubuntu and started using linux full-time. Turns out I've been able to find an app for almost everything I do, in the standard repositories, no less. The sole application I use that doesn't run on linux runs just fine under Wine.
In my experience, Linux is there.
Since 99% of home users don't understand what is going on, all it would mean is more computers would be going to the shop for simple cleanings.
You say that like it is the users fault, however, poor documentation and complex UI design (although completely off topic) is equally, if not more at fault..... Does a pilot ridicule you when you fly on his plane but don't understand the aerodynamics?
Port this analogy over to automobiles, rather than planes(a bit more appropriate, since you actually operate an automobile/PC, unlike a plane) and it actually supports the parent's statement. Unless it's something that I understand and can fix(out of gas, flat tire..etc), when my car doesn't work I take it to the shop.
How about starting with good, old-fashioned requirements gathering?
Talk to a few people for as many roles as you can determine. Find out what features your office currently uses, and prioritize and categorize them(must-haves, costly-to-lose, frivolous[quantified as much as possible]). Compare this to the equivalent(or NONequivalent OO features). This data will tell you exactly what to do.
Classic cost-benefit, imho. Use leg-work and good analysis to make the right recommendation, not buzzwords and advertising.
Once you make the right decision, selling it to the masses is easier than you think. It's those decisions that are made with no real research or for the wrong reasons that aren't accepted and blow up in your face.
I hadn't noticed til you mentioned it, but yes, I have not had to reboot my Linksys v6(running ddwrt) for at least 5 months, which is when I plugged it into my UPS. Nice!
Technical management is a little tricky, especially with experienced, high-caliber resources. You HAVE to understand current technology, and solid design and architecture principles or you'll either get run over or completely alienate them, neither of which is good for business. Luckily, it sounds like you have a good start, possessing a technical background. You don't have to continue to code, but should at least be able to converse. A large part of the value of technical management is to be able to communicate technical constraints and direction to the business AND vice versa.
PM is just PM...and is a given.
The first programming course really just serves 2 purposes.
1) Teach programming concepts...how to think like a programmer. If the course succeeds you'll come out of the course not with a command of a language ready to hit the job market and produce valuable work, but with an understanding of what a program is and in the right frame of mind to work into deeper technical concepts like data structures, programming paradigms, algorithms...etc. And,
2) Weed out those people who just aren't meant to program.
Those who have grown up programming are only taking the course for the credits(and perhaps can learn solid fundamentals if they've only "dabbled"). There is no happy medium that will challenge these people and provide maximum value for those who fall into category #1.
My pick would be C++. Steep-but-quick initial curve to help with weed out, straightforward enough to provide clear examples of basic concepts, and with enough growing room to transition directly into advanced concepts and OO. The drawback is that it's not instantly practical for a lot of real-world programming productivity, but IMO sets a great foundation. With a solid base, you can pick up the higher-level stuff much easier.
Slashdot Mirror
What is astonishing is that we were lucky enough to detect the first gamma ray busts...what are the odds of that?
In soviet rus... Personally, I thought the reasoning behind the opinion was fairly obvious. Our entire economy is based on it. You create something, it's yours. You own it.
I would try linux again if they applications were there but they just arent. You can browse, IM etc... but I do more than that.
I felt this way until a year or so ago when i switched to Ubuntu and started using linux full-time. Turns out I've been able to find an app for almost everything I do, in the standard repositories, no less. The sole application I use that doesn't run on linux runs just fine under Wine. In my experience, Linux is there.
troll
Your foresight is truly astounding.
Gah, are we gonna do this again?
Telcos and free market?
Since 99% of home users don't understand what is going on, all it would mean is more computers would be going to the shop for simple cleanings.
You say that like it is the users fault, however, poor documentation and complex UI design (although completely off topic) is equally, if not more at fault ..... Does a pilot ridicule you when you fly on his plane but don't understand the aerodynamics?
Port this analogy over to automobiles, rather than planes(a bit more appropriate, since you actually operate an automobile/PC, unlike a plane) and it actually supports the parent's statement. Unless it's something that I understand and can fix(out of gas, flat tire..etc), when my car doesn't work I take it to the shop.
What moral lessons are there to be learned? Don't hire hackers?
Surely I can't be the only one immensely impressed by the use of a hair-band nightclub show reference to support economic analysis? Good stuff.
Forget my aimpoint and NV gear...hook me up with the FLIR-enabled Ipod!
How about starting with good, old-fashioned requirements gathering?
Talk to a few people for as many roles as you can determine. Find out what features your office currently uses, and prioritize and categorize them(must-haves, costly-to-lose, frivolous[quantified as much as possible]). Compare this to the equivalent(or NONequivalent OO features). This data will tell you exactly what to do.
Classic cost-benefit, imho. Use leg-work and good analysis to make the right recommendation, not buzzwords and advertising.
Once you make the right decision, selling it to the masses is easier than you think. It's those decisions that are made with no real research or for the wrong reasons that aren't accepted and blow up in your face.
I hadn't noticed til you mentioned it, but yes, I have not had to reboot my Linksys v6(running ddwrt) for at least 5 months, which is when I plugged it into my UPS. Nice!
Technical management is a little tricky, especially with experienced, high-caliber resources. You HAVE to understand current technology, and solid design and architecture principles or you'll either get run over or completely alienate them, neither of which is good for business. Luckily, it sounds like you have a good start, possessing a technical background. You don't have to continue to code, but should at least be able to converse. A large part of the value of technical management is to be able to communicate technical constraints and direction to the business AND vice versa. PM is just PM...and is a given.
My dad is a huge EQ addict.
Is there something inherently wrong with this statement, or is it just me?
Why should the playing field be levelled?
The first programming course really just serves 2 purposes.
1) Teach programming concepts...how to think like a programmer. If the course succeeds you'll come out of the course not with a command of a language ready to hit the job market and produce valuable work, but with an understanding of what a program is and in the right frame of mind to work into deeper technical concepts like data structures, programming paradigms, algorithms...etc. And,
2) Weed out those people who just aren't meant to program.
Those who have grown up programming are only taking the course for the credits(and perhaps can learn solid fundamentals if they've only "dabbled"). There is no happy medium that will challenge these people and provide maximum value for those who fall into category #1.
My pick would be C++. Steep-but-quick initial curve to help with weed out, straightforward enough to provide clear examples of basic concepts, and with enough growing room to transition directly into advanced concepts and OO. The drawback is that it's not instantly practical for a lot of real-world programming productivity, but IMO sets a great foundation. With a solid base, you can pick up the higher-level stuff much easier.