What PL do not require a bunch of applications to get a job?

Question

Java

Hello!
Dear programmers, tell me which of the popular programming languages ​​and areas (hardware\web\desktop\mobile\etc) do not require knowledge of a bunch of additional technologies?
Let me explain with an example:
it is almost impossible for a PHP programmer to get a job knowing only PHP. It is often necessary to know HTML, JS, jQuery, layout, one of the PHP frameworks, MySQL, MSSQL.
Almost the same for a JS programmer - HTML, jQuery, AJAX, JSON, Node.js, layout.
Web designer - everything above, plus PhotoShop, SEO, SMM.
Of course, few people need a junior with knowledge of only the PL itself, but there are such programming languages, directions, technology stacks where you don’t need to be a master all-rounder, and the need for such programmers is no less?
Thanks a lot for the answers!

Answer 1

I will try to include philosophy, examples and "as if I were talking to you in a bar".
JAP is a tool. The tool always interacts with the object and with the environment. Accordingly, you definitely need to know something about the object and be able to use the tool inside the environment, and this will drag additional knowledge, let's call them "natural" dependencies. How deep do you need to know them? There is no answer here: as much as you need and want. It's about balance and emphasis. If there are no strict parameters at the level of the mind, you need to trust your intuition, because there is nothing else. For a JS programmer, JSON/jQuery/AJAX are natural dependencies and cannot be bypassed anyway. I give a tooth that the evening and a little Google will be enough for you to become almost LIKE A PRO in this. These are all data storage formats, or paradigms. It's like reading the composition of a chocolate bar in terms of complexity and entry threshold. Most likely, difficult words scare you.
This is about close and inevitable natural dependencies. But there are more distant, but nevertheless natural, knowledge of them allows you to develop, to have a more complete picture in your head. Here is a guitarist, he may just be a techie. There is a guitarist-musician who feels the Dorian way in the blues. And there is a guitarist-musician-sound engineer who finally understood how to mix guitars boldly and now in symbiosis with a sound engineer. Which of them is the coolest, obviously.
You can just type (html/css) and ignore programming altogether. But the natural environment resists: you are already (!) writing in a declarative language, it would be nice to learn more about this (about languages ​​​​or even about typing), especially since the most interesting js language is extremely close to you, and binding problems will instantly come out there html and js, different approaches to this, whole paradigms and frameworks; and now you have an interesting task of animating svg, you smoke a manual on the desired lib, read something about reflow / repaint, suddenly you learn something about selectors. And after some time, being the same layout designer, you see an architectural design flaw that fits very inconveniently into the technologies used, offer to fix it and save the team from a mess in a month, when some transition is superimposed on some position: fixed and the animation also falls in Safari, and only there, and here is a new one: "Redo, what the hell, the whole hat, so that it was ok." Something has changed in thinking and the picture has become more complete. SUDDENLY you are already an engineer, you can say, the salary is growing, everything is going on, the routine has become less.
So, about engineers. You can learn, for example, Python in a couple of days, there is also an excellent manual. But a real programmer is an engineer, because it's all about architecture, how objects/components interact, and how it all relates to the task. Which hammer to take, it does not matter how to read the composition on the bank. That is, the essence of your work lies precisely in the object and environment, and not in the tool. Figuratively speaking, when you are sitting in a cafe, the essence is not in a cup of tea, but in the atmosphere and how you feel in it, but at the same time, a cup of tea is needed to make you do something and thereby enter into interaction with the environment, so you have to learn how to drink tea beautifully.
Let me draw a line here: natural dependencies are the norm, but the essence is in engineering. You can move on dependencies further. You have an interval where there is a minimum threshold, below which it is impossible, and a maximum, where you are a "jack of all trades", which is also bad. You can move between the minimum and maximum threshold. Take the same networks: deploy the application, see the linux, set up the network. You can get a little confused and read about the basics of routing, literally 2 pm, you can also talk about the network stack in Linux, 2 more pm, and it will already be many times easier. In addition, the culture as a whole will increase, and if you are a back-end programmer, then it will be easier for you to interact with admins. About OSPF, obviously, it is not necessary to read, the balance is important. Balance is understanding
So, now we have natural dependencies, engineering and balance between thresholds. Not php/jquery/html/css.
It is also important to note that everything is developing very quickly now, and this is another argument that you should not become attached to the tool. Someone may say, they say, take the same js, programming on it is a whole paradigm, a different approach, its own features. This is true, but the point here is not in js, but in general in dynamic / interpreted languages.
By the way, with regard to SEO: from a technical point of view, these are a couple of manuals from Google and nothing more. There, SEOs can say a lot, you need to be more careful with them :)
And now, in fact, the conclusions:
1) There are a lot of cool jobs, you have to try. It is only necessary to distinguish close and necessary natural dependencies from a master of all trades. I believe that you need to work as a jack of all trades at least once, just to understand why this is bad. But there will always be dependencies, and this is the norm. You have listed too radically, of course.
2) You don’t need to cut yourself for a vacancy. You just need to go where it is interesting, always try to be an engineer and not kill the art in yourself (that is, not be afraid to do what seems right in order to either make sure you are right or make a mistake and become cooler).
3) No need to think in the style of "what if rubionrails collapses tomorrow, the community disperses, there will be no vacancies, what will I do." You are an engineer. You have experience in designing IT systems, it will not be difficult to switch to something related if it is clear that the technology is dying.
4) According to natural dependencies, you need to move as much as you are interested, you will only get better from this.
This is, of course, if you are really interested in all this. All these are areas very close to art, and here you need to love doing all this.

Answer 2

There is no such thing. Although ... in McDuck you can only know how the cash desk works. Although even there you have to know how to treat customers ...

Answer 3

Your question looks contradictory:
what kind of language is it if crowds of pros write in it, but there are no results of their activities in the form of frameworks / libraries?
True, I know one loophole:
you can get a job at a school (or even at an institute) to teach a language without knowing anything other than the syntax of this language.
But here you still need a diploma.
)))

Answer 4

Just advice.
Do not call yourself a programmer while you are confused by such questions. Any new technology takes 3-5 days to master before practical application, if you already have the appropriate baggage behind you.
Learn more. And keep in mind, in this work you have to learn constantly.

Answer 5

Each butt can be mastered quite easily. And in order not to grab your head later, you should learn butts as they come out and their relevance

Answer 6

Let me slightly rephrase your question: What car services do not require the ability to use a screwdriver to get a mechanic.

Answer 7

None