hnrc/aula

Aula.io - The best of tech talks in one place

Aula.io

This is a project that aims to collect all the best tech talks in a structured fashion, making it easy to discover interesting tech talks at Aula.io

Please contribute by sending pull requests ❤️

The format for talks looks something like this:

{
    "title": "A Whole New World",
    "key": "a-whole-new-world",
    "year": 2012,
    "url": "https://www.destroyallsoftware.com/talks/a-whole-new-world",
    "imageUrl": "https://www.destroyallsoftware.com/images/talks/a-whole-new-world.preview.png",
    "description": "This talk announces the most ambitious software project I've ever undertaken, then considers why its existence is so surprising (and in some cases frustrating) to people.",
    "tags": [
        {
            "title": "Invention",
            "key": "invention"
        },
        {
            "title": "History",
            "key": "history"
        }
    ],
    "speakers": [
        {
            "title": "Gary Bernhardt",
            "key": "gary-bernhardt"
        }
    ],
    "location": {
        "title": "Strange Loop",
        "key": "strange-loop"
    },
    "added": "2014-05-04T09:09:05.904Z"
}

Where all key fields are slugged versions of their corresponding title. added is a ISO 8601 zulu timestamp from the time when the talk was added to this repo.

Contributors 🙌

• mateusz-fiolka
• snurra
• chids
• kristiany
• kagrela
• inem
• stpe
• linusno

Credits

Props to the creators of these fine pieces of code:

• NeDB
• Routie
• SpinKit

aula's Issues

Add John Hughes - "Testing the Hard Stuff and Staying Sane"

Didn't have access to create a PR, so I'll post an issue:

{
    "title": "Testing the Hard Stuff and Staying Sane",
    "key": "testing-the-hard-stuff-and-staying-sane",
    "year": 2014,
    "url": "https://www.youtube.com/watch?v=zi0rHwfiX1Q",
    "imageUrl": "",
    "description": "Even the best test suites can't entirely prevent nasty surprises: race conditions, unexpected interactions, faults in distributed protocols and so on, still slip past them into production. Yet writing even more tests of the same kind quickly runs into diminishing returns. I'll talk about new automated techniques that can dramatically improve your testing, letting you focus on what your code should do, rather than which cases should be tested--with plenty of war stories from the likes of Ericsson, Klarna and Volvo Cars, to show how these new techniques really enable us to nail the hard stuff.",
    "tags": [
        {
            "title": "Testing",
            "key": "testing"
        },
        {
            "title": "Erlang",
            "key": "erlang"
        },
        {
            "title": "Race conditions",
            "key": "race-conditions"
        },
        {
            "title": "Parallelism",
            "key": "parallelism"
        }
    ],
    "speakers": [
        {
            "title": "John Hughes",
            "key": "john-hughes"
        }
    ],
    "location": {
        "title": "Clojure/West",
        "key": "clojure-west"
    },
    "added": "2014-12-23T15:00:00.000"
}