Timeline for My coworker is lying about the current state of his work
Current License: CC BY-SA 3.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2016 at 16:04 | vote | accept | XenoMind | ||
| Apr 29, 2016 at 20:59 | history | tweeted | twitter.com/StackWorkplace/status/726154012517646336 | ||
| Apr 29, 2016 at 14:20 | comment | added | keshlam | Actually, this is a great place to use BCC rather than CC. They don't need to know you've informed the manager; and they may respond better if they don't feel your indirectly attacking them. | |
| Apr 29, 2016 at 12:39 | history | reopened |
user8036 Dawny33 Chris E Old_Lamplighter David K |
||
| Apr 25, 2016 at 18:21 | comment | added | Dan | @Brandin It wouldn't even hurt to CC your manager especially if this person in on another team. Something like, "Person X, I tested it on my machine and it doesn't work. Here are the log files." | |
| S Apr 25, 2016 at 14:55 | review | Reopen votes | |||
| Apr 29, 2016 at 12:39 | |||||
| Apr 25, 2016 at 14:55 | history | closed |
gnat Alec Kent A. jimm101 IDrinkandIKnowThings |
Not suitable for this site | |
| S Apr 25, 2016 at 14:50 | history | edited | mcknz | CC BY-SA 3.0 |
Spelling and grammar changes to improve readability.
|
| S Apr 25, 2016 at 14:50 | history | suggested | Michael | CC BY-SA 3.0 |
Spelling and grammar changes to improve readability.
|
| Apr 25, 2016 at 14:30 | review | Suggested edits | |||
| S Apr 25, 2016 at 14:50 | |||||
| Apr 25, 2016 at 13:38 | comment | added | Dunk | This problem occurs way to often in the software world. What's the definition of "done". The thing that really sucks is that these people who have a very "loose" definition of "done" tend to be the ones that impress their managers the most. After all. they seem to always be "done" when their deadline is due. Never mind that their stuff doesn't work and they cause others to miss their deadlines. Since they have no ethics anyways, they have no problems pointing the finger in others' direction. | |
| Apr 25, 2016 at 11:48 | answer | added | DraxDomax | timeline score: 0 | |
| Apr 25, 2016 at 9:59 | review | Close votes | |||
| S Apr 25, 2016 at 14:55 | |||||
| Apr 25, 2016 at 9:59 | answer | added | Gediminas | timeline score: 28 | |
| Apr 25, 2016 at 9:40 | history | edited | paparazzo | CC BY-SA 3.0 |
deleted 1 character in body
|
| Apr 25, 2016 at 9:35 | comment | added | Lilienthal♦ | "and I have no idea how far he can go" I assume you just mean that his shoddy work can have a big impact on your part of the project? Or are you referring to intentional sabotage? | |
| Apr 25, 2016 at 9:02 | answer | added | Kilisi | timeline score: 47 | |
| Apr 25, 2016 at 8:59 | comment | added | XenoMind | @Brandin, this is definitely reasonable. | |
| Apr 25, 2016 at 8:26 | comment | added | Brandin | Normally when tests fail you should report it to the developer. "Hey, your tests are failing on my machine." Just start with that and see what happens before escalating things. And don't assume he's lying or "sabotaging" things. Even if you think this is the case, don't show it while you're communicating with him. | |
| Apr 25, 2016 at 8:21 | comment | added | XenoMind | @Brandin, impossible. If it didn't succeed - then it didn't. | |
| Apr 25, 2016 at 8:17 | comment | added | Brandin | Did you mention this to your coworker? Something like, "Hey, your tests are failing on my machine.". Maybe the 10 machines he tested on are configured one way, while your machine is configured another way. From your message it sounds like you may be jumping the gun with talk about lying, sabotaging your work, etc. | |
| Apr 25, 2016 at 8:13 | history | asked | XenoMind | CC BY-SA 3.0 |