|
Dan Neely wrote:
XmlReader inFile = new XmlTextReader(fs);
MyClass dataFromFile = (MyClass)Serializer.Deserialize(fs);
Maybe it wasn't as obvious as I thought in retrospect. The problem was these two lines. the XmlTextReader read the entire filestream when constructed so its index was at the end of the file when I tried deserializing from it instead of inFile. 
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
A brief moment of amusement... Working on getting an application server all installed and running for our group... Which of course involves going through dozens of people throughout the firm, and an e-mail thread that has actually crossed eight different cities in five countries on three continents. And I'm not exaggerating at all...
Now, we need admin access on the box, in order to run and maintain services... We go through the request process, it gets rejected, I think three times so far... Gets rejected again by someone suggesting we open an IT support ticket to explore alternatives...
So now we have an IT ticket entitled "Explore alternatives to admin access for installing application updates." Some IT guy on the other side of the country, after hearing our situation, replies... "A possible solution to this is to fill a server admin access request form and send it..."
So BASICALLY... Their "alternative to admin access" is to get admin access.
It boggles the mind, doesn't it?
|
|
|
|
|
Red Tape saves the nation!
|
|
|
|
|
Heh, no kidding...
I'm just waiting for the moment, after ANOTHER two months of e-mails crossing a few more countries, when they finally look up and say "You know, Ian, you were right all along."
See the problem with E-mails... With a face-to-face conversation, you can walk out and slam the door. With a phone conversation, you can angrily hang up... Over e-mail, all you can do is not respond... It doesn't have the same effect.
|
|
|
|
|
|
I wasn't snarling! I was in complete shock... I think I might be at the end of my rope... My actual reply to the e-mail was:
So... Let me get this straight... Your proposed "alternative to admin access" is to request admin access.
That's it... I'm stepping out of this conversation.
Wonder who will yell at me first.
|
|
|
|
|
Ian Shlasko wrote: wasn't snarling!
I would have been!
Did you know:
That by counting the rings on a tree trunk, you can tell how many other trees it has slept with.
|
|
|
|
|
Time to pick up the phone then, Ian  And then keep picking it up until what you want to get done gets done. That's the thing about corporate "environments"; nobody knows who works for whom or what level of authority they have, so you get this ass-covering mentality where the whole system stagnates into some eternal stalemate. Start pressuring people, especially late at night, though and you'd be surprised at how speedily things get resolved.
|
|
|
|
|
Heh... Nah, this has been going on since the beginning of April... Phone calls, e-mails, video conferences... Soon as we have it all worked out, someone else gets involved and stops it cold again.
So my new tactic is to keep all of the higher-ups well-informed, in the hopes that they'll eventually get so sick of hearing about it that they'll tell these people to just shut up and do it.
Basically, if this doesn't happen soon, I'll probably end up getting myself fired. At this point, I'm beyond caring.
|
|
|
|
|
All you have to do is copy the people that need to know on this message:
Due to circumstances beyond my sphere of influence (managers with agendas other than "getting the work done", namely protecting their turf), the "XYZ" project cannot be completed or delivered. The plain and simple fact is that I need to be able to do "this and that", but I need admin access (even if only temporarily) to complete the task. I've gone through proper channels several times in order to complete the task assigned to me, but I've encountered one roadblock after another. I am prepared to hand this task off to whatever "admin" you might suggest, and once handoff has been achieved, I consider myself to have successfully completed the task. Since I can't get the necessary permissions, I also cannot be expected to accept responsibility for maintenance issues regarding the application in question.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
Heh, if I was on a big development team, that might work... But I'm a front-office solo developer... Can't hand anything off to anyone.
They actually WANT me to go through "channels" any time I need to apply an update or bugfix to the software... But if something breaks down, I need to be able to apply a fix within minutes, not days. Can't seem to get the parent company (Which supplies our IT infrastructure) to understand that.
|
|
|
|
|
There is a logical and simple method for getting this fixed.
Next time you can, put out a bug that will in some obscure manner completely lock the system out of mission critical data. Have some easy to implement solution ready.
When all hell breaks loose, state, with absolute certainty, that you "have to have admin rights to the necessary servers, NAO!!!!"
Make sure the servers you want for this and any other such projects are in there.
Fix the issue, blame it on some "obscure hardware interaction with the language on the machine level" and state you couldn't test it in a comparable environment to the production systems because you spent the last 4 months trying to get access to those systems.
Then tell them in order to prevent the loss of a few million again, whatever bonehead has been blocking you needs to shut up and let you do the work.
Not that I'd do this in your shoes...
If I have accidentally said something witty, smart, or correct, it is purely by mistake and I apologize for it.
|
|
|
|
|
Evil, man... Pure evil
|
|
|
|
|
postulate 1: Suit wearing business units only respond to the loss or acquisition of capital.
postulate 2: Information technology directly influences the loss or acquisition of capital but does so in a mostly invisible manner.
postulate 3: Managers wish to please suit wearing units, while they do not understand the information technology aspect of capital acquisition or loss.
postulate 4: In order to please the suits, managers will attempt to stall anything that might cause disruption of capital acquisition.
hypothesis: If one makes the IT aspect of capital acquisition suddenly and violently visible in a negative meanner, any stalling caused by managers is withdrawn in order to please the business suits.
You need only experiment to test this hypothesis.
If I have accidentally said something witty, smart, or correct, it is purely by mistake and I apologize for it.
|
|
|
|
|
Except I'm in one of the suit-wearing business units, and I get paid slightly more if they do well
|
|
|
|
|
Happiness = pay+leisure+sex+toys/amountofworkneededtogetthem
Is being paid better enough to make up for the amount of work those managers are adding to the bottom?
Otherwise, a little bit of a reminder as to the state of the universe and their place in it is in order.
translation: convincing them to eff off and get out of your way might = happiness++
If I have accidentally said something witty, smart, or correct, it is purely by mistake and I apologize for it.
|
|
|
|
|
|
Really? C'mon - if you were going to quit you'd have done it before now. Start asserting yourself! Get your name known and get your name hated! It's a bloody liberating experience, that's for sure, and it gets stuff done!
Otherwise you're just going to repeat the same experience everywhere you go. Honestly, you will*. Read 'em the riot act in the martin_hughes style (swear a lot!) and you'll go far! Above all, remember that matey jim the CEO, his fiends and everyone else in his clique bleeds exactly the same way as everyone else who "happens", unfortunately, to be in the way of a swinging bat. There's nothing special about any of them.
*Unless you do the big time on SF authorship, that is
|
|
|
|
|
martin_hughes wrote: Unless you do the big time on SF authorship, that is
I'm hoping to manage that before the financial industry drives me sane
|
|
|
|
|
If there is one thing you should not have to worry about it is that the financial indusrty will drive anyone sane.
If I have accidentally said something witty, smart, or correct, it is purely by mistake and I apologize for it.
|
|
|
|
|
Except I'm already insane, so there's really only one direction left to go.
|
|
|
|
|
Ian Shlasko wrote: the financial industry
Say no more.
The only industry I have encountered whose inefficiency exceeds that of government.
Bob Emmett
CSS: I don't intend to be a technical writing, I intend to be a software engineer.
|
|
|
|
|
I sympathise greatly.
When Desklamps Attack [BOFH][^]
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
Why do programmers often confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
|
|
|
|
|
Haha, nice!
Ok, that just cheered me up
|
|
|
|
|
I have seen enough things like this to be virtually boggle-proof.
------------------------------------
I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
