"whenever someone tells you that few companies use or need real-time, they’re likely referring to settings where human decision-makers are in the loop (“human real-time”). That misses the mark because the true impact of these technologies will be in applications with no humans in the loop. As UC Berkeley Professor Joe Hellerstein noted a while back, 'real-time is for robots.'"
--
Month: October 2015
Adding CloudFlare CDN Services for Site
CloudFlare offers free CDN services including some basic SSL support. Switching over now that the most editing activity is in these Tech Notes posts.
Update: oops, forgot that the DNS needs to be changed, just as the doc says, but not done from provider's cPanel, so a bit of fooling around on the main account page.
O’Reilly: Field Guide to the Distributed Development Stack
Online document, sourced at GitHub for collaboration, on the emerging technologies associated with the "distributed development stack." Principal author is Andrew Odewahn, CTO at O'Reilly Media.
"The Guide is organized into buckets based on a general observation":
Gall’s Law: the Relationship of Simple to Complex Systems
a rule of thumb for systems design from Gall's book Systemantics: How Systems Really Work and How They Fail. It states:
A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system.
– John Gall (1975, p.71) Wikipedia
Technical Debt – References
Some references on technical debt.
- Martin Fowler 1 Oct 2003 post.
- Ward Cunningham
- The WyCash Portfolio Management System, 26 Mar 1992
- Debt Metaphor video, 14 Feb 2009
- Complexity as Debt wiki
- Alexander von Zitzewitz
- on complexity and architectural debt, Love Your Architecture, 3 Jun 2015
- Not all Technical Debt should be Treated Equally
- 18F - US Government Procurement Innovation
- Eric Ries
-
Machine Learning: The High Interest Credit Card of Technical Debt
- "...machine learning specific risk factors and design patterns to be avoided or refactored where possible. These include boundary erosion, entanglement, hidden feedback loops, undeclared consumers, data dependencies, changes in the external world, and a variety of system-level anti-patterns."
- Managed and Unmanaged Technical Debt
- Software Engineering Radio