The Choice
8 comments
As in any situation in life there is not a straight answer. There are pros and there cons in your situation.
I understand you are struggling because you are doing many things you are not confident with, this is a stressful and unpleasant sensation. We want to feel challenged in our responsibilities but also we what to be sure we can do i then.
I can understand that having someone senior to guide you and, why not say, to protect you, can bring you this security you need to feel comfortable with what you are doing. And to be sure you are learning things in the right way
On the other hand, in my opinion, in your actual situation you are going to develop an alert8ng mode in your brain. You are going to collect a giant amount of problems that are going to stick in your mind. They will be itching you strongly and when you finally will find the solution, either by your own or, in future situations, with someone senior you will collaborate with, you will be extremely attentive and the knowledge will be writing in your brain like in a rock.
Having someone to guide you will teach you how this person solves this problem, you will think this is the way and will give you small space to develop your own way to do it or at least to understand that there are always other ways.
The most important skill in our profession, i think, it is not too know the solutions to everything, but to develop a powerful problem solving skill
What I would do, and I did, would be to stay on this company for 1~2 years and then move to another team with senior people to mentor you. You will be in a privileged situation to really learn from this people.
PD: your English is good ;)
I understand you are struggling because you are doing many things you are not confident with, this is a stressful and unpleasant sensation. We want to feel challenged in our responsibilities but also we what to be sure we can do i then.
I can understand that having someone senior to guide you and, why not say, to protect you, can bring you this security you need to feel comfortable with what you are doing. And to be sure you are learning things in the right way
On the other hand, in my opinion, in your actual situation you are going to develop an alert8ng mode in your brain. You are going to collect a giant amount of problems that are going to stick in your mind. They will be itching you strongly and when you finally will find the solution, either by your own or, in future situations, with someone senior you will collaborate with, you will be extremely attentive and the knowledge will be writing in your brain like in a rock.
Having someone to guide you will teach you how this person solves this problem, you will think this is the way and will give you small space to develop your own way to do it or at least to understand that there are always other ways.
The most important skill in our profession, i think, it is not too know the solutions to everything, but to develop a powerful problem solving skill
What I would do, and I did, would be to stay on this company for 1~2 years and then move to another team with senior people to mentor you. You will be in a privileged situation to really learn from this people.
PD: your English is good ;)
Your answer describe well what I'm living. You understand so much my situation. Thank you for sharing this with me I did need it.
Yes indeed, I realized that one the most important skill in our profession is Problem solving.(if it is not the most important one). Being good at it, is the key, so in my case the lack of senior guide makes me take a lot of time to solve some problems and as in company with real customers this creates frustrations etc. I also had that objective of staying in the company for 2 years. That 2 years last so long from time time depending on projects I have. Being by my own, makes me realize also that I have to relearn many things seen, but the obstacle I face with that is that I don't aend anything I start, this may be a lack of discipline from me. But changing technologies from time to time is also a source of it.
PD: good to know my english can be understood, thank you.
Yes indeed, I realized that one the most important skill in our profession is Problem solving.(if it is not the most important one). Being good at it, is the key, so in my case the lack of senior guide makes me take a lot of time to solve some problems and as in company with real customers this creates frustrations etc. I also had that objective of staying in the company for 2 years. That 2 years last so long from time time depending on projects I have. Being by my own, makes me realize also that I have to relearn many things seen, but the obstacle I face with that is that I don't aend anything I start, this may be a lack of discipline from me. But changing technologies from time to time is also a source of it.
PD: good to know my english can be understood, thank you.
It's a good sign that you are working alone with success. You are autonomous, you can solve problems and learn by yourself, you are communicating with non-developers easily, and you are delivering value to the company. You're in the right path, congrats.
About your question, IMHO the first stages of the developer career should be in a team. Why? Because it's the easiest (and fastests) way to learn: from senior colleagues (or team leader if (s)he programs as well). Working with others can help you get what you need to learn, what you don't like about the profession, etc. Later, when you are a senior, you could work from home, or alone without much issues.
Once said that, if I were you, I'd stay one year in the company (because some non-sensical HR filters) and will start interviewing. Start taking interviews, but (and this is important) don't feel discouraged if you don't pass them. Most times you are not a good fit because a new candidate pops up, the position is removed, you don't "click" with HR, etc. IMO only 5-10% of the interviews are failed because of the candidate. Now, every interview you have you'll learn something about the company, the business and about yourself. Keep in mind that a job can take 20 interviews with different companies, so don't feel preassured (you have already a job), and take this as a little "adventure".
About your question, IMHO the first stages of the developer career should be in a team. Why? Because it's the easiest (and fastests) way to learn: from senior colleagues (or team leader if (s)he programs as well). Working with others can help you get what you need to learn, what you don't like about the profession, etc. Later, when you are a senior, you could work from home, or alone without much issues.
Once said that, if I were you, I'd stay one year in the company (because some non-sensical HR filters) and will start interviewing. Start taking interviews, but (and this is important) don't feel discouraged if you don't pass them. Most times you are not a good fit because a new candidate pops up, the position is removed, you don't "click" with HR, etc. IMO only 5-10% of the interviews are failed because of the candidate. Now, every interview you have you'll learn something about the company, the business and about yourself. Keep in mind that a job can take 20 interviews with different companies, so don't feel preassured (you have already a job), and take this as a little "adventure".
Thank you for precious answer.
There are serious disadvantages to this setup for the following reasons(some of which you have already identified):
1. Lack of mentors will be an issue.
2. "Jack of all trade, master of none" problem. This is not a problem at personal level. But this is a problem in an industry where recruitment happens for specific domain or language and not for versatility of engineers.
3. In this age, employees are treated as use-and-throw commodity. So not having a skillset that is transferable becomes a major issue if you had to all of a sudden look for a job.
The problem you have mentioned mostly appears in small contracting/consultancy companies that take projects of other companies.
Other issue to lookout for is not getting sucked into a project that uses some obscure technology that no one else uses e.g. having to work on some proprietary in-house developed language for all the projects.
I have seen all this happen at lot of software consultancy and contracting companies. The founders of these companies start pulling all sorts of project right left and center to make lot of money. But it is the emloyees whose careers are destroyed.
1. Lack of mentors will be an issue.
2. "Jack of all trade, master of none" problem. This is not a problem at personal level. But this is a problem in an industry where recruitment happens for specific domain or language and not for versatility of engineers.
3. In this age, employees are treated as use-and-throw commodity. So not having a skillset that is transferable becomes a major issue if you had to all of a sudden look for a job.
The problem you have mentioned mostly appears in small contracting/consultancy companies that take projects of other companies.
Other issue to lookout for is not getting sucked into a project that uses some obscure technology that no one else uses e.g. having to work on some proprietary in-house developed language for all the projects.
I have seen all this happen at lot of software consultancy and contracting companies. The founders of these companies start pulling all sorts of project right left and center to make lot of money. But it is the emloyees whose careers are destroyed.
I can identify most of what you are saying from my position.
The lack of mentorship is a big issue I recognize it. I have even tried to have remote ones but it's hard to maintain thoses relations.
Being a "Jack of all trade" is not even bad for companies but in the process of recruitment. A jack of all trade is not really trusted by companies. Companies prefer recruit you as an expert but work with you as a Jack that's kind a paradoxal.
Thank you for your answer.
The lack of mentorship is a big issue I recognize it. I have even tried to have remote ones but it's hard to maintain thoses relations.
Being a "Jack of all trade" is not even bad for companies but in the process of recruitment. A jack of all trade is not really trusted by companies. Companies prefer recruit you as an expert but work with you as a Jack that's kind a paradoxal.
Thank you for your answer.
It sounds like you're doing ok. I'm 9 years in and still have similar issues. I have come to hate my job, so I would be careful since you might be on a similar track.
"Since I've started I've been working with several programming languages dependng on customers proposals. I don't like that because I'm not being good at any of them."
My company does this to me all the time. I wish I could focus on one or two things and become a true expert.
"Since I've started I've been working with several programming languages dependng on customers proposals. I don't like that because I'm not being good at any of them."
My company does this to me all the time. I wish I could focus on one or two things and become a true expert.
Thank you for your answer.
I like the work environment, but my main problem is that I feel that I need a superior who knows well about programming and who can help me out when facing some bugs or critical questions. Since I've started I've been working with several programming languages dependng on customers proposals. I don't like that because I'm not being good at any of them. Because I don't have the time needed to learn that programminglanguage and all technologies around it. I don't know if I have to keep with the company or not. What are the advantages and the drawbacks of staying in this company. Sorry my bad english.