site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
544
Share Topic
Post a:
Post a:
AuthorAll Replies


FormerSREmployee

@verizon.net

What Jan doesn't tell you

I am a former SR employee, and yes, former AOLer to boot. Granted, there were some bad hires brought in - both ex AOL and others, and the mistake was in trying to make the company behave like something other than a startup.

But what Jan fails to disclose is that the tech organization that he was part of was entirely dysfunctional. Jan behaved like a giant baby, refusing to even speak to people in other parts of the company that he felt were below him (like some in Network Operations). Instead of working to make it better, he hid in his office and whined and refused to play nice. The CTO was clueless - and delivered nothing of value in the time I was there, and did nothing to control the ridiculous destructive behavior (see above) that made his org so dysfunctional.

Unfortunately, there was some valuable technology talent (Jan for all his failings is pretty sharp after all), but the company got stuck between the cowboys, the big company execs and the spineless leaders like the CTO. And thus, nothing got done, no improvements were made, the money kept bleeding and everyone knows the result.

Lisa needs to shoulder some of the blame clearly - but there is planty to go around.

sruser

join:2005-04-21
Arlington, VA

Re: What FormerSREmployee doesn't tell you!

Wow of course someone from operations would post that one sided kind of comment. I see you guys finally learned how to use a computer. Well I wouldn't point the finger directly at Jan for being a baby, I mean if you guys knew what you were doing maybe it would have been easier to work with you. As far as communication goes, you guys lacked it just as much as our side did. Not to mention the fact that you yelled at our NOC when they called alerting you of possible network issues, so belittlement was on your team as well. The only difference is we didn't belittle our own team members. As far as improvements and such all were put on hold by, you guessed it, Lisa Hook. Speaking of Cowboys lets not fail to mention that "operations" decided to change the OS literally over night without even first testing it in Development, straight to production, wow yeah can't see why anyone would not talk to you guys. Not to mention the fact that everyone you hired always wanted to change the network instead of learning it first. The idea of the network was to keep it simple yet for some people they just couldn't grasp that concept unless they had something else more complicated in there. I always loved the comment after giving a network overview, "Nah it can't be that simple, is it?"

Oh and lets not forget that you also were the ones that spec'd the billing system, ordered the hardware for only the lab, and then a week before deployment of the billing system forgot that you didn't order staging and production hardware. Then the best part was setting up the machines out at equinix and not plugging it into a live socket. So the machine was not up for 4 days because no one checked the power. Oh, and I believe it was "Network Operations" that was supposed to maintain the data center information. The list goes on and on for you guys so I think you got mixed up when you were describing our department as dysfunctional because I would love to see your list of mishaps compared to ours. Logically before we released or updated packages we tested it in the lab so if it screwed up, no harm. Now I'm not pointing directly at you per say but just letting everyone know there is two sides to every story. I mean would you want to work with a group or individuals in a supposedly "operations" group whose eyes glazed over whenever you presented anything new?

I personally blame the management infrastructure for prohibiting the creativity and pioneering that most individuals had at SunRocket. I view my time there as a learning experience and I worked with a great group of people. While I was as SR I worked for both the Operations group and the Systems Architecture group. Total I was with the company 2 1/2 years.

B
Premium,MVM
join:2000-10-28

reply to FormerSREmployee

Re: What Jan doesn't tell you

said by FormerSREmployee :

Lisa needs to shoulder some of the blame clearly - but there is planty to go around.
Wrong. She shoulders all the blame. Jan didn't "play nice"? It was Lisa Hook's personal responsibility to know about it and address it. CTO clueless? Guess who's fault that is. Dysfunctional organization? Lisa Hook's fault, and Lisa Hook's job to repair.

Nope. If nothing else, you've further proved that the upcoming injuries or deaths of Sunrocket subscribers (due to missing E911) are on Lisa Hook's hands and hers alone. Shame on that evil greedy little woman.

--B
--
In a realm outside causality and function


WasNewUser

@mchsi.com

reply to FormerSREmployee
many problems with SR was due to the lack of communication and unwillingness to fix anything. everything was a non-issue.


Tuesday, 29-May 05:25:23 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics