• Referencing in advice to client. Good book.

    tags: cio

  • “Ideas are fragile. They often start powerless. They’re barely there, so easy to ignore or skip or miss.

    There are two things in this world that take no skill: 1. Spending other people’s money and 2. Dismissing an idea.

    Dismissing an idea is so easy because it doesn’t involve any work. You can scoff at it. You can ignore it. You can puff some smoke at it. That’s easy. The hard thing to do is protect it, think about it, let it marinate, explore it, riff on it, and try it. The right idea could start out life as the wrong idea.

    So next time you hear something, or someone, talk about an idea, pitch an idea, or suggest an idea, give it five minutes.”

    tags: ideas mentoring

  • Doodler vindication!

    “Studies show that sketching and doodling improve our comprehension — and our creative thinking. So why do we still feel embarrassed when we’re caught doodling in a meeting? Sunni Brown says: Doodlers, unite! She makes the case for unlocking your brain via pad and pen.”

    tags: TED creativity doodling

  • “Conway’s law is an adage named after computer programmer Melvin Conway, who introduced the idea in 1968:

    …organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.”

    tags: organization systems

  • Good self-made woman entrepreneur story: 

    “Sara Blakely is the youngest self-made woman to join this year’s billionaires’ club–turning $5,000 in savings into a new retail category”

    tags: forbes spanx

  • My latest on Active Information:

    “About a decade ago, I was working with my favorite co-conspirator on a universal task viewer service, which was an adjunct to our event-driven architecture. In order for something to appear in the task viewer, it had to be “trackable” (include the proper interface).
    Over the course of our design sessions, and throughout the next few months, we kept identifying business and system actions that should be trackable. It became apparent to us that nearly every business and system action could be trackable, following an interface pattern similar to making document objects printable.
    I hadn’t thought of “trackable” — and the running “hey that’s trackable” joke — in years. However, reading Counting Every Moment on self-tracking in the recent Economist Technology Quarterly bounced trackable up my memory stack.”

    tags: active-information self-tracking hpio

  • Jump to Kanban in Lean manufacturing distilled section

    tags: kanban agile

  • “The thing I’ve grown to dislike about Scrum are it’s time-boxed sprints.

    Working with startups, Scrum sprints are almost always way too long. When your sprints are too long then releases are infrequent (deferring revenue) and the team is forced to wait too long before being able to adapt to changing customer needs. This is wasteful because it means you’re continuing to move forward with outdated information.

    On the other hand, if sprints are too short, big features need to be arbitrarily chunked into smaller tasks, which aren’t useful to the customer on their own & can obfuscate what the team is trying to achieve”

    tags: agile scrum kanban

  • “People who think well, write well.”

    tags: writing ogilvy

  • “It astounds me how little senior management gets a basic truth: If clients don’t trust you they will eventually stop doing business with you. It doesn’t matter how smart you are.”

    tags: nytimes goldman leadership

Posted from Diigo. The rest of my favorite links are here.

Posted by brenda michelson at 7:30 am in links | Permalink | Comments(0)
| Trackback URL

Posted from Diigo. The rest of my favorite links are here.

Posted by brenda michelson at 6:31 am in links | Permalink | Comments(0)
| Trackback URL

  • This is very interesting. Amazon brings cross-border orchestration to cloud(s) and enterprises; and presumably between business partners. Use for scale, flexibility and potentially integration.

    “Amazon Web Services says its new Simple Workflow Service (SWS) will run applications that are distributed between customer sites and Amazon’s cloud infrastructure, further blurring the line between the customer’s data center and their chosen cloud.”

    tags: amazon workflow cloud computing SWS SQS

Posted from Diigo. The rest of my favorite links are here.

Posted by brenda michelson at 6:30 am in links | Permalink | Comments(0)
| Trackback URL

  • “Achieving continuous innovation, Hamel stresses, “lies outside the performance envelope of today’s bureaucracy-infused management practices.” It will require major changes in mind and heart. It will need, Hamel writes, new values, new processes for innovation, a greater adaptability, the infusion of passion in the workplace and a new belief system or ideology.”

    tags: Innovation Hamel

  • An excellent piece in the NYT on all things big data.

    “GOOD with numbers? Fascinated by data? The sound you hear is opportunity knocking…”

    tags: bigdata nytimes

  • “For years now, it has been self-evident to us at RedMonk that programming language usage and adoption has been fragmenting at an accelerating rate [coverage]. As traditional barriers to technology procurement have eroded [coverage], developers have been empowered to leverage the runtimes they chose rather than those that were chosen for them. This has led to a sea change in the programming language landscape, with traditional language choices increasingly competing for attention with newer, more dynamic competitors.

    The natural consequence of this tectonic shift has been uncertainty. Vendors for whom supporting Java and Microsoft based stacks was once sufficient are being forced to evaluate the array of alternatives in an effort to maximize their addressable audience. Platform-as-a-Service (PaaS) stacks like Cloud Foundry and OpenShift are perhaps the best example of this; the differentiation for each at launch was in part their support for multiple independent runtimes from JavaScript to Ruby.

    While the question is obvious – which languages should I support? – the answer, and mechanisms for determining an answer, have been considerably less so….”

    tags: programming language sogrady redmonk

Posted from Diigo. The rest of my favorite links are here.

Posted by brenda michelson at 6:31 am in links | Permalink | Comments(0)
| Trackback URL

  • Colin on the need to break free of batch based MapReduce: “All of these recent shifts from companies like Google, Yahoo, and others no longer see a competitive advantage in batch based MapReduce. The future has arrived, let’s look at some evidence…”

    tags: continuousquery mapreduce hadoop realtime

  • Excellent post / advice:

    “I follow a style of development that greatly reduces the risk of big projects like Storm. I call this style “suffering-oriented programming.” Suffering-oriented programming can be summarized like so: don’t build technology unless you feel the pain of not having it. It applies to the big, architectural decisions as well as the smaller everyday programming decisions. Suffering-oriented programming greatly reduces risk by ensuring that you’re always working on something important, and it ensures that you are well-versed in a problem space before attempting a large investment.

    I have a mantra for suffering-oriented programming: “First make it possible. Then make it beautiful. Then make it fast.”"

    tags: development storm pragmatism iteration

Posted from Diigo. The rest of my favorite links are here.

Posted by brenda michelson at 6:31 am in links | Permalink | Comments(0)
| Trackback URL

Posted from Diigo. The rest of my favorite links are here.

Posted by brenda michelson at 6:30 am in links | Permalink | Comments(0)
| Trackback URL