Search Results for "add code"
Share April 26, 2010's comic on:
Dilbert says, "I cannot meet your arbitrary deadline, so the engineer's code requires me to kill myself with a lightsaber." Dilbert says, "But lightsabers haven't been invented yet. The best I can do is annoy myself with a flashlight." The Boss says, "Could you do this in the hall?" Dilbert says, "Annoyance before dishonor!"
Share April 29, 2010's comic on:
The Boss says, "How long will your project take if I add two people?" Dilbert says, "Add one month for training, one month for the extra complexity, and one month to deal with their drama." The Boss says, "But after all of that?" Dilbert says, "They'll be as useful as this meeting."
Share October 14, 2007's comic on:
Asok: I found a clever way to write my application code in one hour! "Normally this sort of thing would take weeks." "I assume my high level of efficiency will be recognized and rewarded." Alice: "Let me know how that works out for you." The Boss: "You did all of that in one hour?" Asok: "Yes. I did." The Boss: "From now on. I expect you to finish all of your projects in one hours." "Otherwise I'll assume you're ripping off the company." Asok: "You could have warned me." Alice: "That's not how experience works."
Share August 24, 2007's comic on:
Dilbert: "As you requested, I sorted the future product features into three priorities." "Let me know which group I should stop working on." Essential Critical Must-Have "This is the part where you pretend to add value."
Share November 08, 2007's comic on:
"I need a $1,600 handheld bar code scanner to finish my lab tests." "Okay. Apply for a capital budget variance, prepare an RFP, get three bids, form a team to evaluate the bids, then prepare a purchase order." "Never mind. I'll just learn how to read bar codes by sight." "Quitter."
Share November 26, 2007's comic on:
The Boss: We're going to try something called agile programming. "That means no more planning and no more documentation. Just start writing code and complaining." Wally: "I'm glad it has a name." The boos: "That was your training."
Share May 27, 2001's comic on:
Tags #recommend vendor, #internal debvelopers, #play out, #outside vendor, #clueless weasel, #begin work, #sign contract, #internal weasels complain, #use, #steaming mounds, #worthless code, #plan too much, #practiced yesterday
Dilbert stands before the Boss giving a presentation. Dilbert says, "...And that's why I recommend using this vendor." The Boss asks, "Why don't we use our internal developers?" Dilbert replies, "Let me explain how this will play out." Dilbert begins drawing a diagram on the board. Dilbert says, "Step One: We select an outside vendor because our internal developers are clueless weasels." Dilbert continues, "Step Two: We sign a contract and begin work." Dilbert says, "Step Three: Our internal weasels complain to our VP and she order us to use them." Dilbert continues drawing a complex diagram on the board. Dilbert says, "Step Four: The outside vendor sues us while our weasels grunt out steaming mounds of worthless code." Dilbert returns home to Dogbert. Dilbert asks Dogbert, "Do I plan too much?" Dogbert says, "Is this the conversation we practiced yesterday?"
Share June 22, 2013's comic on:
Wally: I'd love to help you, but I'm in the middle of defragging my disk drive. When that's done, my computer will be compiling code for a few hours. Dilbert: How's work? Wally: I hear bad things about it.
Share July 12, 2013's comic on:
Coworker: You attend all of my project meetings but you never add value. Wally: I'm more of a big idea guy-- a conceptualist, if you will. Coworker: Okay, what's your big idea? Wally: Okay, here's where my system breaks down.
Share September 21, 2013's comic on:
Dilbert: What's your take on code consistency versus best practices for legacy systems? Boss; I want all of that stuff and I want it now. Dilbert: When people ask what you do for a living, what the $%@* do you say?