Priority - how sensitive the profit is to changes in schedule.

Do we want to apply effort in testing (More time)? or Do we take the risk of rework (More Money)? 

To be able to compare we need to use the same unit of measure to take an informative and intelligent decision..... sometimes the Cost of Delay is so high that you must take the risk of rework. By understanding the cost of delay you are able to take and make the correct economic choices. You are able to prioritize because you know how sensitive the profit is to changes in features and schedule.

Don Reinertsen at GotoConference - The Tactical and Strategic Art of Economic Models. 

http://www.infoq.com/presentations/Economic-Models 

Some Key points in the presentation:

• We are ignorant about our economic models and unaware of our ignorance - we need to learn more to take better and faster decisions.
• If you ask people who can delay a product, what they think it would cost to our stakeholders if this product is delayed by sixty days? You would get 50:1 responses...... someone saying 1000 to someone saying 50000. The problem is that If you dont know the Cost of Delay, you would do different *choices* if you think the number is different.... 
• If everybody understand the cost of delay they can take and make the correct economic choices at all levels - not only product managers. 
• Priority - how sensitive the profit is to changes in schedule.

The Power of Curiosity and Inspiration

"One thing that you have to do well to succeed: Make every single detail perfect and limit the number of details." - Jack Dorsey, the creator of Twitter

5 minutes video by Jack Dorsey. A must see! Here are my notes:

 Why does Square call their product managers "Editors"? Editing Ideas: Select the Ideas; Avoid Flood of Ideas. 

 Pay attention in particular to:

1. Editing the team, Bring the best people in and edit away any negative elements.
2. Editing the communication: Internal - This is the vision, help set the priorities to do the right thing. External - the product, the story we are telling the world 
3. Editing the money - investing and revenue.

Clean Architecture.

Well last night I found out that the videos from NDC 2012 were available - I hate when this happen to me, especially late night. I couldn't resist and I saw a couple of presentations :D

Here is one from Uncle Bob. I strongly agree with the following quotes in his presentation:

 “an architect’s job is not making decisions, but delaying them as much as possible (ideally when we know more about the problem being solved)”

 “A good architect maximizes the number of decisions not made.” 

Robert C. Martin - Clean Architecture from NDCOslo on Vimeo.

 Enjoy

How can you create a computer program with no assignments....

How can you create a computer program with:

• No control Flow
• No assignment
• No Arrays
• No Strings
• No Numbers
• No Booleans

 This is what lambda calculus is about. The following presentations are the best explnations I've found about Lambda calculus. The first one is Jim Weirich explaining lambda calculus and Y-combinator using javascript.


Jim Weirich: Adventures in Functional Programming from Edge Case UK on Vimeo.

Jim will be presenting this talk in this year StrangeLoop conference. The second one is Tom Stuart presenting how he transform a Fizzbuzz program in ruby to a implementation using only procs. 

http://rubymanor.org/3/videos/programming_with_nothing/