There's no testing when it comes to this. It's not actual code or books about it.did you test your changes before the "PR's"?
books too. they want to see initiative so the more you learn about a topic the better.
-
be careful. a stream of incorrect guesses is a good way to get a one way ticket out of there.
did you catalogue your changes before passing the ball back to whomever have you the task?
Like I said a few pages back how I'm working with backstage.io which is just a portal software for everything to be in one place ( like an appstore for the tools/documents/guides that specific company uses) and in order to register a component(project) on backstage , you have to create a .yaml file for it.
Then you fill that file with details about the projects , like the name of it, which team owns it , if it's an api or something else , if it's in production or development/expiremental stage.
You also have to give it the url where the repo is located , and other things. Something also about pagerduty and sentry.
I'm able to find all that information with no problem, but then it ask for other details like if the project consumes any api , or produces an api for a different project or if it depends on another project for it to work.
And the documentations don't provide that information, only someone that's work on that project or been with the company for a while.