4 ms·

>Why should someone be able to become an expert in HTML but not, say, SQL? The more things you become expert at, the less deep your expertise can be. Some peo

>Why should someone be able to become an expert in HTML but not, say, SQL? The more things you become expert at, the less deep your expertise can be. Some people may have the talent to become extremely deep at html, css, javascript, react, sql, and whatever back end language and frameworks, all at the same time. Many won't.

BjoernKW 8y ago
That's true but then again you don't have to be a 100% expert in a particular area to be useful. 80% often is more than enough. The remaining 20% can be researched or compensated for by an IDE if need be. There's no need for example to know the complete JavaScript API by heart. That's what documentation and autocompletion are for. You just need to know where to look and have an understanding of how things work on a conceptual level.
- tracker1 8y ago
  I'd say even 50% with some firm conceptual understandings, and syntax for what you're working in/with. I don't consider myself an expert in React, but I'm more than sufficient with a relatively good understanding of concepts. Rarely do you really have to dig deep into event models, but when you do it helps to know conceptually. Beyond that, it's similar for the very back. When to lean towards a given database type or environment is helpful. It depends a lot on your needs and other specifics to a situation. I would say that a lot of higher level concepts and specific language syntax can help. I reach for map/reduce/forEach daily, as well as a ton of other things. Just knowing what's in the box can help a lot in a language... a given framework, meh, know enough to get things done and refactor/read a lot.
beatgammit 8y ago
I think it's less talent and more dedication. My coworkers are impressed when I'm able to help them on all parts of our stack, but it's really because of the extra time I spent over my career outside of work learning new things. From the start of college to about 4 years into my first developer job, I spent most of my free time building my experience. I'd experiment with new languages, build projects using different tech, etc, all to deepen my experience across the board. To summarize that with "talent" cheapens the work that has gone in to it, and I think most people who are in the same position would feel the same way. It's mostly about time invested, though aptitude certainly helps. Talent is learned and trained, not innate.
- h1d 8y ago
  This. You won't be much special if you stick to one side of the stack which will give you only average salaries. It's sad people get impressed when you can just program and handle servers at the same time.

BjoernKW 8y ago

That's true but then again you don't have to be a 100% expert in a particular area to be useful. 80% often is more than enough. The remaining 20% can be researched or compensated for by an IDE if need be. There's no need for example to know the complete JavaScript API by heart. That's what documentation and autocompletion are for. You just need to know where to look and have an understanding of how things work on a conceptual level.

tracker1 8y ago
I'd say even 50% with some firm conceptual understandings, and syntax for what you're working in/with. I don't consider myself an expert in React, but I'm more than sufficient with a relatively good understanding of concepts. Rarely do you really have to dig deep into event models, but when you do it helps to know conceptually. Beyond that, it's similar for the very back. When to lean towards a given database type or environment is helpful. It depends a lot on your needs and other specifics to a situation. I would say that a lot of higher level concepts and specific language syntax can help. I reach for map/reduce/forEach daily, as well as a ton of other things. Just knowing what's in the box can help a lot in a language... a given framework, meh, know enough to get things done and refactor/read a lot.

beatgammit 8y ago

I think it's less talent and more dedication. My coworkers are impressed when I'm able to help them on all parts of our stack, but it's really because of the extra time I spent over my career outside of work learning new things. From the start of college to about 4 years into my first developer job, I spent most of my free time building my experience. I'd experiment with new languages, build projects using different tech, etc, all to deepen my experience across the board. To summarize that with "talent" cheapens the work that has gone in to it, and I think most people who are in the same position would feel the same way. It's mostly about time invested, though aptitude certainly helps. Talent is learned and trained, not innate.

h1d 8y ago
This. You won't be much special if you stick to one side of the stack which will give you only average salaries. It's sad people get impressed when you can just program and handle servers at the same time.