Skip to content

Latest commit

 

History

History
71 lines (60 loc) · 6.38 KB

november.md

File metadata and controls

71 lines (60 loc) · 6.38 KB

November 2019

Getting beyond process

  • Clay Shirky (2003), A Group Is Its Own Worst Enemy - http://www.shirky.com/writings/herecomeseverybody/group_enemy.html 1.) If you were going to build a piece of social software to support large and long-lived groups, what would you design for? The first thing you would design for is handles the user can invest in. 1.) Second, you have to design a way for there to be members in good standing... some way in which good works get recognized 1.) Three, you need barriers to participation 1.) ...you have to find a way to spare the group from scale. Scale alone kills conversations, because conversations require dense two-way conversations
  • Pete Hodgson (2019), Hello, Production - https://blog.thepete.net/blog/2019/10/04/hello-production/

    Deploying something useless into production, as soon as you can... pulls unknown risk forward, opens up parallel streams of work, and establishes good habits.

  • Ted Dziuba (2011), on how to produce good software - http://widgetsandshit.com/teddziuba/2011/12/process.html

    policies and procedures irritate top performers, and are just more grievances on their list that will some day metastasize into a resignation letter. (Side note: if someone keeps such a list, there's a high probability they are a top performer.

    • Rule 1: Resist Process from the Start
    • Rule 2: Grow Headcount as a Last Resort
    • Rule 3: Use The GitHub Workflow (And Other Good Stuff)
    • Rule 4: Just Let Go

Programming

Architecture

HTML and CSS

React and Redux

JavaScript

WebAssembly

TypeScript