1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both 4. eliminate local variables to an absurd degree
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both 4. eliminate local variables to an absurd degree 4a. start with functional chains
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both 4. eliminate local variables to an absurd degree 4a. start with functional chains 4b. refactor via functional composition
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both 4. eliminate local variables to an absurd degree 4a. start with functional chains 4b. refactor via functional composition 4c. use tap/each as if to scream "Side Effect!"
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both 4. eliminate local variables to an absurd degree 4a. start with functional chains 4b. refactor via functional composition 4c. use tap/each as if to scream "Side Effect!" 5. minimize third-party dependencies and write wrappers around them
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both 4. eliminate local variables to an absurd degree 4a. start with functional chains 4b. refactor via functional composition 4c. use tap/each as if to scream "Side Effect!" 5. minimize third-party dependencies and write wrappers around them 6. pull side-effects nearer the entry point (imperative shell / functional core)
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both 4. eliminate local variables to an absurd degree 4a. start with functional chains 4b. refactor via functional composition 4c. use tap/each as if to scream "Side Effect!" 5. minimize third-party dependencies and write wrappers around them 6. pull side-effects nearer the entry point (imperative shell / functional core) 7. disagree with whatever my pair does every 10 minutes
1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both 4. eliminate local variables to an absurd degree 4a. start with functional chains 4b. refactor via functional composition 4c. use tap/each as if to scream "Side Effect!" 5. minimize third-party dependencies and write wrappers around them 6. pull side-effects nearer the entry point (imperative shell / functional core) 7. disagree with whatever my pair does every 10 minutes 8. overwhelm people with information so that I get my way
FORM APPROVED OMB NO. 1651-0009 Customs Declaration 19 CFR 122.27, 148.12, 148.13, 148.110,148.111, 1498; 31 CFR 5316 Each arriving traveler or responsible family member must provide the following information (only ONE written declaration per family is required). The term “family” is defined as “members of a family residing in the same household who are related by blood, marriage, domestic relationship, or adoption.” 1 Family Name First (Given) Middle 8 Countries visited on this trip prior to U.S. arrival 4 (a) U.S. Street Address (hotel name/destination (b) City (c) State 10 The primary purpose of this trip is business: Yes No 11 I am (We are) bringing (a) fruits, vegetables, plants, seeds, food, insects: Yes No (b) meats, animals, animal/wildlife products: Yes No (c) disease agents, cell cultures, snails: Yes No (d) soil or have been on a farm/ranch/pasture: Yes No 12 I have (We have) been in close proximity of livestock: Yes No 3 Number of Family members traveling with you 5 Passport issued by (country) 6 Passport number 7 Country of Residence 2 Birth date Month Day Year 9 Airline/Flight No. or Vessel Name This Space For Offical Use Only
8 Countries visited on this trip prior to U.S. arrival 10 The primary purpose of this trip is business: Yes No 11 I am (We are) bringing (a) fruits, vegetables, plants, seeds, food, insects: Yes No (b) meats, animals, animal/wildlife products: Yes No (c) disease agents, cell cultures, snails: Yes No (d) soil or have been on a farm/ranch/pasture: Yes No 12 I have (We have) been in close proximity of livestock: Yes No (such as touching or handling) 13 I am (We are) carrying currency or monetary instruments over $10,000 U.S. or foreign equivalent: Yes No (see definition of monetary instruments on reverse) 9 Airline/Flight No. or Vessel Name
THE FOLLOWING TALK HAS BEEN APPROVED FOR APPROPRIATE AUDIENCES BY THE PEOPLE WHO RATE TALKS, I GUESS? THE TALK ADVERTISED HAS BEEN RATED F FEELS SOME STRONG EMOTIONS, EVIDENCE OF RELATABLE HUMANITY THROUGHOUT
THE FOLLOWING TALK HAS BEEN APPROVED FOR APPROPRIATE AUDIENCES BY THE PEOPLE WHO RATE TALKS, I GUESS? THE TALK ADVERTISED HAS BEEN RATED F FEELS SOME STRONG EMOTIONS, EVIDENCE OF RELATABLE HUMANITY THROUGHOUT
Indirection Score For a given code path: 1. How many names are encountered? 2. How many source files contribute code? 3. How many tests redundantly cover it?
Indirection Score For a given code path: 1. How many names are encountered? 2. How many source files contribute code? 3. How many tests redundantly cover it? 4. How much is handled by dependencies?
Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using U
Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ U
Somebody has idea U 0 Experiments with idea 0 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Shares idea with others 00
Somebody has idea U 0 Experiments with idea 0 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Shares idea with others 00
Somebody has idea U 0 Experiments with idea 0 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Shares idea with others 00 "Evangelists"
Somebody has idea U 0 Experiments with idea 0 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Shares idea with others 00 Meme Salespeople
Shares idea with others 00 Somebody has idea U 0 Experiments with idea 0 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Idea becomes popular 000
Shares idea with others 00 Somebody has idea U 0 Experiments with idea 0 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Idea becomes popular 000 Aspirational Adopters
Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty Implement with boring code The Boring Code Discovery Model
Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty Implement with boring code The Boring Code Discovery Model Certification Program Coming Soon!
“Some segments of this book may be rough going. That’s the nature of real science. It requires thought. Sometimes deep thought. But thinking can be rewarding. You can just skip the rough parts, or you can struggle to understand. If your struggle is fruitless, then that’s my fault, not yours, and I apologize." Kip Thorne, The Science of Interstellar:
searls
afilina
okuzawats
rakus_dev
suzukimar
akkyie
pospome
uhooi
codehex
yujisoftware
palkan
ryos36
kasacchiful
trallard
lara
zakiwarfel
paulrobertlloyd
stephaniewalter
jnunemaker
chrislema
eileencodes
reverentgeek
carmenintech
akosma
sonatard