1. 5

I think a lot of us like talking at meetups/conferences/unconferences/funerals, so what talks are you planning on giving or want to give?


  2. 4

    I just gave a talk 3 weeks ago about Curv. It’s a high level, easy to use DSL that is used for procedurally generated art, and to create 3D printable objects. It’s a pure functional array language that compiles into GPU code. That last talk was a lightning talk about creative coding, with a live coding demo. I want to give additional talks about the programming language, the live coding environment, the compiler, the way that geometric shapes are represented on the GPU using signed distance fields. To be honest, Curv is a work in progress, so I’ll be spacing these talks out, to coincide with major development milestones.

    1. 3

      Some I’ve committed to (I really like public speaking):

      • J vs Python: For the Chicago Python Language Shootout next week. Not actually a versus, just me talking about APLs and how they influenced R and numpy.

      • What We Know We Don’t Know: A talk about empirical research in software engineering. The more I research on it the more pessimistic I get. Hoping I can make an interesting and engaging talk that isn’t just me shouting “burn it all down” for 30 minutes.

      • An Alloy Workshop.

      • Why We Should Study Software History: We need to study history to understand the present

      • Somebody asked me to speak on FM research and the Theorem Prover Showdown, so I’ll be doing that in April

      And some I’m not committed to but really want to give:

      • Now I Know My A(bstract) B(ase) C(lass)s: ABCs in Python, __subclasshook__, and the super weird stuff you can do with them. I submitted this to PyCon but had to withdraw it for scheduling reasons.

      • Mechanical Computing: Things like planimeters, Jacquard looms, adding machines, all of the stuff that digital computers made obsolete.

      • Everything Is State Machines: Exactly what it sounds like.

      1. 2

        What We Know We Don’t Know

        This one sounds good to me. make sure you post a link on twitter for any you do :)

      2. 3
        • “23rd Century Software Ethics”: I pretend to be a time traveler, here to talk to software engineers about the state of an ethical code for software developers in the 23rd century. (Submitted for PyCon 2019)
        • “My Little Pony:DevOps is Friendship”: What lessons can DevOps engineers learn from Twilight Sparkle’s adventures in Equestria? (Submitted for All Things Open 2019)
        1. 2

          I’m thinking of a lightning talk to give at PyCon this year. I gave a talk at PyOhio (blog post: Bringing macros to Python by abusing type annotations) not too long ago, so if I don’t have time to come up with something else I may just do that again. I’d like to do something different, but I need to finish this PhD at some point :)

          1. 2

            The company I work at has semiregular talks for developers and I’ve been meaning to write “How to Not Be Afraid of Large (and Small) Numbers” for a while. I want to explain back-of-the-envelope estimation “at the edges” and why it’s useful. “At the edges” means what might happen if you take some variable of a problem to the limit. A practical example for my team would be asking “how many servers could we ever possibly use?,” then seeing what it would cost to actually do that. Thinking along these lines reveals hidden bottlenecks and contours in the problem, and being comfortable doing these thought experiments lets you brainstorm and navigate scaling issues better.

            1. 2

              I am giving a talk at the 17th International Conference on Gambling and Risk taking. It is on how if one’s gambling positions do not follow the probability calculus they are exposed to assured loss (arbitrage). I am presenting a “boost”-style algorithm a la Schapire to repair such flawed positions and provide a measure of protection.

              1. 2

                I’m planning out a talk on honeypots for devops teams. A lot of devops teams I deal with are curious about what attacks actually look like, so the plan is to walk them through deploying a honeypot that matches their infrastructure services, so they can get a rough idea of what to look for when facing real-world adversaries.

                I’ll probably give it at a few internal places for specific teams, and possibly as a workshop at a couple of colleges and Unis I help out with.

                1. 1

                  All my CFPs are on my website. I’m not sure that’s the best place but I haven’t figured out a better solution. I’d like to give a talk on burnout with other complications (disability, disease, mental health issues, etc.).