been workin on this thing for a while now. get down to near the end of this thing, and get a bomb dropped on us, where a basic assumption was proven 100% wrong. Whole project is now fucked
10/14/2009 7:35:48 PM
FUCKED
10/14/2009 7:36:08 PM
BOOHOOWELCOME TO LIFE
10/14/2009 7:36:26 PM
when life gives you lemonssay fuck the lemons and bailjust bail dude...bail
10/14/2009 7:38:34 PM
10/14/2009 7:38:49 PM
i feel your pain. mine is over now, but it's been MOTHERFUCKING PANTERA TIME for about 3 weeks straight. i turned my shit in with bloody knuckles today. RAHHHHHHHHHHHHHHHHHHHHHHH[Edited on October 14, 2009 at 7:40 PM. Reason : with pantera i can overcome anything]
10/14/2009 7:39:39 PM
^^ Naw. Take it out on the wood framed unusual box son.]
10/14/2009 7:39:59 PM
A BLOO BLOO BLOO
10/14/2009 7:40:01 PM
/hug
10/14/2009 7:42:06 PM
End hug son.End hug.
10/14/2009 7:42:59 PM
hey just wondering, i basically made the same thread and no one talked shit to me
10/14/2009 7:43:01 PM
ass out of you and me
10/14/2009 7:45:18 PM
10/14/2009 7:47:30 PM
if you assumeyou only make an assout of u and me
10/14/2009 7:49:29 PM
how clever of you
10/14/2009 7:59:19 PM
i always (and still do think) thought that was the stupidest shit evermakes an ass out of u and meno the fuck it doesn't, i took geometry in 9th grade and there is no fucking postulate or theorem to back that shit up, faggot
10/14/2009 8:02:12 PM
bend over and take it
10/14/2009 8:02:51 PM
it's not like this has been the best executed project ever. The requirements were never fully given, and any attempt on my part to say "hey, I need some requirements" was met with "fuck that, we write them down at the end anyway." But, the assumption that was made was so obvious that it wasn't even viewed as an assumption. No one even thought about it.
10/14/2009 8:17:25 PM
any large scale ($50million+) project with no formal and rigid functional requirements definition has no chance of being fully functional, on budget, and on time.hi, i'm a project manager.
10/14/2009 8:24:54 PM
oh, I know that. this was definitely below 50mil, though, lol
10/14/2009 8:26:27 PM
what you just realized its not incredibly easy for the poor to pull themselves up by their own bootstraps?
10/14/2009 8:26:38 PM
wat
10/14/2009 8:27:26 PM
^^wat?
10/14/2009 8:39:25 PM
^^^wat?
10/14/2009 8:44:57 PM
OKAY
10/14/2009 8:57:31 PM
That's part of my stimulus package so that you get to work harder and make more money.[Edited on October 14, 2009 at 9:48 PM. Reason : l]
10/14/2009 9:48:43 PM
so are you going to disclose this faulty assumption or what? my company is guilty of the same thing, but we just blame it on the reps or sales dept.
10/14/2009 10:54:02 PM
Section 1: IntroductionSection 2: Issues foundSection 3: AssumptionsSection 4: RisksSection 5: Actual Design starts
10/14/2009 11:07:42 PM
i'm all about tossing formal and rigid functional requirements definitions out the window
10/14/2009 11:09:46 PM
10/14/2009 11:10:17 PM
#agile 4 lyfe son
10/14/2009 11:11:55 PM
should have procrastinated
10/15/2009 2:57:30 AM
do you still get paid?
10/15/2009 3:19:07 AM
i'm sure he does. he kinda sounds like my coworker... i don't want this to come out wrong, because i really like the guy, even hang out with him outside work on occasion (anyone who knows me knows that if i dont like you, you'll see me as little as possible. hell, if i like you i hardly see you)anyways, my coworker... he FREAKS THE FUCK OUT over little stuff at work, like the big project we were working on for the past 2 months. every day he was going to the VP of our department and complaining that our task was impossible in the timeline. he started wanting to stay late every day, work saturdays, etc. i had to talk him down off the ledge many times... i was like "dude, look. we get paid to do what they say. we only have so much responsibility in this. just do what they say, even if you know its gonna blow up in our faces... cause its not gonna be us looking bad, cause we did what we were told"he finally chilled out, everything worked out fine, and i was actually able to skip work the day before it was due to put time toward my next project.unless you're a super high paid exec, just collect your paycheck and chill. no need to stress or whine over something you can't control thats what i learned over the past 2 months.
10/15/2009 7:27:31 AM
where's that pretentious dick and his "first world problems" post?
10/15/2009 9:17:10 AM
http://www.thewolfweb.com/message_topic.aspx?topic=572048
10/15/2009 9:18:13 AM
10/15/2009 9:20:40 AM
^^no, not the same person. that is the thread. I'm talking about the shitwad that always posts that phrase^lol [Edited on October 15, 2009 at 9:21 AM. Reason : .]
10/15/2009 9:21:06 AM
^^ yeah i just sent that around my group
10/15/2009 11:10:55 AM
i love that cartoon. "what the customer finally received"LOL
10/15/2009 12:07:57 PM
good cartoon, lol.
10/15/2009 1:35:28 PM
meh, I've pulled a couple things out of my ass and got this thing back on track. now we get to see if this will actually work, lol. I have my doubts
10/20/2009 9:43:59 PM
10/20/2009 9:50:07 PM
I just laughed for a good half minute at that picture up there ^. Definitely gonna send that around to the team tomorrow and some of our vendor's support guys too
10/20/2009 9:54:57 PM
^^ man... I worked with a group like that one time... It was freaking impossible to get anything done at all. Here's a newsflash - if you need me to spend the time to document everything you're supposed to do, then why don't I just F-ing do it myself? Once I've come up with all the specs, tradeoffs, process flow, and whatnot, I've already spent 90% of the energy involved anyway... That's why your lazy ass is (allegedly) working... to get this crap done.This shouldn't be taken as a diatribe against documentation or specifications, but when one engineer has to explain every freaking step and make all the trade-off decisions for ANOTHER engineer just to get a single design task done, then there's something wrong! And no, I'm not talking about a learning curve... These people had the skillset, they were just playing the kind of "change-order" hardball you describeThey were all salaried employees, but they had just recently been converted from a contracting group.... Worst experience of my life, it was. They had absolutely no sense of teamwork or pride in their work.[Edited on October 20, 2009 at 10:04 PM. Reason : s]
10/20/2009 10:00:52 PM
^what you described isn't a change order game; that sounds like a group that was trying to force you to take responsible charge for the project or was afraid that you wouldn't pay the bill.If you ever want to work for the military, you have to get comfortable with the change order game. you low bid a job with the assumption that it's going to get changed 27 times before it ever gets built, and then you take whatever else is left on the table through change orders.
10/20/2009 10:32:38 PM
nah... they were just stonewalling, sadly... They were actually responsible for one piece and we were responsible for another... And like I said, there was no bill for us to pay to them since we were both theoretically on the same design team...
10/20/2009 10:47:59 PM
^?xanother version:
10/20/2009 10:52:56 PM
set em up
10/20/2009 10:53:43 PM