Totally agree with you!! Also, going a bit more into the technical side, I found really helpful to follow this learning path: 1) Learn about the products your team provides, how they provide value to the business, and which are the main features 2) Understand the key metrics 3) Learn about the services architecture, how the features fit into it, and why it was built that way 4) Deep dive into the code and learn how are the most critical features architected.
I am moving on from my current job and your videos are really helping understand the things that i didnt know before i start looking. I saw a job description the other day constantly talking about SOLID principles and immediately wondered wtf is that.
I usually build a dictionary of Words I don't understand that people are using. I usually tell people I am gonna ask dumb questions and let anyone ask me dumb questions so I become the guy they can ask when they are embarrassed, if i cant explain something it also shows me I dont understand something enough. ------------------------------------------------------------------------------- Technical things to understand From a QA side i usually understand the git strategy/environment structure/Pull request process/Ticket management in the SDLC
Yeah this is a great tip. It helps a lot to be the "dumbest person in the room". Simon Sinek has a video on that mentioning that many people estay with the doubts and gaps of knowledge because they are afraid of being embarrassed instead of asking the questions and learn. And good thing you also do it for others, that creates a safe space in the teams so people feel free to ask questions.
Great tips, I add the task that involve the informal ways to know the key persons in differents support areas, in order to improve you joining the software developer process.
very helpful advice for someone who just joined moved outside my home country and joined a new company. effectively, the way to cooperate is pretty different compared to my previous companies, and tech stacks & tools are more or less different, first months are good transitional periods for self-training not only technically, and functionally, but also culturally. BTW, for anyone, who wants to move to hong kong and work as a software engineer in a leading investment bank, please reply to me.
Totally agree with you!!
Also, going a bit more into the technical side, I found really helpful to follow this learning path:
1) Learn about the products your team provides, how they provide value to the business, and which are the main features
2) Understand the key metrics
3) Learn about the services architecture, how the features fit into it, and why it was built that way
4) Deep dive into the code and learn how are the most critical features architected.
Great tips!
Great tips. One more thing is to document what you have learnt.
Yep good tip. Also helps the next one joining in the team.
I am moving on from my current job and your videos are really helping understand the things that i didnt know before i start looking.
I saw a job description the other day constantly talking about SOLID principles and immediately wondered wtf is that.
Oh nice. Just in case I have a video on solid principles if you want to get a quick review :)
I usually build a dictionary of Words I don't understand that people are using.
I usually tell people I am gonna ask dumb questions and let anyone ask me dumb questions so I become the guy they can ask when they are embarrassed, if i cant explain something it also shows me I dont understand something enough.
-------------------------------------------------------------------------------
Technical things to understand
From a QA side i usually understand the git strategy/environment structure/Pull request process/Ticket management in the SDLC
Yeah this is a great tip. It helps a lot to be the "dumbest person in the room". Simon Sinek has a video on that mentioning that many people estay with the doubts and gaps of knowledge because they are afraid of being embarrassed instead of asking the questions and learn.
And good thing you also do it for others, that creates a safe space in the teams so people feel free to ask questions.
Great tips, I add the task that involve the informal ways to know the key persons in differents support areas, in order to improve you joining the software developer process.
Really good tip too!
Hey Cristian, very good advices, I agreed to everything - Saludos amigo!
Thank you! Saludos! :)
very helpful advice for someone who just joined moved outside my home country and joined a new company. effectively, the way to cooperate is pretty different compared to my previous companies, and tech stacks & tools are more or less different, first months are good transitional periods for self-training not only technically, and functionally, but also culturally. BTW, for anyone, who wants to move to hong kong and work as a software engineer in a leading investment bank, please reply to me.
Glad it was useful!
thanks, appreciate it
Thank you for a good tips!
You're welcome! Glad you enjoyed it!
This got me interested in joining a new team 😆😁
😂
Really nice, thank you!
Glad you enjoyed it!