4 ms·
Try to understand what your colleagues have done. This will help you get to really know the team culture. If you're a programmer, read through some parts of th
by ipiz0618 6y ago
Try to understand what your colleagues have done. This will help you get to really know the team culture.
If you're a programmer, read through some parts of the codebase, if possible, to get a sense of how your colleagues are doing their work.
- melvinroest 6y agoAs in just open random files and read? Or open up a UI and see what it does under a debugger? Or open up the test files first to see how things are supposed to be called/used? I wonder what your structure is.
- ipiz0618 6y agoIf the code base is huge, maybe just read some of the code your team has been writing (if you have a fixed team). Seeing how things are supposed to be called / used is also very important if you're collaborating with others on a project. Probably you'll find some internal libraries written by others useful. Maybe start with reading the parts related to what you expect to be doing? This of course comes after getting their consent.