Andreas Jung: Plone and the blockchain

Blockchain is the base technology behind bitcoin, but it is not bound to crypto currencies. It is a distributed data structure, usually based on peer to peer. No central entity of control.

Each block has a hash of its previous block, timestamp, transaction root, and a nonce.

Use cases: auditing, financial transactions, logistics, QA, legal, automotive, others.

What does this have to do with Plone and CMS? Some ideas:

• revision safety
• audit trail
• verification of content integrity and authenticity

Our use case: collaborative editing environment. So we created SmashDocs. Using Plone and BigChainDb.

Erico Andrei: Websauna

Websauna is a web framework based on Pyramid. https://tokenmarket.net is created with that, also with blockchain BTW. Miko says hi!

I am using it too, and helping him. We want you on board as well, and we can sprint on it. Also we want to improve Pyramid. Move Websauna to Pyramid 1.9. Documentation. User testing.

See https://websauna.org.

Alexander, Anton: Ploneconf and PyconWeb

Why don't we make a PyconWeb conference? We did that last year. Next one starting on 9 June 1918. See you at https://pyconweb.com

Fred van Dijk: Music to your ears

Confession: I am a bit of an audiophile. When I talk with people about how they listen to music, I get sad. Lot of people use a ten euro headphone. "I don't hear a difference with more expensive ones." I am convinced that a better audio setup helps you work better.

What is the weakest link? Music source (up the settings), D/A converter (underestimated component), cables (spend twenty euros, that's the sweet spot), headphones (ten euro and you expect quality?).

If you divide the costs over the number of hours you listen music: I came at six cents an hour.

Especially the D/A converter (USB) really helped me.

Nejc Zupan: A few Pyramid goodies by Niteo

• pyramid_force_https
• pyramid_redirect
• pyramid_heroku

Releases are on PyPI, enjoy!

Manuel Reinhardt: Giesing 2060

Science fiction writing project about an area of Munich in the year 2060. Using Plone, two content types, snippets that give links to other story snippets, different story lines, you can read through it in various ways.

If you like reading or writing science fiction or Python code, or both, have a look at http://giesing2060.de

Alexander Pilz: Ten years of Euphorie

A Plone success story.

This is a software to guide employers and employees for mandatory health and safety risk assessment. In 2007 Euphorie was created by Wichert Akkerman and Cornelis Kolbach, with the NuPlone interface (currently still working on Plone 5 actually). In 2008 adopted by Europe. In 2016 interest by an industry client of ours.

Why was this successful with Plone? Customisation and enhancement was made easy. Good security. Open source. Now they no longer need to cary kilos of paperwork to factories.

Jens Klein: Alpine City Sprint

I invite you to come to Innsbruck to work with us on the next Plone. Today on an open space we discussed that we may be using Zope 4 on Plone 5.2, and we can work on that.

Welcome January 2018 in Austria. We always visit a special place as well, now a space lab, with simulation for Mars missions.

Perfectionism

One of the bugs is: perfectionism. 'Denys, your work style is like champagne. The company that we merge with, their style is more like prosecco. Less good, but at a party no one notices the difference.'

Perfectionism can be really good and bad. It can be healthy and unhealthy, positive and negative. Steve Jobs was a perfectionist. That worked out good for consumers, but he could be hard to work with, having problems picking the perfect beige color.

Several perfectionist problems:

• Perfectionist paralysis. This can be one reason for procrastination, waiting for an ideal moment to start with an ideal project. Fear of failure: not getting a perfect result. They want perfect tasks, where they know they will succeed.
• Picking a detail.
• Unnecessary task. 'This can be improved. It is not hard, it would not take more than fifteen minutes.' And you spend a day on something that does not give value, or even makes things worse. Perfectionists never know when to stop.

So stop being a perfectionist? No, make your perfectionism positive. Henry Ford was a perfectionist, constantly improving the design, and never going in production. He failed at two companies before investors stopped him.

Think: 'My product should be perfect. And this release/feature/commit moves me one step closer to this perfect result.' Stephen Hawking: 'Perfection simply doesn't exist.'

Imposter phenomenon

• You think that your success is due to luck/timing/etc.
• You think that others might discover that you are not as skilled as they think you are
• You think that others are more intelligent than you are.

Will Smith: 'What people think is my self confidence, is actually my fear.' Lots of people have this. Among them very successful people. Both men and women have this, also in science, shown by studies.

I read websites, Twitter, news feeds, RSS, I get a lot of information, but I cannot read everything. And I still have to work. So I stopped reading them. I may skim the titles, and open a few browser tabs, and leave them open for a few days. I did not want to read it, but my imposter syndrome wanted to read it.

What do we do about it?

• Embrace imposterism. When you are about to read yet another news story: stop and enjoy. You are learning.
• Measure yourself with your own yard stick. That is a good comparison.
• Communicate your fears. Writer Neill Gaiman met Neill Armstrong. 'If he feels like an imposter, maybe everyone else does.'

Long hours

Have you ever worked long hours? Once? Regularly? Did the code work the day after?

A regret of many people before they die is: why have I worked so hard?

Long hours happen. It can be temporary, which can be normal for a hard worker. But it can also be permanent, which is a signal for a workaholic. It is hard to spot the difference. Hard working people have some balance. Are you working and thinking of skiing? Or the other way around?

If you normally work 40 hours, and you work 20 hours more, then this raises productivity for three to four weeks. After that, it drops. Why? Our brain gets tired. So we make errors. So we lack accomplishment. So we make long hours to fix those bugs. And we are in a loop.

The Japanese have a word 'karoshi': death by overwork. Same for 'Guolaosi' in Chinese: 1600 deaths a day.

When the brain detects stress, it sends signals: the chemicals adrenalin and cortisol. This couple is essential for our well being. But when applied for a prolonged period of time, things go wrong: premature ageing of our brain, drop in learning abilities, weakened memory. So it leads to mental disability: you work long hours, and you end up with dementia or alzheimer.

How do we prevent stress?

Look at Harvard University, established 1636, home to 133 nobel laureates and 8 presidents. Students asked if they could do a four year study in three years. Answer: 'Slow down. Get more out of Harvard by doing less. Take a year off.' It helped those who returned after a year. 'College can help you learn how to think, more than what to think.' We need room to think.

Our lives have only version 1.0. We need to fix bugs live, in production.

We need more healthy and happy developers. Acknowledging a problem is the first step to mental health. Debug yourself often and stay healthy and happy. Thank you.

See also my article in Smashing magazine which was published yesterday.

Trust me: at thirty five, either you start thinking about health, or health starts thinking about you.