Moved to https://github.com/kbilsted/Functional-core-imperative-shell/blob/master/README.md
| With the OS X firewall enabled, you can remove the "Do you want the application "python" to accept incoming network connections?" message. | |
| Create a self-signed certificate. | |
| Open Keychain Access. Applications > Utilities > Keychain Access. | |
| Keychain Access menu > Certificate Assistant > Create a Certificate... | |
| Enter a Name like "My Certificate". | |
| Select Identity Type: Self Signed Root | |
| Select Certificate Type: Code Signing | |
| Check the Let me override defaults box |
| from abc import ABC, ABCMeta, abstractmethod | |
| from collections import namedtuple | |
| from itertools import count | |
| PayloadFactory = namedtuple('PayloadFactory', [ | |
| 'good', 'created', 'queued', 'unchanged', 'requires_auth', | |
| 'permission_denied', 'not_found', 'invalid', 'error' | |
| ]) | |
| """ |
| # aecho.py | |
| from socket import * | |
| import asyncio | |
| loop = asyncio.get_event_loop() | |
| async def echo_server(address): | |
| sock = socket(AF_INET, SOCK_STREAM) | |
| sock.setsockopt(SOL_SOCKET, SO_REUSEADDR, 1) |
| import logging | |
| import uuid | |
| import time | |
| from mesos.interface import Scheduler | |
| from mesos.native import MesosSchedulerDriver | |
| from mesos.interface import mesos_pb2 | |
| logging.basicConfig(level=logging.INFO) |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| # encoding: utf8 | |
| import sys | |
| from gi.repository import Gtk | |
| from gi.repository import Gio | |
| from gi.repository import Granite | |
| class Application(Gtk.Application): | |
| def __init__(self): | |
| Gtk.Application.__init__(self, |
| import sys | |
| from gi.repository import Granite | |
| from gi.repository import Gtk | |
| from gi.repository import Gio | |
| class LightWindow(Gtk.Dialog): | |
| def __init__(self): | |
| super(LightWindow, self).__init__() |
| import mesosphere.mesos.util.FrameworkInfo | |
| import org.apache.mesos.MesosSchedulerDriver | |
| /** | |
| * @author Tobi Knaup | |
| */ | |
| object Main extends App { |
Over the last 3 years or so I've helped a bunch of companies, small and large, switch to Django. As part of that, I've done a lot of teaching Django (and Python) to people new to the platform (and language). I'd estimate I've trained something around 200-250 people so far. These aren't people new to programming — indeed, almost all of them are were currently employed as software developers — but they were new to Python, or to Django, or to web development, or all three.
In doing so, I've observed some patterns about what works and what doesn't. Many (most) of the failings have been my own pedagogical failings, but as I've honed my coursework and my skill I'm seeing, time and again, certain ways that Django makes itself difficult to certain groups of users.
This document is my attempt at organizing some notes around what ways different groups struggle. It's not particularly actionable — I'm not making any arguments about what Django should or shouldn't do (at least