You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last night, I received the news that Malcolm Tredinnick had passed away. I was
at the hotel bar, concluding the first night of sprints at PyCon 2013. It took
everything I had not to spontaneously start crying on the spot.
Malcolm was a friend, a mentor, a valued community mentor, a leader and a
wonderful human being. He gave freely of himself to so very many people &
causes. He made himself available to others, even when he was so busy he could
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Over the last 3 years or so I've helped a bunch of companies, small and large, switch to Django. As part of that, I've done a lot of teaching Django (and Python) to people new to the platform (and language). I'd estimate I've trained something around 200-250 people so far. These aren't people new to programming — indeed, almost all of them are were currently employed as software developers — but they were new to Python, or to Django, or to web development, or all three.
In doing so, I've observed some patterns about what works and what doesn't. Many (most) of the failings have been my own pedagogical failings, but as I've honed my coursework and my skill I'm seeing, time and again, certain ways that Django makes itself difficult to certain groups of users.
This document is my attempt at organizing some notes around what ways different groups struggle. It's not particularly actionable — I'm not making any arguments about what Django should or shouldn't do (at least
When using yarn, it will create a yarn.lock lockfile which holds data on your used dependencies. This file also includes hard-typed versions, so should you update your dependencies, the yarn.lock file is basically outdated and needs to be regenerated. While yarn does this automatically, Greenkeeper pull requests that update dependencies as of right now do not do this regeneration, which means you would have to do it manually.
This gist shows you a way how to automatise this step using a Travis CI script.
Prerequisites
You use Travis CI and have it build Pull Requests (default behaviour)
You have a yarn.lock file in your repository for Travis CI to automatically install yarn (yarn will be added to their default images soon)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We got inspired by the RailsGirls workshops and plan to organise similar workshops in Berlin for women and all sorts of beginners but for Python this time.
We need you Python enthusiasts to help us with the coaching!
So if you think you can help coaching Python put your name down here (by forking this gist and adding yourself or leaving your contact details in a comment).
No need to be an expert, no matter how much you know about Python programming your knowledge and experience will be useful to a beginner!
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters