- Check the unit tests, they often contain some simplified example of how code is used.
- Check the database schema or something equivalent to it.
- Get a local version of the system running as early as possible. This way you can test the impact of small changes on the code base.
- At the beginning ask the code owners as many insightful questions about the code as you can.
The idea of Dijkstra’s algorithm is really easy. Suppose we drop a huge colony of ants onto the source node [math]u[/math] at time [math]0[/math]. They split off from there and follow all possible paths through the graph at a rate of one unit per second. Then the first ant who finds the target node [math]v[/math] will do so at time [math]d(u, v)[/math] seconds, where [math]d(u, v)[/math] is the shortest distance from [math]u[/math] to [math]v[/math]. How do we fi... (more) I've thought a lot about this very question: how should companies build native mobile apps? It's a very different problem than web development, where you can push code 24/7 and bugs are cheap to fix. On mobile, you've got one shot to get it right and make a great first impression.
(I'd probably augment this advice for larger teams, so apply this only to ... (more)