The document discusses bringing people together in love and harmony. It calls for unity among all people, expressing themes of love, heart, togetherness, and thanking the Lord. It references children crying out and pleads for mercy for those less fortunate. Overall it promotes a message of oneness, compassion, and seeking spiritual fulfillment through community.
Knuth’s sentence "It was nice to learn Python; a nice afternoon" describes very well how easy it is to get engaged and fall in love with our favourite snake.
But if you are a professional programmer and use and abuse Python for paying your bills, there is a chance that your beloved pet will go out of control and bite you!
To save you some scars, I want to share with you 10 topical steps of my evolution from a Python programmer into a Python tamer.
Ten Commandments of Challenger Brands L:
Redefine the Category
Make a Powerful Statement
Assume Thought Leadership
Powerful Symbols & Metaphors
Big Bang News
Sacrifices & Choices
Out Maneuver
High Media Presence
Idea Centered
Mischievous Disruptions
Author: Anisha Motwani
Knuth’s sentence "It was nice to learn Python; a nice afternoon" describes very well how easy it is to get engaged and fall in love with our favourite snake.
But if you are a professional programmer and use and abuse Python for paying your bills, there is a chance that your beloved pet will go out of control and bite you!
To save you some scars, I want to share with you 10 topical steps of my evolution from a Python programmer into a Python tamer.
Ten Commandments of Challenger Brands L:
Redefine the Category
Make a Powerful Statement
Assume Thought Leadership
Powerful Symbols & Metaphors
Big Bang News
Sacrifices & Choices
Out Maneuver
High Media Presence
Idea Centered
Mischievous Disruptions
Author: Anisha Motwani
This presentation takes a look at the key forces that are leading to commoditization of brands. Various factors ranging from economic to consumer are at play. A lot of times, this commoditization is also the organizations and brands own doing. We then look at the ways in which brands can prevent this from happening and retain their diferentiation in today's hyper-competitive world.
Financial Planning for Youth
A simple, easy to understand guide for youngsters to learn how to manage their money and create wealth.
This presentation sheds light on the factors that are critical to a healthy financial management over one's lifetime. It will further take you through the fundamentals of planning - be it investment planning, risk management, tax and contingency planning or planning for your retirement.
In complex systems, the bottleneck of the performance is frequently not in the framework or in the programming language used, but in the connected interfaces themselves. The developer has only a small influence on the third party system performance. This talk gives ideas how to deal with this problem in an unconventional way.
There’s a huge disconnect between the business world and the engineering world that drives our software projects into the ground. We rewrite our software over and over again, not because we lack the engineering skills to build great software, but because we fail to communicate, make decisions in ignorance, and don’t adapt when our current strategy is obviously failing.
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the loss of productivity, the escalating costs and risks, and could steer our projects with a data-driven feedback loop?
Visibility changes everything. With visibility, we can bridge the gap between the business world and the engineering world, and get everyone pulling the same direction.
Find out how you can:
1. Identify the biggest causes of productivity loss on your software project
2. Translate the world of developer pain into explicit costs and risks
3. Collaborate with other industry professionals in the art of data-driven software mastery
Let's break down the challenges and learn our way to success, one small victory at a time.
Speaker: Janelle Klein
Janelle is a NFJS Tour Speaker and author of the book, Idea Flow: How to Measure the PAIN in Software Development: a modern strategy for systematically optimizing software productivity with a data-driven feedback loop.
For a number of years key global themes have emerged in UX:
UX Professionals are not feeling valued enough to be included in the upfront strategic product planning to help drive product success. A feeling sometimes described as ‘not invited’
The term UX is not always well understood organizationally or in the market place.
It’s hard to sell the ‘value of what we do’ with some people feeling forced to use reactionary methods to sell UX.
Limited time and opportunities, or a perceived lack of time to plan for UX ‘up front in product development’ can result in products that have no value when they reach the market place.
Why are product teams still jumping too quickly into development without allocating the necessary resources to question value?
This presentation will:
Guide people towards assessing, understanding and discovering value in order to make valuable stuff in the world.
Zero in sharply on the on the ‘analysis’ or ‘up front piece’ of product development i.e. at the strategy stage, when products are being planned.
Look at how to implement ‘value questions’ as part of product planning, so it will provide practical tips along the way.
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the loss of productivity, the escalating costs and risks, and could steer our projects with a data-driven feedback loop?
By measuring the friction in “Idea Flow”, the flow of ideas between the developer and the software, we can create a data-driven feedback loop for learning what works. Rather than making decisions based on anecdote and gut feel, we can start driving our improvement decisions with real data.
Data-Driven Software Mastery is about learning and improving faster than ever.
Find out how you can:
• Identify the biggest causes of productivity loss on your software project.
• Avoid spending tons of time solving the wrong problems
• Collaborate with other industry professionals in the art of data-driven software mastery
Idea Flow gives us a universal language for describing our experience, so we can share the patterns and principles of what works. With a feedback loop, we can run real experiments!
Idea Flow turns the development community into a scientific community.
Most of us started with patterns by Eric Evans and others. This helped us build models using Object Orientated Design and we have grown to appreciate the value of patterns such as Aggregate and Value Object. This talk looks forward and consists of various attempts to push our boundaries towards a more declarative way of domain modelling. We will look at a functional and logic based approach to design, where the statement of the requirement is the model itself. Apart from the variable choices in programming languages, the thinking tools that arise from this helps reduces the impedance between programmers and domain experts. The intention of this talk is to share, generate conversation so that we move forward as a community.
This presentation takes a look at the key forces that are leading to commoditization of brands. Various factors ranging from economic to consumer are at play. A lot of times, this commoditization is also the organizations and brands own doing. We then look at the ways in which brands can prevent this from happening and retain their diferentiation in today's hyper-competitive world.
Financial Planning for Youth
A simple, easy to understand guide for youngsters to learn how to manage their money and create wealth.
This presentation sheds light on the factors that are critical to a healthy financial management over one's lifetime. It will further take you through the fundamentals of planning - be it investment planning, risk management, tax and contingency planning or planning for your retirement.
In complex systems, the bottleneck of the performance is frequently not in the framework or in the programming language used, but in the connected interfaces themselves. The developer has only a small influence on the third party system performance. This talk gives ideas how to deal with this problem in an unconventional way.
There’s a huge disconnect between the business world and the engineering world that drives our software projects into the ground. We rewrite our software over and over again, not because we lack the engineering skills to build great software, but because we fail to communicate, make decisions in ignorance, and don’t adapt when our current strategy is obviously failing.
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the loss of productivity, the escalating costs and risks, and could steer our projects with a data-driven feedback loop?
Visibility changes everything. With visibility, we can bridge the gap between the business world and the engineering world, and get everyone pulling the same direction.
Find out how you can:
1. Identify the biggest causes of productivity loss on your software project
2. Translate the world of developer pain into explicit costs and risks
3. Collaborate with other industry professionals in the art of data-driven software mastery
Let's break down the challenges and learn our way to success, one small victory at a time.
Speaker: Janelle Klein
Janelle is a NFJS Tour Speaker and author of the book, Idea Flow: How to Measure the PAIN in Software Development: a modern strategy for systematically optimizing software productivity with a data-driven feedback loop.
For a number of years key global themes have emerged in UX:
UX Professionals are not feeling valued enough to be included in the upfront strategic product planning to help drive product success. A feeling sometimes described as ‘not invited’
The term UX is not always well understood organizationally or in the market place.
It’s hard to sell the ‘value of what we do’ with some people feeling forced to use reactionary methods to sell UX.
Limited time and opportunities, or a perceived lack of time to plan for UX ‘up front in product development’ can result in products that have no value when they reach the market place.
Why are product teams still jumping too quickly into development without allocating the necessary resources to question value?
This presentation will:
Guide people towards assessing, understanding and discovering value in order to make valuable stuff in the world.
Zero in sharply on the on the ‘analysis’ or ‘up front piece’ of product development i.e. at the strategy stage, when products are being planned.
Look at how to implement ‘value questions’ as part of product planning, so it will provide practical tips along the way.
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the loss of productivity, the escalating costs and risks, and could steer our projects with a data-driven feedback loop?
By measuring the friction in “Idea Flow”, the flow of ideas between the developer and the software, we can create a data-driven feedback loop for learning what works. Rather than making decisions based on anecdote and gut feel, we can start driving our improvement decisions with real data.
Data-Driven Software Mastery is about learning and improving faster than ever.
Find out how you can:
• Identify the biggest causes of productivity loss on your software project.
• Avoid spending tons of time solving the wrong problems
• Collaborate with other industry professionals in the art of data-driven software mastery
Idea Flow gives us a universal language for describing our experience, so we can share the patterns and principles of what works. With a feedback loop, we can run real experiments!
Idea Flow turns the development community into a scientific community.
Most of us started with patterns by Eric Evans and others. This helped us build models using Object Orientated Design and we have grown to appreciate the value of patterns such as Aggregate and Value Object. This talk looks forward and consists of various attempts to push our boundaries towards a more declarative way of domain modelling. We will look at a functional and logic based approach to design, where the statement of the requirement is the model itself. Apart from the variable choices in programming languages, the thinking tools that arise from this helps reduces the impedance between programmers and domain experts. The intention of this talk is to share, generate conversation so that we move forward as a community.
Put the key stakeholders in the same room with an unlimited modelling surface, and some tricks, and you'll end up not only with a viable model, but also with skeleton for continuous improvement.
To help us get our message across when sharing information its often helpful to think about data like its a gift. Gift giving provides us a context for "packaging" the data and thinking about our audiences, the recipients of the data.
1. Let’s ecommerce together
and feel Plone right
One Love! One Love! What about the one heart? Sayin': One Love!
One Heart! One Heart! What about the One Heart?
Let's get together and feel all right. What about? (One Heart! )
Hear the children cryin' Let's get together and feel all right What about the?
(One Love! ); As it was in the beginning Let's get together and feel all right.
Hear the children cryin' (One Love! ); I'm pleadin' to mankind!
(One Heart! ), So shall it be in the end (One Love! );
Sayin': give thanks and praise (One Heart! ), Oh, Lord!
To the Lord and I will feel all right; All right! (One Heart)
Sayin': let's get together Give thanks and praise to the Lord Wo-ooh!
And feel all right. And I will feel all right;
Wo wo-wo wo-wo! Let's get together Give thanks and praise to the Lord
And feel all right. And I will feel all right;
Let them all pass all their dirty One more thing! Let's get together and feel all right.
Remarks (One Love! ); Give thanks and praise to the Lord
There is one question Let's get together to fight And I will feel all right;
I'd really love to ask (One Heart! ): This Holy Armagiddyon (One Love! ), Let's get together and feel all right.
Is there a place for the hopeless So when the Man comes there will be
sinner, no,
Who has hurt all mankind just No doom (One Song! ).
To save his own beliefs? Have pity on those whose
Chances grows t'inner;
There ain't no hiding place
From the Father of Creation.
Alessandro Pisa - 2012/10/12 - Arnhem Plone Conference 2012
15. Shared members
Register:
✔ on one site
✔ available in the other
Huge work:
✔ login
✔ registration
✔ catalog...
16. Shared members
Register:
✔ on one site
✔ available in the other
Data split in ZODB and SQL
Products.Archetypes.Storage.StorageLayer
Huge work:
✔ login
✔ registration
✔ catalog...
17. Members: solutions
Shared user base:
First ZODB
Then ZODB (per site) + SQL (shared)
SQL Fields
Products.Archetypes.Storage.StorageLayer
caching!
30. Fight for your right
The things you own end up owning you
31. Validation: formlib
from zope.schema import ValidationError
class NotMyEmailError(ValidationError):
"""email has to be alessandro.pisa@redturtle.it!
"""
def is_my_email(value):
if value!='alessandro.pisa@redturtle.it':
raise NotMyEmailError
else:
return True
32. Validation: Archetype
from Products.validation.interfaces.IValidator import IValidator
from Products.validation import validation
from my.custom.product import is_my_email
class FormlibValidatorWrapper(object):
implements(IValidator)
def __init__(self, validator):
self.validator = validator
self.name = validator.func_name
def __call__(self, value, *args, **kwargs):
try:
self.validator(value)
except ValidationError, error:
return error.doc()
validation.register(FormlibValidatorWrapper(is_my_email))