Re: Merry Christmas!
Neko is back! Thank you ever so much! Now I can waste even more time on lockdown!
23 posts • joined 14 Jul 2015
A test of our capabilities is mandated by regulation on a somewhat scheduled basis. It is supposed to be a "surprise inspection", but somehow we always managed to know about when (down to the week) it was going to occur. We would then go to 12 hour shifts to prepare for the surprise inspection that was supposed to highlight our ability to execute the mission at a moments notice.
So there I was, in a meeting with management. We were about to start the extended work shift when I commented that we should just operate with that level of effort anyway because it *was* our job to be able to execute at a moments notice. Silence reigned.
I received a good heart to heart talk (his to mine, I was not required to respond nor was a response time offered, you know the drill) with the Chief later in private.
My workaround to that was to casually mention something like "Nice shoes", smile, and keep on walking. It drove some of them crazy trying to figure out if I was gay, a crossdresser, or something else entirely. A few actually unbent enough to be able to talk to because, well, positive, non-threatening comment and no leering followup.
So we know the orbital parameters of the sats. If you can, use a directional antenna to receive sat signals. Depending on antenna parameters (beamwidth), you can cut down on jamming signals by aiming for a cluster of sats. Lower flying jammers would have to be in the beam of the antenna to be effective. It isn't perfect, but with enough money, a defense contractor should be able to develop a beam steerable planar array that could track several sats at a time, and pick the signals that agree best with what is to be expected from the orbital parameters of the sats. Use that expensive CS clock on the ship to know the time, then pick the signals that match the expected time.
Let it be known that this is the first time that I know of that the use of a beam steerable antenna can be used to track multiple navsats for the determination of position during jamming was proposed. License fee is 10 million dollars for a perpetual, irrevocable license to the idea. You know where you can find me. I'm not greedy and I don't want to have to deal with license renewals.
Ah yes, year end spendout. I once spent a day with the organization finance guy waiting outside the budget committee door. They would pop out and ask the assembled masses if anyone had a, say, 10K purchase request. Those that had all the paperwork done got the money. We did out homework that year and got many goodies. Goodies we actually used mind you, but otherwise unobtainable under the normal budget process.
In a past job, I was a Senior Systems Engineer. Then at the next job became a Network Architect. Now in this job I'm a Technical Engineering Specialist. I consistently do more engineering style work as a TES that I ever did in prior jobs. Sometimes it is about job duties than job titles, but everyone judges on titles. I sometimes get the "so you got demoted" look when I talk about my past jobs. Funny, I make more now that I did in any before. Go ahead, demote me into a higher paying job, please!
Way back when I was in the military, if you bought a used car you took the risk that it may have at some point possibly been used to maybe transport a careless drug user who dropped a few seeds in the upholstery.
If you asked the base cop shop for a courtesy sniff by the drug dogs, you were routinely denied. If there by chance was a random seed or so subsequently found, you would kiss your current enlistment goodbye, and if a career person, stop that cold. Strict liability. In your car, you own it, it is yours, you did the crime, now do the time.
This created a brisk trade in used cars that were previously owned by military members of good standing as it constituted the best defense against those random seeds dropped by other possibly shady previous owners.
I well remember a conversation with a financial sector IT worker. We were upgrading the code on our Nexus 5k and his comment was along the lines of "we haven't gotten through testing the previous version yet". I asked how long it took them to go through acceptance testing and his answer was "about 3 years". When I asked why so long the response was "we like low risk upgrades where all possible failure modes are known and corrective measures tested and documented".
I worked for a military officer who rejected my letter to the commander because a word was misspelled. I asked for clarification because I had checked every word with the dictionary (this was before spell check software).
He told me the dictionary did not have that spelling. I asked to look at his dictionary. His was a Merriam-Webster Collegiate, mine was a Merriam-Webster Comprehensive. His dictionary didn't have my alternative spelling, so I obviously made a spelling mistake as his dictionary was the One True Source.
This was one case where size didn't matter as his was definitely smaller than mine.
Not much of an IT angle, but I worked for a cleaning company a long while back. A new guy was given the task of buffing the floors with one of those electric buffers. Gently lift the handle and the buffer (which had a big round motor driven buffing pad) and it swung one way, gently push down and it went the other way. Heavy bugger. If you weren't careful, you could really bang the walls. Yep, one wall was adjacent to the vault.
Police were not amused.
We had a network/server Lab/Stage area adjacent to the Data Center. Access to the DC was via a door to which the Architect level personnel had rights. The other side of said Lab was public space via a door to which network/server staff had rights. Very handy for moving configured gear from the staging process into the DC.
All was well until one Architect started to give tours of the DC via the lab because he didn't want to be bothered with signing in and out his guests via the Data Center Ops office.
They now have to trundle gear through the halls and offices to get it into the Data Center because the DC Ops Manager sealed the door due to said Architects antics.
A section of the raised floor is walled off so the IT department can have a decent lab (everything is tested in the lab before going into production. Everything.). Comes time to move in and we find the room full of boxes. It appears that the designated storage room (on a slab, shares office aircon) was deemed too small, so they took over the next largest space. The lab was built in the former storage area. After some heat related equipment failures, they finally relented and installed aircon. And overhead wiring trays and power runs. Everything the new storage room has in fact!
Users at a remote site were complaining a new application ran very slow, while all other users at the main site reported no problems. Latency was below 5ms and utilization below 40% on the WAN link.
It turned out that the desktops were configured at the main site and shipped to the remote site, so the fact that the application used a file share at the main site as a temp directory was never an issue. It worked fine if you were local, but your data took multiple hops across the WAN before you ever got to do anything with it, even then, it was still across the WAN.
Changed the temp dir to use one on the workstation and all was good.
Biting the hand that feeds IT © 1998–2020