|
My dev environment has live links with database, app server, web context, auto-generated documentation, reference docs, class hierarchies, schemas, spell check, version history, build status, code coverage, style checking, integration and unit tests.
In comparison, code on paper (even fancy electronic paper) is 'dead'. The main things I'd be able to review in such a format - style and structure - are already fairly well covered by automated tools that keep a team of over eighty people 'singing from the same sheet'.
I'd still welcome a large format reader - my main reason for jumping into e-books was to reduce the number of two-inch thick reference books I accumulate each year - but the quality and complexity of navigation through code is not something I'd ever expect an e-reader to support.
|