Timeline for As a Junior Software Engineer should I say that something has been done wrong if I feel so?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2015 at 23:06 | comment | added | rob | I know the age of the code wasn't mentioned, but as a senior developer, I can tell you I would be embarrassed to look at my own code from 10+ years ago. If someone asked me to explain it, I'd probably also explain how it should have been done instead. I hope I'd also be open to learning something new if there's an even better way of doing it that I don't know about. | |
| Feb 7, 2012 at 15:34 | vote | accept | Why123 | ||
| Jan 29, 2012 at 16:05 | comment | added | Why123 | @jamesson no I didn't. And I did not post from my SE account either :). | |
| Jan 29, 2012 at 15:53 | comment | added | jamesson | In addition, I really hope you did not post from work. | |
| Jan 29, 2012 at 15:51 | comment | added | c_maker | And I would add: Listen to what they say and research whether their answers make sense. Look for cop out answers like "this is the way everyone does it" or "its working why change it" etc... if it seems like they do not give you actual technical reasons, that is a big problem. But first... Do not put them on the defensive by accusing them of something. I have made that mistake before and it is hard to repair. | |
| Jan 29, 2012 at 15:42 | history | answered | Bryan Oakley | CC BY-SA 3.0 |