Timeline for What should junior developer expect from their senior team lead
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2013 at 16:48 | vote | accept | Ravi Gadag | ||
| Feb 8, 2013 at 7:04 | vote | accept | Ravi Gadag | ||
| Feb 9, 2013 at 16:48 | |||||
| Feb 7, 2013 at 22:04 | comment | added | Steven Evers | @RaviG: Of course they're disinterested. You're a fresh new dev, eager to please, with eyes much bigger than your stomach... and you're trying to tell your devs what to do. It's bad enough when management has a new idea everyday for how to change the entire product... a new guy? pfft. Go do something. | |
| Feb 7, 2013 at 18:36 | comment | added | Ravi Gadag | They are disinterested. | |
| Feb 7, 2013 at 18:27 | comment | added | Erik Dietrich | It sounds to me as though your ideas would most likely be an improvement to what exists. Next up is to figure out why they're getting rejected. You haven't built enough rep with the seniors? They're lazy? Miscommunication? Could you be making a better case or could you get your way after proving yourself? If so, gutting it out might be a good experience. If they're just lazy and disinterested, it might not. | |
| Feb 7, 2013 at 17:48 | comment | added | Ravi Gadag | I showed a demo of all the new things. still they are uncomfortable. see my updated answer | |
| Feb 7, 2013 at 17:36 | history | answered | Erik Dietrich | CC BY-SA 3.0 |