How to read Scala code with lots of implicits?
Consider the following code fragment (adapted from https://stackoverflow.com/a/12265946/1333025):
What is the best way to understand code in a project with null documentation?
It is our first game and we are a start-up. We had a programmer who suddenly is seeming to be a dead weight. Though we knew him personally we thought that he was as motivated as we are and hence I never looked for a code review or documentation. Now it seems that he is slacking a lot and we want him out.
Reasoning about complex programs
For programs that can be complex to run for some reason, e.g. taking a long time, are there methods to understand and even debug or at least have some knowledge about the bugs without having to actually run it and see the outputs? Of course it would involve reading the code, but in which way?
Reading assembly useful for insights when writing C/C++? [closed]
Closed 9 years ago.
Advice for volunteer developers learning large codebases [closed]
Closed 9 years ago.
Advice for volunteer developers learning large codebases [closed]
Closed 9 years ago.
Advice for volunteer developers learning large codebases [closed]
Closed 9 years ago.
Advice for volunteer developers learning large codebases [closed]
Closed 9 years ago.
Advice for volunteer developers learning large codebases [closed]
Closed 9 years ago.