To add a personal anecdote, I was accepted to speak at a large regional conference as my first speaking gig. I explicitly stated I did not have any previous conference experience. I attribute this partially to having a relatively niche topic.
I was lucky enough to give the talk twice at a local user group prior to the conference, which helped with the actual conference talk, I am sure.
We use http://www.dbmaintain.org at the Java shop where I work. It enforces all of the best practices in the article.
Something else that we do is to have the schema/mandatory data in a separate git project. This has the added benefit of having a separate deployable artifact from the application itself.
Is "So if there are 23 people in a room there's a 50% chance that one of them will share a birthday with me?" correct? If you pick a fixed person (you) that would break the pigeonhole principle, I think.
I would think that saying "So if there are 23 people in the room there is a 50% chance any 2 of those people share the same birthday" is better.
Edit: I misunderstood, you're saying that other people are misunderstanding. My mistake!
I think that programming is a microcosm of culture as a whole, not just pop culture. On one end you have the pop aspects of it (Node, Ruby, <insert trendy language/framework>, and at the other end you have COBOL and Fortran and other 'un-hip' languages. In-between is everything that makes up the programming culture.
I notice that some of the tips have code examples and some don't. I know that people other than the author of the tip can post comments, but it may be useful if they could also post gists along with the comment. This way tips without examples could be fleshed out by someone other than the author.
This might be an obvious suggestion, but have you tried building something useful? I have found myself in that strange in between space before when learning a new language, and by starting to build something I am able to quickly move past that middle ground.
I see a couple mentions in this thread of Flask taking a while to adopt Python 3. I am relatively new to Flask, could you explain why they are seemingly behind things in regards to Python 3?
I was lucky enough to give the talk twice at a local user group prior to the conference, which helped with the actual conference talk, I am sure.