The TPP is likely to export some of the worst features of U.S. copyright law to Pacific Rim countries: a broad ban on breaking digital locks on devices and creative works (even for legal purposes), a minimum copyright term of the lifetime of the creator plus seventy years (the current international norm is the lifetime plus fifty years), privatization of enforcement for copyright infringement, ruinous statutory damages with no proof of actual harm, and government seizures of computers and equipment involved in alleged infringement. Moreover, the TPP is worst than U.S. copyright rules: it does not export the many balances and exceptions that favor the public interest and act as safety valves in limiting rightsholders’ protection. Adding insult to injury, the TPP's temporary copies provision will likely create chilling effects on how people and companies behave online and their basic ability to use and create on the Web.
Our culture's default assumption is that everybody should always be striving for perfection -- settling for anything less is seen as a regrettable compromise. This is wrong in most software development situations: focus instead on keeping the software simple, just "good enough", launch it early, and iteratively improve, enhance, and re-factor it. This is how software success is achieved!
"Information radiator" is the generic term for any of a number of handwritten, drawn, printed or electronic displays which a team places in a highly visible location, so that all team members as well as passers-by can see the latest information at a glance: count of automated tests, velocity, incident reports, continuous integration status, and so on.
Also known as
a related term, nearly synonymous, is "Big Visible Chart"
Intensive use of information radiators conveys two messages in addition to the information itself:
the team has nothing to hide from its visitors (customers, stakeholders…)
the team has nothing to hide from itself: it acknowledges and confronts problems
The main benefit of the practice is therefore to promote responsibility among the team members. A secondary benefit is that information radiators tend to provoke conversation when outsiders visit, which can yield useful ideas.
1980s: the notion of "visual control" originating in the Toyota Production System is an anticipation of "information radiators"
1999: the term "Big Visible Chart" is coined by Kent Beck in "Extreme Programming Explained", though laterattributed by Beck to Martin Fowler
2001: the term "information radiator" is coined by Alistair Cockburn, part of an extended metaphor which equates the movement of information with the dispersion of heat and gas
Tomorrow is the funeral for Aaron Swartz, the programmer and sometime activist who killed himself last Friday, while facing federal trial. No one knows, or will ever really know, what caused Swartz to take his own life. But his suicide, in the face of possible bankruptcy and serious prison time, has created a moment of clarity. We can rightly judge a society by how it treats its eccentrics and deviant geniuses—and by that measure, we have utterly failed.
Programming is changing. The PC era is coming to an end, and software developers now work with an explosion of devices, job functions, and problems that need different approaches from the single machine era. In our age of exploding data, the ability to do some kind of programming is increasingly important to every job, and programming is no longer the sole preserve of an engineering priesthood.