3 ms·
> On the other hand, as far as I see, I am supposed to know many of them. Why do you think of that? were you hired as the person that knows all of them? Remem
by kostarelo 6y ago
> On the other hand, as far as I see, I am supposed to know many of them.
Why do you think of that? were you hired as the person that knows all of them?
Remember that as software engineers, our job is to solve problems. It doesn't matter what technology, language, or framework as long as you bring value on the table.
The question is what is it that you want to learn? based on that you will figure out what you need to learn and how you will be providing value to future employers.
Personally, I'm heading for a senior position. As a senior (in my current company, may vary from company to company) is to enable others, unblock from potential issues and mentor them on best practices and core values. Based on that, I choose where to focus my learning and what to read/research next.
Of course, I am still a software engineer and still need to learn new technologies maybe or refresh my current knowledge. I do that by reading newsletters, blogs and spending time outside my working hours to those. I will choose to go deeper into a particular technology if I think that it will bring value to our current stack. That's not required though and you can demand from your employee to provide that time for you. I'm doing it because it's my choice to do so.
- roenxi 6y agoMmm. And in concrete terms; put about half your efforts into learning soft skills (problem identification, how to give feedback without putting noses out of joint, how to listen effectively). Mastering the black art of literally repeating what people say back to them is worth a bit more than any single technical skill.
- chrisbennet 6y ago"Mastering the black art of literally repeating what people say back to them is worth a bit more than any single technical skill." As someone with 35 years of experience, this is the voice of wisdom.
- atentaten 6y agoCan someone expand on this? What is the value of repeating what people say back to them? Is it to show them that you understand what they are saying, or is it to allow the person to think about what they just said so that they might reevaluate it?
- rahimnathwani 6y ago1. Show them you heard and understood. 2. Give them an opportunity to clarify if you didn't quite understand.
- erkanerol 6y ago> Why do you think of that? were you hired as the person that knows all of them? > Remember that as software engineers, our job is to solve problems. It doesn't matter what technology, language, or framework as long as you bring value on the table. What I observe in the industry is different. The market is so fierce and competitive and many companies (especially non-enterprise, medium-sized startups) are looking for people who perfectly fit their positions. Tools, domain, methodologies, etc.
- kostarelo 6y agooh yes of course my point wasn't that you could target companies with totally different requirements just because you think you can bring value. But it's exactly what you said: because the market is so competitive you are far likely to get a job even by just focusing on the technology you are really interested in.