bryanteagle6
Well-Known Member
Well then! Nothing like knowing the standards! Ha
- Example: In sorting out a DFAS issue (SGLI payments), I eventually spoke with someone who haD been there for 30+ years. The technical skills of this person were abysmal given the need. The person's predecessor (a 35 year DFAS employee) passed away and took all institutional knowledge to the grave (ie, the person did not document or write anything down because, you know, job security)
- Example: In sorting out a DFAS issue (SGLI payments), I eventually spoke with someone who haD been there for 30+ years. The technical skills of this person were abysmal given the need. The person's predecessor (a 35 year DFAS employee) passed away and took all institutional knowledge to the grave (ie, the person did not document or write anything down because, you know, job security)
People like this are called "information brokers" and intentionally do not document anything because they are either incompetent, or they think that by keeping all of the information that they are somehow protecting their jobs, or both.not Navy related, but my old boss did this same thing. After a unfortunate series of events (maybe it was fortunate because he was a jerk) he no longer is employed with the company and I was asked to step-in to his spot. Guess what was the first thing I did, document the crap out of everything.
Do you work for a large financial institution. This experience is eerily similar to what I dealt with when I worked for one in particular.He was in the same role for 20+ years and he was toxic, an outgoing coworker called him a cancer to the unit. Every person that has even worked with him has either quit or transferred internally. He was about a year away from retirement when he was given an early retirement. He had so many excuses as to why he didn't want things documented (Things change too often, you can't document every situation, regulators could find it and hold us accountable for not following the procedures to "T", etc). His attitude was definitely one of "I'm untouchable because no one has the experience that I do", well that all changed when his bad behavior irritated/triggered the wrong person. A few interviews with HR later and he was called into a meeting and never returned.
Navy IT has and always will suck. Several impediments:
- The GS and SES (PhD required... please...) pay scales suck, which makes it difficult to attract and to retain requisite talent
- What you end up with are a pool of people who have a CISSP or related, and very little work experience. Why? Because, all you need for many security/IT govvie jobs is a certification. And, what do these people do? They stay forever and stagnate because they are unemployable in the private sector
- You could literally be a goat herder with a clearance and get a govvie IT job if you have a CISSP
- Military owned and contractor operated networks and systems
- IT rate training sucks and does not teach people how to troubleshoot. Typical Navy issue of wanting to pump out more widgets: it just lowers the bar
- A multitude of ignorant, aging Navy civilians who are in the IT workforce who are not qualified
- Example: In sorting out a DFAS issue (SGLI payments), I eventually spoke with someone who haD been there for 30+ years. The technical skills of this person were abysmal given the need. The person's predecessor (a 35 year DFAS employee) passed away and took all institutional knowledge to the grave (ie, the person did not document or write anything down because, you know, job security)
I never actively discouraged any of my reservists from using Kelly Beamsley, even if it made me cringe to see people relying on it, but I did actively encourage using the official reserve homeport. I mean the one with the CAC login. I even printed out color screenshots with bright arrows pointing to the five or six most commonly used links, the URL in giant, easy-to-read letters, and posted the copies around our computer labs (might as well make it as easy as possible).The simple fact that a retired Navy reservist's link page remains the resource for much of the Navy Reserve to access Navy IT is a pathetically sad commentary on just how fucked up Navy IT is.
Do you work for a large financial institution. This experience is eerily similar to what I dealt with when I worked for one in particular.
Well it’s all gonna be moot when encrypted OWA gets deprecated and Big Navy IT gets caught with their collective dick in their hand. What do you mean the reservists can’t do evals now?words
That's... really impressive. FY19 AT waivers for all my friends!!Well it’s all gonna be moot when encrypted OWA gets deprecated and Big Navy IT gets caught with their collective dick in their hand. What do you mean the reservists can’t do evals now?
Not to mention someone had the genius idea to push an NROWS build, with no notice mind you, that REQUIRES the Sailor to update GTCC and passport info before the unit can push orders. Bringing N3 departments across the force (or at least the one I run) to a screeching halt until I can herd the cats to get their shit updated. Because that’s just an OK thing for me to need to do on top of the two DH hats I’m wearing and my civilian job . . . ?
Not to mention someone had the genius idea to push an NROWS build, with no notice mind you, that REQUIRES the Sailor to update GTCC and passport info before the unit can push orders. Bringing N3 departments across the force (or at least the one I run) to a screeching halt until I can herd the cats to get their shit updated. Because that’s just an OK thing for me to need to do on top of the two DH hats I’m wearing and my civilian job . . . ?