3 ms·

tl;dr — Pretend like it didn’t happen. The company failed you, not the other way around. Specifics: Unless you credibly represented yourself as someone who co

by csa 8y ago

tl;dr — Pretend like it didn’t happen. The company failed you, not the other way around. Specifics: Unless you credibly represented yourself as someone who could produce from “day 1” (figuratively), then you should probably still be in the training/development mode with a senior person giving you a significant amount of support and scaffolding. This sounds especially true since you say you had no experience with the stack. If they were giving you support, then the issue was most likely with your senior person rather than you. The only possible way that you failed was simply by not doing work by spending entire days procrastinating (note that most folks only have about 4 or 5 strong productive hours of thought work a day). If that’s the case, I recommend you read the book Getting Things Done. As others have mentioned, don’t even list in on your resume. Resumes have “relevant” experience, and it sounds like that company was irrelevant in terms of your development.

shoo 8y ago
> you should probably still be in the training/development mode with a senior person giving you a significant amount of support and scaffolding. This sounds especially true since you say you had no experience with the stack. If they were giving you support, then the issue was most likely with your senior person rather than you. i agree. Quoting the OP: > in which all employees work remote full-time, which I’ve since learned may not be the best situation for me this is a good observation. as a new grad i'd expect you to be able to ramp up slowly over a period of months if dropped into an existing team on an existing project with some experienced and capable devs you can learn from while working on initially relatively simple tasks like basic bug fixes or enhancements. there's a good chance you would find it much harder to ask for help (or have colleagues notice in passing that you are getting stuck with some inane idiosyncratic organisational or technical obstacle they can immediately help you with) if everyone is remote. you may get more mileage out of getting a junior job in a larger organisation that explicitly has some kind of well-defined and resourced training / development program for grads, if you can find such opportunities. small businesses tend to need you to start making them money right away (by billing you out to the clients or so on)

by csa 8y ago

shoo 8y ago

> you should probably still be in the training/development mode with a senior person giving you a significant amount of support and scaffolding. This sounds especially true since you say you had no experience with the stack. If they were giving you support, then the issue was most likely with your senior person rather than you. i agree. Quoting the OP: > in which all employees work remote full-time, which I’ve since learned may not be the best situation for me this is a good observation. as a new grad i'd expect you to be able to ramp up slowly over a period of months if dropped into an existing team on an existing project with some experienced and capable devs you can learn from while working on initially relatively simple tasks like basic bug fixes or enhancements. there's a good chance you would find it much harder to ask for help (or have colleagues notice in passing that you are getting stuck with some inane idiosyncratic organisational or technical obstacle they can immediately help you with) if everyone is remote. you may get more mileage out of getting a junior job in a larger organisation that explicitly has some kind of well-defined and resourced training / development program for grads, if you can find such opportunities. small businesses tend to need you to start making them money right away (by billing you out to the clients or so on)