3

I have finished my CS degree this year and got my first real job in IT, if you don’t count an internship and student jobs.

Since the beginning, I have been basically the only JS developer, responsible for the JS part of the projects.

I do manage to deliver but it is very stressful as I don’t have anybody to ask for help if I am stuck. I am also worried that by not having anybody to look at my code I might be picking up bad practices from the internet or overlooking some elegant solutions.

I am left to make choices and decision that I am afraid I am not qualified yet to make.

Am I crazy to think this is not a good place for a junior and this is not how it should be? I am thinking of looking for another job since I feel I might be wasting my time here but I am not sure whether this is a right thing to do. What do you, more experienced folks, think about this?

closed as off-topic by Mister Positive, gnat, DarkCygnus, Snow, Jim G. Nov 15 '17 at 7:12

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions asking for advice on a specific choice, such as what job to take or what skills to learn, are difficult to answer objectively and are rarely useful for anyone else. Instead of asking which decision to make, try asking how to make the decision, or for more specific details about one element of the decision. (More information)" – Mister Positive, gnat, DarkCygnus, Snow
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 4
    Don't quit and look for a new job. Find a new job that is more what you are looking for first, then quit. – Seth R Nov 8 '17 at 23:13
  • Sorry for the confusion, I did not mean I would quit before finding a new job. The point of the question is more whether it makes sense to look for a new job in a situation like this or am I blowing things out of proportion?( Will edit the question) – Kabachok Nov 8 '17 at 23:28
  • Have you mentioned your concerns to your manager? – Jane S Nov 8 '17 at 23:28
  • 1
    This is by no means a solution, more of a bandaid, but... If you have the time and desire: find a local JavaScript enthusiast group if there's one near you. You can bounce ideas off of some of the more senior members (here and there, not for everything), it's great networking and these groups can be a lot of fun. – silencedmessage Nov 9 '17 at 15:05
  • 1
    Even though you're the only JS dev, you can still have other people look at your code. Most juniors make mistakes in architecture. Isn't there anyone with solid CS knowledge that could help you in this area regardless of programming language. – user8365 Nov 10 '17 at 22:02
8

Am I crazy to think this is not a good place for a junior and this is not how it should be?

I don't think this is crazy at all and it's certainly worth some consideration. One of the main purposes a job should serve is to prepare you for your next job. If you don't think you're getting the right kind of experience to make you a better developer, you need to change that.

Before quitting, you should express your concerns to your manager. Tell them that, though you're able to make deadlines, you have doubts about the quality of your code. Ask if someone can review it and give you constructive feedback. If there truly is no one there with the ability to critique your work, this is a red flag. A much wiser person than me once said, "if you're the smartest person in the room, you're in the wrong room."

If you're unsatisfied with their response to your concerns, I would still recommend you consider sticking it out for a year. It will be much easier to find a new job once you hit the one-year mark and you will avoid having short-term employment on your resume that you will have to explain in future interviews. Since this is your first job, hiring managers may be willing to look past it, but as long as you're not completely miserable, it may be better to play it safe. In any case, make sure you find another job before you quit.

So what can you do in the meantime? Go to meetups, consider taking some MOOCs through Coursera or edX, maybe do some online coding challenges and learn from the feedback you get. There are some things that can only be learned on the job, but in the digital age, there are plenty of other ways to learn, especially when it comes to programming.

  • 2
    I would like to point out that this is great advice for any situation in which you are not satisfied about a particular aspect of your job: Don't quit immediately, try to find a solution, and have a good use of your time while your situation works itself out. If things really don't get better, leave. – everyone Nov 9 '17 at 13:24
3

As others have suggested, don't quit before having a new job in hand.

Beware though, you may just be having a rough time making the transition from school to the workplace. Almost any job you take will be asking for more initiative and independence then you may have had to demonstrate in school. You've just finished four years of advanced education in computer science. By this point you should be able to pick up JS on your own. It will be hard, and stressful, and you may have to seek out external resources to learn how to do it right, but lots of folks without a CS degree do teach themselves JS. Having a mentor always helps, but inevitably in your career you are going to reach the point where no mentor is available, and you have to trudge on anyway.

You know what's being asked of you and I don't. It may be that your employer's have unreasonable expectations. But consider treating it as a challenge, and don't let your fears undermine you. It's a cliche, but failure is a great instructor.

Not the answer you're looking for? Browse other questions tagged or ask your own question.