Last weekend I attended the Australian Python Conference (pycon) which I enjoyed! I would like to congratulate the organizers, speakers (and the attendees 🙂 for the great work. It was my first time attending this conference, and I appreciated the quality of talks and the organization of the conference. Unfortunately, I only attended half of the conference, as I got sick on the first day.
As someone coming from the academic world, I found pycon very inclusive. The diversity of the attendees was impressive for me. In my opinion, this is one of the main reasons why the conference has such great quality. Furthermore, I could not feel the “cold-war” vibe that some academic conferences have.
- There are good Python modules to extract data from tables in PDF files. The main contributor of the libraries
camelot-pyandexcalibur-pypresented how they work. Dashseems to be more mature thanBokeh(maybe because I am not very familiar with both), as it is based onPlotly,ReactandFlask.Pytestcan be used to test scripts outside the Python ecosystem. For instance, verifying AWS policiesNumbacan be used to accelerate Python algorithms. I have found a link explaining more about it.- When using a microservices, six elements should be taken into consideration
1. Architecture
2. Consistency
3. Interoperability
4. Resilience
5. Deviations
6. Performance - Running post-mortum sessions. These are useful to understand the issues that lead to a software to break. In particular, the point is not to find someone to blame but understand the chain of events leading to issue.
- Software testing can be automatically designed. The module
hypothesisprovides an algorithm that automatically test the code.
Critical point 