Devs only please: Junior developer receiving no mentorship at job

[semtex]

Is this normal?

This is my first job. I'm a .net developer full stack. They hired me back in August knowing I'm a Java guy with no history of web development or .net but they tossed me into this huge project and it seems to be a sink or swim situation. Luckily I fit in very well socially and have a great work ethic and have contributed greatly where I've been able to, so I'm pretty sure they want to keep me.

Is this a normal situation? because I gotta admit I've been paranoid about getting axed since I'm not a .net wizard.

 

[69 others]

Is this normal?

This is my first job. I'm a .net developer full stack. They hired me back in August knowing I'm a Java guy with no history of web development or .net but they tossed me into this huge project and it seems to be a sink or swim situation. Luckily I fit in very well socially and have a great work ethic and have contributed greatly where I've been able to, so I'm pretty sure they want to keep me.

Is this a normal situation? because I gotta admit I've been paranoid about getting axed since I'm not a .net wizard.

situations like this are more common at places where either software development is not their core business so they don't really understand what it takes to successfully develop large projects (a good team) or they just don't want to invest in the resources to do so or the project is not that important so they hired someone to see if they could finish it or support it with the intention if they do let's keep them or if the don't fukk it. what type of place is it? do you have benchmarks? if you don't then sit down with whoever you report to and create some. how many people worked on this project before you? how many other developers work there? did they made it clear to you that you were going to be working with little or no support from other devs before you took the job?

the best thing to do like i said above is to sit down with whoever you report to or the stake holders in the project and hammer out some benchmarks like deadlines, features, bug to be fixed etc and go from there. if you don't already set up a repository for source control, a bug tracking and project tracking system like jirra where you can track bugs and requested feature request with the main stakeholders so everything is on front street.

also what type of project is it? if you know java then C# should not be a stretch. did you work on large projects before this or is this your first? this could be a good learning opportunity for you. as a developer do not attach yourself to a language or think about yourself as an "xyz developer".

 

[semtex]

situations like this are more common at places where either software development is not their core business so they don't really understand what it takes to successfully develop large projects (a good team) or they just don't want to invest in the resources to do so or the project is not that important so they hired someone to see if they could finish it or support it with the intention if they do let's keep them or if the don't fukk it. what type of place is it? do you have benchmarks? if you don't then sit down with whoever you report to and create some. how many people worked on this project before you? how many other developers work there? did they made it clear to you that you were going to be working with little or no support from other devs before you took the job?

the best thing to do like i said above is to sit down with whoever you report to or the stake holders in the project and hammer out some benchmarks like deadlines, features, bug to be fixed etc and go from there. if you don't already set up a repository for source control, a bug tracking and project tracking system like jirra where you can track bugs and requested feature request with the main stakeholders so everything is on front street.

also what type of project is it? if you know java then C# should not be a stretch. did you work on large projects before this or is this your first? this could be a good learning opportunity for you. as a developer do not attach yourself to a language or think about yourself as an "xyz developer".

It's a software company so everyone I work with is either dev or qa. And yeah we do agile dev in which the sprints are 2 weeks long. This is my first job so it's my first experience with a big enterprise level codebase. I'm taking as a learning experience but there was no formal training at all, no senior devs helping taking u under their wing or anything. It's not just about learning the language, it's learnjng the company's infrastructure and learning to do stuff within that context. Asp.net mvc encompasses much more than just C#

 

[69 others]

It's a software company so everyone I work with is either dev or qa. And yeah we do agile dev in which the sprints are 2 weeks long. This is my first job so it's my first experience with a big enterprise level codebase. I'm taking as a learning experience but there was no formal training at all, no senior devs helping taking u under their wing or anything. It's not just about learning the language, it's learnjng the company's infrastructure and learning to do stuff within that context. Asp.net mvc encompasses much more than just C#

so what do they expect from you what benchmarks you have to reach? do you have to do more maintenance or develop more new features? did they tell you you'll be on a team or by yourself from the start

 

[semtex]

so what do they expect from you what benchmarks you have to reach? do you have to do more maintenance or develop more new features? did they tell you you'll be on a team or by yourself from the start

We are on teams. I have a principal dev, senior dev, and mid level dev on my team. I've never heard the word benchmark there. When I first got there I worked bug fixes but now I'm beginning to actually add code.

 

[Chris.B]

Yes it's normal.

Good programmers "figure it out". If you succeed in this environment, you can make it any where

 

[69 others]

We are on teams. I have a principal dev, senior dev, and mid level dev on my team. I've never heard the word benchmark there. When I first got there I worked bug fixes but now I'm beginning to actually add code.

by benchmark i mean deadlines, feature and performance implementations, etc. someone is assigning you task right? then ask that person for feedback to see where you stand

 

[Data-Hawk]

LOL...Kind of normal.. I mean it shouldn't be that way. They kind of just threw me into the code base..


One of the reasons I started complaining about the lack of documentation.

 

[semtex]

by benchmark i mean deadlines, feature and performance implementations, etc. someone is assigning you task right? then ask that person for feedback to see where you stand

more or less. If sprint work isn't done by the end of the sprint then it gets added to the next sprint. We have priorities for each release. The more senior people worry about that type of stuff.