Slashdot Mirror
IT Training in the Military?
firehzd1 asks: "Yesterday's article about the new Czar of Security for the Department of Homeland Security raises a very important question, especially lately. What type of opportunities are there for IT work in the military/government. It seems every article I read is bashing the govt/military for terrible IT decisions/systems but I never hear the other side of the story. How bout we hear from those in the field that can give us a idea of what it is like behind the other side of the heavily armed gate?"
Hell I don't know a thing about the actual state of IT in the DoD, but I did sleep at a Holiday Inn Express lastnight.
From what I've read about system purchasing for the combat arms and aviation the following seems to be important to the DoD when it comes to computing technology.
1. Robustness is important
2. There is growing motivation to buy common systems for all the branches (including Coast Guard) rather than have many specialized systems.
3. Anything you sell the DoD today you have to support for at least 15 years, that includes CPUs like the PowerPC and IA. The new JSF, F-22 and Super Hornet are using Cat-5 and PowerPC chips (in the 132-400 MHz range IIRC) to power the flight computers and to connect systems and buses.
I think the move towards Microsoft isn't so much of a whoring out to MS, as it's a decision based on the fact that MS will be there in 15 years.
I was an electronics tech for the Navy. Did maintenance on comm gear and other electronic equipment. Went through a variety of schools. I feel the education is very good and the hands on experience is great. I worked with a variety of test equipment, receivers, transmitters, communication gear, etc.
When I was in, the most technologically advanced jobs were CTM (Crypto Tech Maintenance), ET (Electronics Tech), DS (Data Systems), among others (more specialized).
One individual I met while in was a Senior Chief ET at Treasure Island. As far as I know, he was one of the people to first develop laser listening devices for civilian purchase, or at least one of the first that I've heard of. I didn't see a working model, but he explained what it was and how it worked to me.
At yet another installation, I met a group of Navy Petty Officers and Air Force Sgt's that were developing a means to render video to CD, at the time, it wasn't common place (I hadn't even heard of the technology at the time) to find video on CD's.
There's many "cutting edge" tech gadgets being used in the .mil, of course these are the ones you never hear about until they're released to civilian use.
It's like the old story about the guy that invented the first "radar gun" for highway patrolmen, he also invented the first "radar detector" for civilians. :-)
Jerry Fletcher,
Privacy Protection By:
http://www.cotse.net/servicedetails.html
I did 4 years (95-99) in the USMC in an Information Systems Management Office (ISMO) before they started consolidating all the Communication Occupations with the Computer Operators.
Back then the ISMO was a new animal and they pulled officers from all the other fields to staff the place. They opened up the computer field and sorted out the recruits based on good math skills, and logic to fill those positions. The peons really knew what they were doing. We were technically proficient, even though the tech was obsolete. Back then there was no budget for this stuff and the brass though we should be fine with the desktops they bought 5 years ago.
What really drove military IT into the ground was that you were paying a low ranking private first class about $800 a month to do what equally skills civilians where doing in the real world for $50-75k.
Everyone I knew that had any competence would leave the service after their first 4 years, grabbing jobs with major Telcos, Fortune 500's. These corporations didn't even try to hide it. They would spam our office, send headhunters on base, and negotiate salaries with you in front of your staff officers.
The ones that couldn't get the civilian jobs, loved the corps like it was an Elvis fan club, or were too dumb to make it in the real world. They would re-enlist and eventually become your superiors. Still making dumb mistakes and still having a poor grasp of technology. And it killed all of us to know what had to be done, knew what was technically feasible and what wasn't, and you couldn't make any kind of statement or suggestion without someone saying it was insubordination!!!
I don't know how it is now, but my guess is that they are doing a little better. Sure the budgets are still getting cut, and you can't speak unless spoke to, but the brass is more tech savy now, and with the economy in the toilet, just have a job is a luxury. Having one that can't fire you or lay you off is where its at. Hell, I'm probably making as much as they are now with the paycuts I took.
Since you brought it up, I entered the Army Reserves with the MOS 74B (Information Systems Operator/Analyst). I wanted the job to help my resume while I get my B.S. in Computer Science. I'm the kind of person that I had never imagined myself in any form of the military. I went to basic training back in January 03, then went to AIT at Ft. Gordon in March up until July. Unfortunately, the 74B training in AIT was sadly lacking.
I'm sure anyone else here on slashdot would have agreed with me. In the exciting 74B school you will learn things such as installing Windows 2000 Professional and Server, adding users to the active directory, changing the background, etc., which lasts 2 weeks. You will repeat the same online quizzes over and over for two weeks while you cover A+ and N+. You will spend a week on the Unix command line, and a week on Solaris adding users and setting the time. You will learn about subnetting, configuring low-end Cisco switches and routers, and building a LAN. Oh, and then you'll learn Access 97.
The course was entirely geared for people with little or no computer experience. Some of the other trainees with me had CCNA's and MCSE's, yet no one was allowed to test out of any of the courses. Of course, the Army has needs for more than just installing windows and typing a few Unix commands, so we were always told that the "real learning" would occur during active duty, after AIT. I can't say what opportunities there are after AIT since I'm in the Reserves and choose to work in the civilian sector.
If you choose to go into this field, be aware that during the 4 months of AIT as a 74B (which I believe they are going to lengthen to 5 or 6 months) you will have little rights. If you're 17 or 35, you will lose a lot of things that you take for granted during your normal life. Despite being in the IT field, don't expect to have much access to Internet, or a computer for that matter. TV doesn't really exist, cars don't exist, cell phones exist 2 days a week (guess which ones).
Good luck to you if any of you choose this field in the Army. I was begging to go back to college by the time I got done with this course.
Here's the straight scoop from the USMC:
/26 net. Officers get an even more watered down course because they are also trying to soak in LF/HF/VHF/SAT radio principles and other management related skills. No background is considered whatsoever other than the math score on the ASVAB. You will often find officers with history degrees in charge of IT budgets.
Enlisted and Officers alike receive bare minimum training. The junior enlisted are divided into two pipelines, but mostly came from the old consolidated MOS of 4066 - Small Systems Computer Specialist (Name varies depending on who you talk to). Their course is about 2 months of learning how to install windows and other basic software, run basic network management tools, and generic introductions to major end uses of computers i.e. web, database, exchange, etc. They also receive a very quick course on the basics of networking with switches and routers, although most PFCs give you a blank stare if you ask for the Broadcast, Gateway, and IP range of a
The junior Marines get out into the Operating Forces and are promptly bombarded with distractions. Mess duty still exists in places, Camp services to keep the base clean, Camp guard, rifle range for two weeks a year, and a whole slew of minor classes, seminars, and stand downs that have no bearing on IT at all. Add in deployment time where they are stuck working a help desk, or worse, an admin related billet. Then add in weekends, holidays, and vacation time. We did the math out here in Japan where most single folks only stay for 1 year and out of 365 days, we only get 142 days of work out of someone. Unless they are spending their free time keeping up with the industry, they are rapidly growing into an NCO who knows just enough to bullshit his way past any problem, but not actually solve it.
Senior enlisted are even worse. The junior enlisted who are legitimate geeks almost always spend their 4 years focussing on their own education, often during work hours playing with production servers. After they have pissed everyone off by bringing the exchange server down once every other month, they have learned enough to get certified and get out for a "real job". This produces holes in the ranks which are often filled by senior enlisted from other job fields who have to find an open MOS, or get out. My last two comm chiefs were both infantry up to the rank of Sergeant. Of course a few good geeks who love being Marines stay around and generally become the Miracle workers of their commands, but for the most part, the quality of service garnered is grossly lacking. Hopefully, my description of the system is evidence that it is not the people's fault.
NMCI brings a small ray of hope in just getting a level of corporate knowledge. I don't know how many times I've called the server farm to hear, "Cpl Smith is the database guy, but He's on deployment until next month."
Here is an example of how the general level of inexperience hurts. The Blaster Virus attacks via DCOM RPC calls on port 135. The Base networking solution was to simply scan all computers for activity on that port and shut down any subnets that had activity. HELLO!!, port 135 is one of the key ports that NETBIOS communicates over which is a legitimate service. We've spent the past 3 days responding to reports that computer X has the virus only to find the machine clean. I haven't even begun to add up the lost man-hours as a result of NETWORK managers not understanding BASIC NETWORK protocols.
Don't even get me started on the complete lack of UNIX knowledge and support.
I could also rant on the officer side, but it boils down to the same thing....too many distractions to keep up with modern IT and not enough education/background to rapidly grasp the information. To a certain extent, the Marine Corps has hired civillians to manage the Enterprise and we do have one of the most stable and secure Nets in the DOD, but the system could be so much better if IT staffing was completely re-engineered.
The flip side of course, is that Network manager is capable of taking the network into a forward environment and competently defend it as a riflemen. The last time I saw members of the AF and Navy with guns, it scared me.
I've dirtied my hands writing poetry, for the sake of seduction; that is, for the sake of a useful cause. --Dostoevsky