cwinters + via:dancres 6
Wicked problem - Wikipedia, the free encyclopedia
february 2012 by cwinters
understanding this and following its immediate web could probably suck up a month or two of serious time: "Conklin identifies the following as defining characteristics of wicked problems: 1. The problem is not understood until after the formulation of a solution. 2. Wicked problems have no stopping rule. 3. Solutions to wicked problems are not right or wrong. 4. Every wicked problem is essentially novel and unique. 5. Every solution to a wicked problem is a 'one shot operation.' 6. Wicked problems have no given alternative solutions."
design
collaboration
management
complexity
chaos
change
planning
via:dancres
february 2012 by cwinters
Webinos Discovery Plugin
january 2012 by cwinters
"This is an early demo of enabling web page scripts to discover devices and services on local networks, Bluetooth and USB. For local networks, three different discovery protocols are supported: multicast DNS, SSDP and SLP."
browser
hardware
via:dancres
january 2012 by cwinters
Cloudname/cloudname - GitHub
january 2012 by cwinters
"Cloudname is a library for managing services in a distributed environment. It allows services to announce their presence and state, it allows clients to locate services and their endpoints and it provides a simple mechanism for distributing configuration to services...The current implementation uses Apache ZooKeeper to do the heavy lifting, but programmers should never have to deal directly with ZooKeeper -- only the library interface provided by Cloudname."
via:dancres
distributed
messaging
soa
configuration
deployment
january 2012 by cwinters
Ridiculously Transparent // ben's blog
september 2011 by cwinters
"The first couple of go rounds, there was dead silence. No questions—just head nodding and a couple of blank stares. After some probing, we realized that people needed to feel comfortable speaking up, that it didn’t just come naturally. We brainstormed a bunch of different ways to get over this hurdle and here were some experiments that ultimately worked...I thought we would surface creative answers faster. When everyone had a clear understanding of the hard problems, their collective brains were on the table for parallel processing. The best information rarely sat with the senior executives but with the employees that were closest to the product and closest to the customers. And the best answers would often come from the most unlikely of places."
management
behavior
collaboration
trust
transparency
via:dancres
september 2011 by cwinters
LittleProxy HTTP Proxy
december 2010 by cwinters
'LittleProxy is a high-performance HTTP proxy written in Java atop Trustin Lee's Netty framework. It's a side-project of LittleShoot and the Brave New Software Project. While many may still think of "high-performance" and "Java" as a contradiction in terms, the JVM has made astonishing strides over the years. That combined with Netty's use of event-based IO means that LittleProxy outperforms mod_proxy in every test we've ever run, beating it by as much as 83% on some tests using Apache Benchmark. LittleProxy is still a young project, but it works well.'
http
proxy
java
via:dancres
december 2010 by cwinters
http-twiddle.el
november 2009 by cwinters
"This is a program for testing hand-written HTTP requests. You write your request in an Emacs buffer (using http-twiddle-mode) and then press `C-c C-c' each time you want to try sending it to the server. This way you can interactively debug the requests. To change port or destination do `C-u C-c C-c'. "
http
emacs
via:dancres
november 2009 by cwinters
Copy this bookmark: