The ultimate compilation of novelty Lorem Ipsum sites

Javascript doesn’t make dealing with structured data easy at all. Even when you’re working with data you control, you’re having to put filthy, nasty null checks and do-while descent loops everywhere. When the data is out of your control, such as data pulled from some external JSON(P) API, the problem can become more severe.

A Web cache sits between one or more Web servers (also known as origin servers) and a client or many clients, and watches requests come by, saving copies of the responses — like HTML pages, images and files (collectively known as representations) — for itself. Then, if there is another request for the same URL, it can use the response that it has, instead of asking the origin server for it again.

collection of twitter dev resources

O gods of software development and operations, I have sinned.

Your anger falls on me, and I feel your wrath.

The web site I have inherited has no unit tests.
It has no deployment script, and no README.
Or database migration tool.
It makes no use of virtualenv or requirements.txt or buildout,
    nor has any description of dependencies.
It has most of the VCS history missing.
Source dependencies are in random folders,
    clearly checked out from private SVN clones of
        proprietary and open source projects,
    but forked at unknown date with no history.

And I cry, “Why me?”

Have I not used a fabfile for projects I have started?
Have I not included a setup.py for my open source apps?
Have I not written helpful docs, or at least a README.rst?
Have I not written correct commit messages, with carefully
    constructed patches that didn't mix features and fixes?
Are the projects I hand on not covered by automated tests,
    at least for the critical functions?

But then I consider the sins of my youth,
    and I confess: You are just.