Timeline for How do you tell if advice from a senior developer is bad?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4, 2014 at 16:22 | comment | added | Raydot | @DaveE I could have put that better..."In charge of mentoring" can mean any number of things but what the OP goes on to describe sounds like much more of a supervisory role and most of the answers seem to be talking about disagreeing with a supervisor and not a mentor. That's a distinction with a very real difference. So I'm wondering if maybe the OP has the two confused and if clearing up that confusion might help. | |
| Jun 4, 2014 at 15:37 | comment | added | DaveE | @Dave Kaye - the OP says specifically the senior developer is supposed to be mentoring him. This isn't about the general obligations of senior developers to their juniors but the apparent specific obligation of one senior developer to a junior. | |
| Jun 2, 2014 at 19:32 | comment | added | Raydot | @DaveE I don't think a senior necessarily has an obligation to be a mentor. If that's what you're looking for better straighten that out during the interview! | |
| May 24, 2011 at 18:35 | comment | added | Loki Astari | @Niphra: Possible. But without more exact information I am more inclined to believe that this is just a naive learner that knows less than he thinks. Most seniors actually know what they are doing (you don't become a senior engineer if you are stupid you go into management instead). | |
| May 24, 2011 at 7:55 | comment | added | DistantEcho | @Martin: Or the senior's advice was really bad. | |
| May 23, 2011 at 21:25 | comment | added | Kevin | @Daenyth: Oh yeah, the "I told you so" strategy is sure to win over support! Just kidding btw, I used to do that as a junior. I remember it not being appreciated. | |
| May 23, 2011 at 20:18 | history | made wiki | Post Made Community Wiki by Steven A. Lowe | ||
| May 23, 2011 at 18:20 | comment | added | Loki Astari | @DaveE: Sounds like they have already had the discussion and the OP just did not have enough context to currently understand the wisdom of the senior. Sometimes there is only so much you can explain the rest will need to come from experience. | |
| May 23, 2011 at 18:11 | comment | added | Daenyth | I'd also suggest that if/when you do follow his suggestions, keep a document of your concerns regarding the change -- if it breaks later on, you may be able to point to this to show that you predicted the error. | |
| May 23, 2011 at 17:23 | comment | added | maple_shaft♦ | +1 For "He is more on the for the success of the project than you are". How true it is. I know you junior developers don't appreciate how lucky you are to not have that kind of stress on you because I sure didn't when I was a junior developer. Now get off my lawn! | |
| May 23, 2011 at 17:09 | comment | added | DaveE | OP - you're both professionals, even if you have less experience, so have a professional discussion with him about the things you question. If he isn't willing to talk about the whys of his instructions, he isn't much of a mentor. | |
| May 23, 2011 at 17:01 | history | answered | jzd | CC BY-SA 3.0 |