Timeline for How to turn down a task I do not feel qualified for?
Current License: CC BY-SA 3.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 28, 2016 at 2:45 | history | tweeted | twitter.com/StackWorkplace/status/725516164722479104 | ||
Apr 27, 2016 at 18:23 | comment | added | Dan | Maybe it is understood that the topic isn't something everyone knows about. Maybe it is understood that your contributions to this is merely a base to work upon. By turning it down, maybe you'll never be asked to start on something. | |
Apr 27, 2016 at 9:17 | comment | added | Reaces | This actually feels very similar to a company I was in, who did something similar regularly. The main reason was because they wanted the newest / latest thing on their blog at all times. Yet did not want to devote senior company resources on it. The in-house presentations were often cancelled, or usurped by the owner talking about something completely unrelated. Unfortunately this also meant that in the end any argument against the presentation was ignored. As they knew that at the end of the day the presentation was likely dead in the water in advance. | |
Apr 27, 2016 at 9:10 | comment | added | Brandin | Regular code review is not "special care". | |
Apr 27, 2016 at 9:00 | answer | added | Lilienthal♦ | timeline score: 1 | |
Apr 26, 2016 at 23:18 | comment | added | Kilisi | Playing 'safe' and not wanting to take on responsibility is not a good look to the employer. give it your best shot. It's probably nowhere near as difficult as you think. It's just a matter of learning and applying knowledge and actually getting started. | |
Apr 26, 2016 at 21:22 | answer | added | agentroadkill | timeline score: 2 | |
Apr 26, 2016 at 20:53 | comment | added | Trainee | I was given one month and was encouraged to hurry up, as I might be allocated to some project soon (it wasn't specified if this might be topic-related). | |
Apr 26, 2016 at 20:46 | answer | added | user8365 | timeline score: 1 | |
Apr 26, 2016 at 20:46 | answer | added | AndreiROM | timeline score: 4 | |
Apr 26, 2016 at 20:44 | comment | added | agentroadkill | What's the time scale on this project? Is this your permanent job? Perhaps your manager has recognized a gap in his team and is attempting to fill it internally (you). If the company is giving you a year to learn best-practices when using BGP in embedded devices or TLS in a Java environment (can you tell I'm a network engineer?), I'd say it's in your interest to struggle through, so long as the work is interesting. | |
Apr 26, 2016 at 20:35 | review | First posts | |||
Apr 26, 2016 at 21:40 | |||||
Apr 26, 2016 at 20:29 | history | asked | Trainee | CC BY-SA 3.0 |