Skip to main content
added 3 characters in body
Source Link
Nelson
  • 14.4k
  • 6
  • 37
  • 57

When you have an objective, you should define them.

What exactly does "handling large codebase" or "grasp the bigger picture of our software" even mean?

If you give actual concrete examples of failure, then we can dig into the specifics, but this is so vague as to be meaningless.

It may indicate that this is what your expectations are to deliverables when some of the unknowns are not appropriately assigned.

When you have objective, you should define them.

What exactly does "handling large codebase" or "grasp the bigger picture of our software" even mean?

If you give actual concrete examples of failure, then we can dig into the specifics, but this is so vague as to be meaningless.

It may indicate that this is what your expectations are to deliverables when some of the unknowns are not appropriately assigned.

When you have an objective, you should define them.

What exactly does "handling large codebase" or "grasp the bigger picture of our software" even mean?

If you give actual concrete examples of failure, then we can dig into the specifics, but this is so vague as to be meaningless.

It may indicate that this is what your expectations are to deliverables when some of the unknowns are not appropriately assigned.

Source Link
Nelson
  • 14.4k
  • 6
  • 37
  • 57

When you have objective, you should define them.

What exactly does "handling large codebase" or "grasp the bigger picture of our software" even mean?

If you give actual concrete examples of failure, then we can dig into the specifics, but this is so vague as to be meaningless.

It may indicate that this is what your expectations are to deliverables when some of the unknowns are not appropriately assigned.