dominicrodger

> If your documentation is a directory full of files on GitHub, I close the tab. With GitHub Pages, Read the Docs, and other places to host generated documentation for free, not making an effort is unforgivable.

He's not arguing against GitHub pages - he's arguing against just linking to a file/folder in your GitHub repository and thinking you're done (e.g. https://github.com/<org>/<project>/docs).

Pretty sure it's a typo (speaking as a Brit).

In the mother of all pedantic pull requests, I've created https://github.com/python/pythondotorg/pull/77

It's now documented and everything: https://docs.djangoproject.com/en/dev/topics/migrations/#upg...

Doesn't this mean people can track whether you've read an email by including some kind of unique identifier in the image path? If not, how could this possibly work?

Likewise - I did this as part of a hackathon earlier this year - thoroughly enjoyed seeing how all the pieces fitted together.

See also https://news.ycombinator.com/item?id=4970707

I'm pretty sure they're just markers telling you what the code is an example of, so they get out of your way when you hover over the code.

We use it to mean practising how we handle bad things, such as unexpected server failures, which seems to me a reasonable appropriation of the term.

Thanks for the write-up - interesting read.

Out of interest, how do you catch and block all POST requests when the site's in read-only mode without duplicating code? Not sure if you use CBVs at Lanyrd - if so, do you use a common mixin? If not, how?

See also "Entmoot" from Lord of the Rings.

I don't think it is, based on the GitHub repository powering http://slug.in (https://github.com/yetizzz/zzz).

Kenneth Love's working on this at http://gettingstartedwithdjango.com/.

Isn't that what http://fredericjacobs.com/identifying-the-traitor is?

What's wrong with PIL on Ubuntu? If you're running into needing to repoint JPEG_ROOT/ZLIB_ROOT - I've started avoiding that by symlinking where PIL expects things to be to where they actually are). Works a charm, and avoids using --system-site-packages.

FWIW, I think "Will Chirp become 'next Twitter'?" was the short version of the title, based on the most read links on the BBC site.

Nice work! Might want to update the README - it's no longer a jQuery plugin.

Maybe previous experience is significant - I learned to program building websites (HTML -> early CMSes -> PHP), then did a computer science degree (mostly Java, though I did a bit of Ruby on Rails), then got a job in C++ (where I still work, 3 years later), which I'd been doing for a year or so by the time I picked up Django.

To be honest, I suspect my Python's not great - I probably ought to spend more time just writing Python - I'd hazard a guess that less than 20% of the time I spend building websites with Django is spent writing Python (most is probably spent fiddling around with HTML/JS). I can always get by - but every once in a while I learn something new that I wish I'd known about long before (I remember learning about list comprehensions at an intro to Python talk at Stack Overflow DevDays after I'd been using Python for about a year!).

FWIW - I learned Python by learning Django, and loved it. Probably a meaningless datapoint, but I thought I'd offer it anyway.

Presumably only by observing a company over time: does their behaviour change? Have they kept their promises for how they're going to fix it?

Anyone else's imaginations going wild thinking what bizarre combination of circumstances might lead to the lack of a "group by" in an ORM leading to a gradual death, during which one still has sufficient strength to post to HN?

The quote is Kernighan's I think: "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."