Timeline for How to handle senior developer shirking his work and giving it to interns instead of doing it?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jul 28, 2017 at 15:16 | history | suggested | Dent7777 | CC BY-SA 3.0 |
Fixed spelling and redundancy issues
|
| Jul 28, 2017 at 15:01 | review | Suggested edits | |||
| S Jul 28, 2017 at 15:16 | |||||
| Jul 28, 2017 at 8:05 | comment | added | Lilienthal♦ | @LaconicDroid We can comment on his behaviour just fine, we just can't guess at his motivation in appearing to drop the ball. But that is in itself a major problem. It could very well be true that he's on a deadline and other stuff came up (unexpectedly). But it takes two minutes to say "I'm really sorry but I won't be able to give you the level of help I wanted due to [reasons]. Try to do X and Y and if you're stuck have a look at [resources] or consult A, B or C." There are any number of ways to handle such a situation professionally. Ghosting the interns is not one of them. | |
| Jul 28, 2017 at 2:10 | comment | added | StephenG - Help Ukraine | Keep records (e.g. of your commits and the sen. dev's emails to you ). Forward them to your own private email accounts. Just is case this all goes bad cover yourselves. I'd suggest an email reminding the senior dev that your manager told you to do other things instead of coding and that you can't do both. E.g. "In case you were not aware of this I should explain that ...". | |
| Jul 27, 2017 at 19:14 | comment | added | chucksmash | I understand why the Sr. Dev doing this would be very annoying to you in this situation. That said, it could also be the case that you as interns and his manager as an ostensibly non-technical employee are underestimating his ability to ramp up on unfamiliar code. From a personal perspective, there is no code I had the capacity to write five years ago that I wouldn't be able to quickly sight read today. He has ostensibly devoted significantly more of his lifetime brain cycles to the domain problems the company solves and the languages they solves it in after all. | |
| Jul 27, 2017 at 15:17 | comment | added | Monica Cellio | Suggested addition: as you wrap up on your last day or two, you'll naturally want to write a short report for your manager about your final tasks and where you've left things (especially as he's on vacation right now). This is the place where you describe the tasks you did and what remains to be done by others after you leave. If some of those were things someone else was supposed to be doing, the manager might investigate that later. | |
| Jul 27, 2017 at 13:53 | comment | added | motosubatsu♦ | @LaconicDroid I'm going off what the OP said "Our manager told him that starting to code on this project was his only work for the rest of our internship." but obviously there maybe things that the OP is unaware of - part of the reason why I suggest the "didn't get much chance you work with us while you were gone" approach if raising it with the manager. | |
| Jul 27, 2017 at 12:35 | comment | added | Laconic Droid | Or maybe he's doing coding on other projects elsewhere that have impending deadlines. Or maybe as the pieces of code he's delegating are "easy things" it wouldn't help him learn the code. There are too many unknowns here to comment on the senior dev's behaviour. | |
| Jul 27, 2017 at 11:56 | history | edited | motosubatsu♦ | CC BY-SA 3.0 |
added 12 characters in body
|
| Jul 27, 2017 at 11:53 | comment | added | Lilienthal♦ | "the senior dev is only punishing themselves since they will have to pick up an unfamilar codebase" - Not to mention the flak he'll probably get when the manager returns and discovers what's (not) been happening. | |
| Jul 27, 2017 at 10:20 | history | answered | motosubatsu♦ | CC BY-SA 3.0 |