The line between necessity to ask questions and annoy everyone with my frequent questions is how much you learn.
As a senior dev I can differentiate between
"they simply can't know the answer"
"they could know, but it's not mandatory"
"how often do they wan't to ask me the same thing"
"How does the companies API work" or "how do I set up a dev environment for this internal software I have to fix a bug for" are valid questions to ask, because there are often no docs for this internal stuff.
Also, the most important thing I learned as a junior dev was, how to get information before asking someone.
You have to decide when it's faster to ask someone and they explain it to you, so you can ask follow questions and when it's okay to read some things online about it.
"How do I use promises in JavaScript" may be a question you could ask or read online. Maybe there is a senior who has time to spare and can tell you how they work, you ask the follow up questions and get running in short time. Maybe everyone has work to do and since you're a cheap junior dev, nobody cares if you need to work an afternoon through a tutorial or something.
From junior devs I expect that they can at least start their computer alone and produce some kind of meaningful software in the language they were hired for ;) so questions about this may annoy people.
Also, if you ask the 10th time about things that you could have already written down the first time, I get annoyed, lol.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The line between necessity to ask questions and annoy everyone with my frequent questions is how much you learn.
As a senior dev I can differentiate between
"they simply can't know the answer"
"they could know, but it's not mandatory"
"how often do they wan't to ask me the same thing"
"How does the companies API work" or "how do I set up a dev environment for this internal software I have to fix a bug for" are valid questions to ask, because there are often no docs for this internal stuff.
Also, the most important thing I learned as a junior dev was, how to get information before asking someone.
You have to decide when it's faster to ask someone and they explain it to you, so you can ask follow questions and when it's okay to read some things online about it.
"How do I use promises in JavaScript" may be a question you could ask or read online. Maybe there is a senior who has time to spare and can tell you how they work, you ask the follow up questions and get running in short time. Maybe everyone has work to do and since you're a cheap junior dev, nobody cares if you need to work an afternoon through a tutorial or something.
From junior devs I expect that they can at least start their computer alone and produce some kind of meaningful software in the language they were hired for ;) so questions about this may annoy people.
Also, if you ask the 10th time about things that you could have already written down the first time, I get annoyed, lol.