Timeline for Avoiding "Smart Guy" Syndrome on Team Projects
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 19, 2011 at 2:09 | vote | accept | yurisich | ||
| Dec 19, 2011 at 2:09 | comment | added | yurisich | I like to think I'm learning as much, if not more, in the interpersonal side of software engineering. Regardless, I'll be satisfied knowing I made a difference someplace that needed it, plus...it's good practice. | |
| Dec 19, 2011 at 2:05 | comment | added | Kyle | If it's as bad as you say it is, its unusually bad and you should seek a graceful exit. Either way patience is your friend. Hopefully your career will be long... Don't stress out so much about the short term. Things usually work out. | |
| Dec 19, 2011 at 1:31 | comment | added | yurisich | Getting early victories is hard when your solution is hinging on "what could happen in the future". Now, when I identify these things, I keep notes on what I should expect, and just wait for it to break. Give myself a head start. | |
| Dec 18, 2011 at 16:44 | history | answered | Kyle | CC BY-SA 3.0 |