Moshe has been in the open source community since 1995 and in the Python community since 1999. He has been a core contributor to Python, and is a core contributor, and an early member, of the Twisted project.
Moshe has given talks at the International Python Conference, PyCon, PyBay, PyTexas and several Python and Docker meetups.
This workshop will take a tour of all the pieces that go into making a web application, and show how they all fit together -- using specific choices, specific examples and a lot of hands-on programming, to give participants a chance to actually write a web applications: all the parts.
The workshop will cover:
Web application structure (10m)
Pyramid (15m + hands-on time)
Hands-on: Modify application (15 minutes)
React (10m + Hands-on time)
Serving static files
Hands-on: Modify how we serve files (15m)
Real react application example
Hands-on: Modify application (20m)
Storage (35m + Hands-on time)
Changing application to have storage
Hands on: Modify storage (15m)
Containers (15m + Hands-on time)
Naive container build
Multi-stage container build
Running containers locally
Hands on: Improve container automation (10m)
End-to-end testing (15m + Hands on time)
Running Docker in docker
Hands-on: Adding a test (10m)
Summary and Q&A
Ever had a code review that was nothing more than nitpicking?
Ever gave one?
Nitpicks do not foster good relationships,
but code consistency is good to have.
Let the robots nitpick for you,
and have interesting discussions about code instead!
Nitpicking in code review is often as annoying for the reviewer as it is for the submitter, and tends to cause social friction. Using the modern Python static analysis toolbox -- PyLint, flake8, MyPy and more -- it is possible to leave the nitpicks to automated processes.
This frees up human reviewer time for important work, like checking that the code is clear and effective -- while letting the nitpicks not just be objective and impartial, but be so in a verifiable way.