Last July I had the opportunity to attend the Europython Conference. It had been 4 years since the last time I attended Europython but the experience was again amazing. I highlight 3 things: Spending time with TrustYou team, learning more about Python and the Community, and having the experience of improvising a lightning talk being a bad speaker but still a good way to give back to the community.
I'll go through some of the talks I have attended and provide some summary of my learnings. In this post, I summarize half of them ( you can see the others in the Part II blog post about to come )
Technologies to master parallelism in Python by Shailen SobheeEven though the title is misleading (I find it difficult to master something by only taking a workshop), I liked it and it helped me to recall and discover some insights in parallel executions in Python. Some topics that we played with:
This image gives an overview of the interaction of Python and Parallelism:
Fast native code with Cython by Stefan Behnel
Cython is a language to write C extensions for Python as easy as Python. Cython compiler translates Python code to C/C++ and supports static type annotations to allow direct use of C/C++ data types and functions. What is Cython good for?
- Integrate native code in Python
- Speed up Python code in Python
- Writing C without having to write C
In this workshop, Stefan shows us how to speed up our code using Cython and compares time against Python and Numpy code.
The naive programmer by Daniele ProcidaAmazing talk that emphasizes software development as a creative craft ( art ) and reinforces inclusivity of naive programmers. We weren't naive at some point of our career? Aren't we naive nowadays after some years as software developers? Do we behave well with naive programmers around us?
Drawing a parallel line between artists and developer we can see how some sophisticated artists like George Braques and naive artists like Henri Rousseau were accepted by their art in the society. Do we accept in the same way "naive" programmers?
My personal opinion on this topic is that naive is not a permanent state that disappears once you acquire some experience, instead of a state that constantly appears and disappears during our lifetime as developer depending on the context, technology, role and/or others.
I highly recommend you to watch this talk if you have the opportunity. I leave this summary with a question for the ready:
Would you rather be a naïve programmer with a vision, or a sophisticated programmer without?Presentation: the-naive-programmer
Bridging the Gap: from Data Science to Production by Florian WilhelmNowadays Data Science is trending and needed in a lot of organizations. Is a fairly new role in the industry and organizations are still filling the gaps to have an effective workflow ( Production working software ) when Data Science is involved. In this talk, the speaker gives some insights on how to do this based on his experience.
- Production is not an afterthought
- Think early about QA
- DevOps culture
- Team responsibility
- Reduce the number of frameworks and languages up to the minimum
- Embrace processes and automation