3 ms·

What do you mean? I have delivered more than one feature in that timeframe. In fact one of them being a large one, and I got this one done in a day without know

by dviola 13y ago

What do you mean? I have delivered more than one feature in that timeframe. In fact one of them being a large one, and I got this one done in a day without knowing much of their codebase. Sure, it took me a week to deliver a small feature because I got stuck with a failing test and I didn't know their codebase that well. They also blamed me at the end for asking many questions. I think they thought I needed much help like it's a bad thing. The manager who fired me at the end also mentioned he had to fire someone else. Sure I could improve my knowledge too. I'm not claiming I have all the knowledge of the universe. Who does?

avenger123 13y ago
"They also blamed me at the end for asking many questions. I think they thought I needed much help like it's a bad thing." I am going to go with this statement you made. I've worked with a few people that are what I call "leeches" . I'll give you a quick story. I was on a project and this person comes by and asks how he can't figure something out. I walk through with him through the codebase and run through a debugger session and by the end he has his answer. Now, there was nothing that I did, that he couldn't do himself. He just wanted some kind of hand holding or didn't know how to dig to figure it out. It took about an hour and I charged the hour to another bucket. Not surprisingly, this person also didn't last too long and was let go from the project. He had other issues but this "leeching" definitely was a factor. So, obviously, only you know your situation and this may not be your case at all, but in any new position there is a fine line between "figure it out yourself" and hey I need help. I would say the first month of any job is a real hustle. You might be putting in 8 hours "on the clock" but maybe another two to three on your own. The ask too many questions is an indicator that those questions should have/could have been answered by yourself and you didn't take the initiative to figure it out. This is a fine line but the question you should ask yourself is - "If I spend another 2-3 hours reading the code base, googling, whatever" can I figure this out for myself. If the answer is likely then go for it. Figure it out. Those 2-3 hours will give you more insight into the code base and make you more comfortable with it. If you are hired as a junior there is a lot of leeway for that. If not, there isn't much. Once you've built your credibility this sometimes changes and you get more leeway but definitely not when you are starting out. I get that for some this might be the opposite, since the notion is that you're a new hire and they should "get you up and going" but they are not hiring experienced developers for their ability to ask questions that they can figure out themselves if they put some effort into it.
dviola 13y ago
I also wanted to say that I have worked with two Rails applications in that timeframe (2 weeks). One app being Rails 4 and the other Rails 3. I delivered more than one feature, not sure how many, maybe 3 or 4 features, without knowing the codebase at all, and the applications were government related applications, so they were large applications. I never worked with government applications before and that domain is new to me, I think I have a decent understanding of how Rails works so I'm not sure what the problem really was. They blamed me for asking questions, I did a bit of pairing with some members of their team. In the end, I was fired, and the excuse was that I wasn't productive, but how I'm going to be productive in a very short timeframe without them letting me learn about their application first? It's tough.
- BSousa 13y ago
  Look, I don't think the parent was attacking you directly, just explaining what may have happen from their perspective. Personally, unless you lied on the interview and were able to bullshit me into the job or you didn't shower, cursed every two minutes or made racists jokes/whatever, I would never fire anyone in the first 2 weeks. Having said that, no one here knows what happened except you and the company and Sam was providing some info of what may have happen from the employers perspective. The best thing for you to do is to take some time and think hard to see if there was something that you could have done for this not to happen. If so, learn and next time act on it, if you truly think that there wasn't much you could have done to change how this went, and the company is at fault, then don't stress about it. Go out, have a beer and you will find another job soon.

by dviola 13y ago

avenger123 13y ago

"They also blamed me at the end for asking many questions. I think they thought I needed much help like it's a bad thing." I am going to go with this statement you made. I've worked with a few people that are what I call "leeches" . I'll give you a quick story. I was on a project and this person comes by and asks how he can't figure something out. I walk through with him through the codebase and run through a debugger session and by the end he has his answer. Now, there was nothing that I did, that he couldn't do himself. He just wanted some kind of hand holding or didn't know how to dig to figure it out. It took about an hour and I charged the hour to another bucket. Not surprisingly, this person also didn't last too long and was let go from the project. He had other issues but this "leeching" definitely was a factor. So, obviously, only you know your situation and this may not be your case at all, but in any new position there is a fine line between "figure it out yourself" and hey I need help. I would say the first month of any job is a real hustle. You might be putting in 8 hours "on the clock" but maybe another two to three on your own. The ask too many questions is an indicator that those questions should have/could have been answered by yourself and you didn't take the initiative to figure it out. This is a fine line but the question you should ask yourself is - "If I spend another 2-3 hours reading the code base, googling, whatever" can I figure this out for myself. If the answer is likely then go for it. Figure it out. Those 2-3 hours will give you more insight into the code base and make you more comfortable with it. If you are hired as a junior there is a lot of leeway for that. If not, there isn't much. Once you've built your credibility this sometimes changes and you get more leeway but definitely not when you are starting out. I get that for some this might be the opposite, since the notion is that you're a new hire and they should "get you up and going" but they are not hiring experienced developers for their ability to ask questions that they can figure out themselves if they put some effort into it.

dviola 13y ago

I also wanted to say that I have worked with two Rails applications in that timeframe (2 weeks). One app being Rails 4 and the other Rails 3. I delivered more than one feature, not sure how many, maybe 3 or 4 features, without knowing the codebase at all, and the applications were government related applications, so they were large applications. I never worked with government applications before and that domain is new to me, I think I have a decent understanding of how Rails works so I'm not sure what the problem really was. They blamed me for asking questions, I did a bit of pairing with some members of their team. In the end, I was fired, and the excuse was that I wasn't productive, but how I'm going to be productive in a very short timeframe without them letting me learn about their application first? It's tough.

BSousa 13y ago
Look, I don't think the parent was attacking you directly, just explaining what may have happen from their perspective. Personally, unless you lied on the interview and were able to bullshit me into the job or you didn't shower, cursed every two minutes or made racists jokes/whatever, I would never fire anyone in the first 2 weeks. Having said that, no one here knows what happened except you and the company and Sam was providing some info of what may have happen from the employers perspective. The best thing for you to do is to take some time and think hard to see if there was something that you could have done for this not to happen. If so, learn and next time act on it, if you truly think that there wasn't much you could have done to change how this went, and the company is at fault, then don't stress about it. Go out, have a beer and you will find another job soon.