I moved to a division that supports subsidiaries. So I also belong to other teams and perticipate in their project. Started in a new project from last month, then I thought what I should do in the circumstanse,
Comprehend the project entirely through “Good First Issue”
I think I fit to understand something through handling that, instead of reading documents. So I usually look for an easy task, or ask mentor or person in the project to assign that.
We can realize what we don’t understand. For example:
- Their using languages, libraries,,,etc
- Their external resource or system
- Development flow. In other words, what should I do for completing a task
- How to test (how does change effect to customers)
- Who should I ask for upon completing task (communication flow and who manages where)
- …etc
Continue handling tasks until we can familialize development flow
If there are ineffective jobs, we can change that and it would be better for the team. However, I think we cannot understand that as high-resolution if doing just once. Iteration let us know some thoughts. Is it certainly needed? how we can make it efficiently?
And also being loud without familiarizing might be bad from their perspective.
Eat lunch with colleagues
There are some commuting lovers unless it is fully-remote workplace. I believe that we may get many findings from casual communication. And also it is beneficial to good communication on the job.
On a new project, we are just newbies. So let’s be willing to learn.