jeroenvdgulik

The list is now hosted on a repository so you can PR -> https://github.com/jeroenvdgulik/awesome-talks/blob/master/README.md

The list

• Alberto Brandolini - Chasing Elephants https://youtu.be/klsksbDJOhI
• Erik Meijer - One Hacker Way https://youtu.be/FvMuPtuvP5w
• Erik Meijer - Category Theory, The essence of interface-based design https://youtu.be/JMP6gI5mLHc
• Gary Bernhardt - Wat https://www.destroyallsoftware.com/talks/wat
• Konstantin Kudryashov - Min-maxing Software Costs https://youtu.be/uQUxJObxTUs
• Marco Pivetta - Extremely Defensive PHP https://youtu.be/8d2AtAGJPno

ryanflorence

Turning Off Github Issues

My friend Michael Jackson turned off github issues on one of his smaller projects. It got me thinking...

Maintainers getting burned out is a problem. Not just for the users of a project but the mental health of the maintainer. It's a big deal for both parties. Consumers want great tools, maintainers want to create them, but maintainers don't want to be L1 tech support, that's why they

aturley

use "collections"
use "lib:sqlite3"

actor Main
  let _env: Env
  new create(env: Env) =>
    _env = env
    let args = env.args

    var db: Pointer[U8] = Pointer[U8]

bradwilson

# Background colors
$GitPromptSettings.AfterBackgroundColor = "DarkBlue"
$GitPromptSettings.AfterStashBackgroundColor = $GitPromptSettings.AfterBackgroundColor
$GitPromptSettings.BeforeBackgroundColor = $GitPromptSettings.AfterBackgroundColor
$GitPromptSettings.BeforeIndexBackgroundColor = $GitPromptSettings.AfterBackgroundColor
$GitPromptSettings.BeforeStashBackgroundColor = $GitPromptSettings.AfterBackgroundColor
$GitPromptSettings.BranchAheadStatusBackgroundColor = $GitPromptSettings.AfterBackgroundColor
$GitPromptSettings.BranchBackgroundColor = $GitPromptSettings.AfterBackgroundColor
$GitPromptSettings.BranchBehindAndAheadStatusBackgroundColor = $GitPromptSettings.AfterBackgroundColor
$GitPromptSettings.BranchBehindStatusBackgroundColor = $GitPromptSettings.AfterBackgroundColor

thedanfernandez

# Step 0 - Open a PowerShell Command Prompt as Administrator
# Step 0.5 - Set execution policy to remotesigned
# Set-ExecutionPolicy remotesigned

iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))


#Apps and Utilities
choco install greenshot --yes
choco install googlechrome --yes

damianh

    using System;
    using System.Collections.Generic;
    using System.Threading.Tasks;
    using Microsoft.Owin;
    using AppFunc = System.Func<System.Collections.Generic.IDictionary<string, object>, System.Threading.Tasks.Task>;
    using MidFunc = System.Func<
        System.Func<System.Collections.Generic.IDictionary<string, object>, System.Threading.Tasks.Task>,
        System.Func<System.Collections.Generic.IDictionary<string, object>, System.Threading.Tasks.Task>>;

    public static class ChaosMiddleware

ryanflorence

Hi Zach :D

Modals are funny beasts, usually they are a design cop-out, but that's okay, designers have to make trade-offs too, give 'em a break.

First things first, I'm not sure there is such thing as a "simple" modal that is production ready. Certainly there have been times in my career I tossed out other people's "overly complex solutions" because I simply didn't understand the scope of the problem, and I have always loved it when people who have a branch of experience that I don't take the time

rofr

using System;
using System.Collections.Generic;
using System.Linq;


namespace OrigoDB.Core.Models
{
    /// <summary>
    /// Message broker supporting any number of queues (competing consumers)
    /// or topics (multiple subscribers)

ThatRendle

Update, September 2016

OK, you can pretty much ignore what I wrote below this update, because it doesn't really apply anymore.

I wrote this over a year ago, and at the time I had spent a couple of weeks trying to get Kafka 0.8 working with .NET and then Node.js with much frustration and very little success. I was rather angry. It keeps getting linked, though, and just popped up on Hacker News, so here's sort of an update, although I haven't used Kafka at all this year so I don't really have any new information.

In the end, we managed to get things working with a Node.js client, although we continued to have problems, both with our code and with managing a Kafka/Zookeeper cluster generally. What made it worse was that I did not then, and do not now, believe that Kafka was the correct solution for that particular problem at that particular company. What they were trying to achieve could have been done more simply with any number of other messaging systems, with a subscriber reading messages off and writing

danbarua

    using System;
    using System.Collections.Generic;
    using System.Diagnostics;
    using System.Linq;
    using System.Reflection;

    using ServiceStack.Net30.Collections.Concurrent;

    /// <summary>