Timeline for how to tell managers you've been given too much responsibility as a junior?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2016 at 13:12 | history | edited | Kilisi | CC BY-SA 3.0 |
Added a comment into the answer.
|
| Sep 12, 2016 at 10:40 | comment | added | Kilisi | It's easy to feel overwhelmed when you're new, cut the issues down to size and soldier through them is what worked for me. Don't be shy to ask the manager for help, but with specifics not generalisations. Document everything you do for reference and be thorough... don't let things go South, if you get stuck and really need an assist, don't sit on it, ask for help, solve that problem, move forwards to the next. | |
| Sep 12, 2016 at 10:35 | comment | added | Tfish | The Project itself is pretty big but just not as big as the previous one, I'm worried about the project as I've only been a junior for about 5 months and with no other supporting devs available to help out it's a bit too daunting. | |
| Sep 12, 2016 at 10:23 | history | edited | Kilisi | CC BY-SA 3.0 |
added 263 characters in body
|
| Sep 12, 2016 at 10:13 | history | edited | Kilisi | CC BY-SA 3.0 |
added 97 characters in body
|
| Sep 12, 2016 at 10:09 | comment | added | Charles Borg | Also remember the golden rule: Check, re-check and check again. As a junior developer you will be making mistakes. If you adobt the habit of checking your work three times before crying wolf you can step by step explain what you have done when pressed by the brass. | |
| Sep 12, 2016 at 10:06 | history | answered | Kilisi | CC BY-SA 3.0 |