We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Keep It Local

Formal Metadata

Title
Keep It Local
Subtitle
Or: (part of) what "reasoning about your code" really means
Title of Series
Number of Parts
23
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Keep It Local by Chris Krycho What do Steve McConnell’s variable scoping guidelines in Code Complete 2, pure functional programming, the data ownership system in Rust, classical object-oriented programming, the actor model in Erlang, and autotracking in Glimmer all have in common? Every one of them is aiming at the same key ingredient of robust, reliable software: the ability to “reason about your code.” But what does that actually mean?