hello, I found a security issue

• As a developer
  • Clearly outline how people can report them,
  • Take reports seriously,
  • Fix it before it's used for bad things,
  • Clearly document fixed security issues.
  • If you have an issue, don't hide it!
• As a user / researcher
  • Check if the issue is known,
  • Inform the developer in private,
  • Allow a reasonable time for the issue to be fixed,
  • Keep track of the issue unless it's fixed (or the time expired).

Being there vs documenting

• Diary to record what I feel / think is better than a camera,
• Experience first of all, then maybe record.

Newcomer's perspective of OSS community

• If you want to learn stuff, do a project on it, contribute, stuff.

IGitt

• lasse@GitMate.io
• Interface for GitLab and GitHub,

Speed packaging

• Secret wheapon: flit.
• It's a bit under development, but soon you'll be able to use it!

Research Software Engineer

• by Raniere Silva,
• there's also a German group.

Python2 vs 3

• ArchLinux fixed it,
• PEP394,
• Don't use #!/usr/bin/env python, use #!/usr/bin/env python{2,3}

Python in Architecture

• BIM "Building Information Model"
• Autodesk Revit
• OSS: revitpythonshell, pyrevit
• rvt_model_services

PyConPl'17

• Challenges!
• This year: Python Strikes Back.
• python-challedges.com

Stuff

• Naming is hard
• Configure github via text files: dothub
• Sealed Mock

aiohttp - testing async HTTP

• It's hard to test async code
• aioresponses

PostgreSQL needs you

• PGConf.EU 2017
• PGDay.IT 2017

Tips on acing tech interviews

• Questions about experience
  • Prove that you might be able to work on the project that you're working on,
  • I want to understand the project.
• Positive attitude,
• Evidence that you can solve problems and think about edge cases.
• Ask in advance how you will be tested (as an interviewer: tell candidates).
• Communication: friendly (also under stress), able to communicate technical concepts.