> For the complete documentation index, see [llms.txt](https://hanfak.gitbook.io/workspace/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hanfak.gitbook.io/workspace/career/junior.md).

# junior

* <https://jg.gg/2020/11/23/are-you-a-junior-developer/>
* <https://building.echo.co.uk/posts/on-being-a-junior-engineer/>

## tips

* <https://www.quora.com/What-are-the-common-mistakes-novice-software-engineers-do-that-should-easily-be-avoided-if-being-told-earlier>

### Things to deal with as a junior

* Here is a list of new things that new developers who work professionally for the first time, this leads to so much cognitive overload, so need to take it easy.

#### List

* Large codebases
* Test automation
* BAs, PMs, QAs, DBAs
* Estimating things you do not understand
* TDD for real
* testing pyramid
* Continuous Integration
* Merge hell
* git flow vs trunk based
* Bad code
* Bugs that cannot be fixed
* Big systems
* Legacy systems integration
* Misused technology
* Complex subject matter
* Insufficient permissions
* Unreasonable colleagues
* Misleading documentation
* Misleading dead code
* Unfamiliar tool chains
* Heavy management processes
* Deadlines
* Faulty APIs
* Vague bug reports
* Unreproducible bugs
* Micromanagement
* Unsatisfying work
* Code standards you disagree with
* Performance reviews


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hanfak.gitbook.io/workspace/career/junior.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.