I feel your pain. Still feeling it.
Also thought sr devs would help me solve install issue probs. But unless your explanation skills for debugging are good (so rare :( ), you just ish feel this way for your first (3-5!?) yrs of coding.
Still feeling it...
One way I've found that has proved helpful in situations like this is to try and create an "environment setup guide" as you go, so you can document your understanding of the setup process and ask for feedback as you get stuck.
This will also help future developers on your team that can now reference your document and update/fix it as they stumble across issues.
My team has even gone so far as to put those guides under source control so there's a history of edits. This way, if someone is confused by a step in the process, they can see who added/last changed it and can approach that person with their question.
I feel your pain. Still feeling it.
Also thought sr devs would help me solve install issue probs. But unless your explanation skills for debugging are good (so rare :( ), you just ish feel this way for your first (3-5!?) yrs of coding.
Still feeling it...
One way I've found that has proved helpful in situations like this is to try and create an "environment setup guide" as you go, so you can document your understanding of the setup process and ask for feedback as you get stuck.
This will also help future developers on your team that can now reference your document and update/fix it as they stumble across issues.
My team has even gone so far as to put those guides under source control so there's a history of edits. This way, if someone is confused by a step in the process, they can see who added/last changed it and can approach that person with their question.
Documentation + artifacts! Love it and will try.