Text extraction. See Typescript Index 2025-03-09, Typescript Transcripts, Transcriber Notes 2025-03-09.
09:11:26
09:11:26 From Jeff Miller ghost writer, graduate student, law clerk at least putting the grad student in as co-author has a point
09:14:47
09:14:47 From Jeff Miller oh hi Eric!
09:20:25
09:20:25 From Jeff Miller The inside of a research office looks a lot like a small business making bets about grants and publications. (my experience in grant-funded planetary astronomy)
09:22:18 From Jeff Miller big frog small pond? (to Brian #1)
09:22:26 From Marc Pierson https://www.amazon.com/dp/B0DZTDWH2D/ref=sr_1_1?crid=2QYJW1RJN9GCM&dib=eyJ2IjoiMSJ9.YIrXctwqzkWD2L-jdpkN4Q.T-nDGgBoj5s_CofEwxs8nF9uHfOVA-faoRU1h6S1keA&dib_tag=se&keywords=do+it+right%2C+michael+lissack&qid=1741532895&sprefix=do+it+right%2C+michael+lissack%2Caps%2C158&sr=8-1
09:22:44 From Jeff Miller oh the classic line about university politics being fierce because the stakes are so small?
09:25:42
09:25:42 From jan dittrich (er/he|they – Siegen) fell victim to the timezone thingy! Thanks for the reminder @Ward Cunningham!
09:29:39
09:29:39 From Jeff Miller the complete O'Reilly guide to Federated Wiki?
09:30:10 From jan dittrich (er/he|they – Siegen) Reacted to "the complete O'Reill..." with 👍🏻
09:30:17 From Jeff Miller Wiki for the Discord Generation?
09:31:44 From Brian Reacted to "oh the classic line ..." with 😀
09:33:49 From Jeff Miller "Crossing the Chasm" (thanks Brian M)
09:34:21 From Brian Would a fedwiki book be for visionaries or for pragmatists?
09:34:49 From jan dittrich (er/he|they – Siegen) Since Brian Marick mentioned "Popularizing": Briefly thought of the "Village health care handbook": https://en.hesperian.org/hhg/New_Where_There_Is_No_Doctor (I did some interviews and research about it, its fascinating, but I was unable to interview anyone form hesperian) Replying to "Would a fedwiki book..." I would assume books are more for pragmatists, usually?
09:35:24 From Jeff Miller I wonder if Obsidian is a reasonable point of comparison that has been adopted by pragmatists. linked notes with a nice skin and built-in workflow
09:37:19 From Jeff Miller oh right Where There Is No Doctor is famous
09:37:28 From Brian I think FedWiki is "visionary" oriented, say in contrast to Obsidian which is more pragmatic. (Thank you Jeff and Brian for concepts).
09:37:35 From Jeff Miller (I joke a lot about "Where There Is No Manager")
09:37:58 From jan dittrich (er/he|they – Siegen) Agree with @Brian Marick here - this kinda matches the conversation around "shouldn't there be just some buttons" for what one can do.
09:38:22 From Jeff Miller "the javascript ecosystem", yes, what's the community around the technology?
09:38:34 From Brian https://www.purescript.org/
09:38:46 From Jeff Miller Javascript has been a bunch of rug-pulls for me in the NodeJS ecosystem. oh ObjectiveJ a copy of the MacOS widgets in Javascript? oh right there's a Javascript Canvas library like that, PaperJS.
09:40:10 From Jeff Miller it's a port of a different graphics widget library with a different underlying engine.
09:40:34 From jan dittrich (er/he|they – Siegen) "where there is no manager": "Ship it" would probably by my goto book :)
09:40:42 From Jeff Miller :)
09:41:25 From Pete Cappucino - Apple AppKit in Objective-J javascript (2018-09-10): https://github.com/cappuccino/cappuccino/tree/v1.0.0
09:43:04 From Pete https://www.cappuccino.dev/learn/
09:43:37 From jan dittrich (er/he|they – Siegen) oh, I had an interesting conversation with Felienne Hermans on the fear of learning something wrong around programming.
09:43:44 From Jeff Miller (Brian M gives an anecdote about the Purescript community and their attitude toward how to learn it)
09:43:54 From jan dittrich (er/he|they – Siegen) HA! just wanted to mention Djikstra.
09:44:27 From Brian Learning Haskell is so steep and long learning curve, everything else is downhill...
09:44:29 From Jeff Miller Jan: I'd love to hear that. Felienne Hermans is famous for a practitioner / researcher approach to learning software.
09:44:38 From jan dittrich (er/he|they – Siegen) something something "Purity and Danger"
09:44:47 From zach lol
09:44:59 From Marc Pierson Some quick notes stimulated by reading the Brians’ writing on the FedWiki.
09:44:59 From jan dittrich (er/he|they – Siegen) @Jeff Miller Yes, I can briefly tell about that.
09:45:02 From Jeff Miller (laughs in anthropology being the only actual science)
09:46:10 From Jeff Miller people don't warn you about graceful diplomatic recovery being a core skill
09:47:20 From Jeff Miller oh right, in Obsidian "rename a page"; hard when you have the page history and links; but not super hard; it would require some choices
09:48:06 From jan dittrich (er/he|they – Siegen) Replying to "oh right, in Obsidia..." its easy in joplin, but I think only because page’s "real name" is just an id.
09:48:18 From Brian @Brian Marick Later on this summer, I'd like to follow back with on your 'static typing for functional programming' work as it should apply equally to the language I'm working on that is statically typed "Forth" that is basically high level lambda calculus...but I'm trying to wrap up some FedWiki explorations.
09:48:42 From Jeff Miller Replying to "oh right, in Obsidia..." right, the newer Confluence is "page name is really an ID", with the display name as the tail of the URL Replying to "oh right, in Obsidia..." I wonder if there are lessons from Wikipedia's different language instances and mappings Replying to "oh right, in Obsidia..." between page and page
09:49:29 From Brian Start book.relocalizecreativity.net and start working on the table of contents. Write the book on the fedwiki...
09:50:43 From jan dittrich (er/he|they – Siegen) Replying to "oh right, in Obsidia..." excellent idea. I think they are connected via Wikidata today? So every page links to a id-ified Wikidata thingy, and that provides the links.
09:50:47 From Jeff Miller (Eric gives a summary of Elm vs. React, where React has a directional data flow like Elm's architecture)
09:50:53 From zach React ruined web programming for the past 15 years
09:51:20 From Jeff Miller Facebook putting its name behind React was a supercharging force.
09:51:50 From zach Yeah, then they turned heel, and now we’re stuck with a generation of web programmers who don’t know html
09:52:13 From Brian popularity accelerates the climb up the S curve, so if the exploration part is desired to be long, then popularity is in conflict.
09:52:30 From Jeff Miller (Eric speculates that Purescript's priorities may not be friendly to any compromise toward widely promoting Purescript) nods in "books from O'Reilly" (toward Eric -- similar intro to the field)
09:53:36 From Jeff Miller Tim O'Reilly's business model: providing the bridge between the early adopters and the pragmatists.
09:53:50 From jan dittrich (er/he|they – Siegen) Oh, I did some actual research of learning programming before stackoverflow. Was pretty interesting. (A lot about books, magazines and trying to recreate games)
09:54:04 From Jeff Miller "I'll get an alpha geek and some good editorial staff, and it'll be ready for the pragmatists"
09:54:16 From Marc Pierson Now in a FedWiki page: https://marc.relocalizecreativity.net/view/the-federated-wiki-a-book
09:54:21 From Jeff Miller (Eric, on Tim O'Reilly)
09:54:24 From jan dittrich (er/he|they – Siegen) Replying to "Oh, I did some actua..." ("actual" as in "not just me being interested in it")
09:55:39 From Jeff Miller keeping the platform's core simple so that it can be flexible for creative adaptation, but the core can't be compromised in certain ways without spoiling the value and vision (summary of the discussion, Eric and Marc)
09:56:14 From zach This suggests that UX is somehow the way to cross the chasm, and that’s not the conclusion of that book fwiw
09:56:21 From Jeff Miller There's an opportunity for pragmatic configured installations of FedWiki now.
09:56:59 From Marc Pierson https://marc.relocalizecreativity.net/view/context-in-fedwiki FedWiki provides massive possibilities for sustaining context.
09:57:17 From Jeff Miller Jef Raskin's essay about making new platforms look familiar (from Jan)
09:57:41 From Brian https://dl.acm.org/doi/pdf/10.1145/182987.584629 Intuitive equals familiar
09:58:17 From Jeff Miller Felienne Hermans - "Hedy" programming language, with a progressive set of complex features, starting easy and simple for the learner clever heuristics for leveling up toward a full Python syntax and semantics (reminds me of learning physics!)
09:58:45 From zach Named for Hedy Lamar by any chance?
09:58:58 From Jeff Miller likely yes, look it up? :)
09:59:12 From Brian Learning "wrong" way only does harm if you stop learning.
09:59:22 From Jeff Miller physics: start with stories and names and interactions, return with more mathematics each revisit
09:59:51 From Eric Dobbs Racket https://racket-lang.org/ probably should be spelled (racket) also has a capability to gradually introduce complex programming constructs.
09:59:56 From Jeff Miller (laughing in "keeping the self-taught people out")
10:00:02 From Paul Rodwell oh, you are on daylight saving already…
10:00:17 From Brian Switched to DST this morning.
10:00:18 From Jeff Miller right, indeed, big barbecue and golf all the afternoon outside sports businesses repeal Big Railroad's concept of time zones
10:01:16 From Marc Pierson Campfire conversations.
10:01:34 From jan dittrich (er/he|they – Siegen) Replying to "Racket https://racke..." Nice. I played a bit with it. I think LISP is fascinating as it never seemed as pure and math-y has haskell and friends. Clojure seems to do a lot of interesting things, too and Penpot seems to be entirely Clojure.
10:01:49 From Jeff Miller If you told the story of the technological evolution of Federated Wiki, it would be the story of the core team's questions and answers and choices. (thinking of Brian M's relation of explaining FedWiki to Dawn)
10:02:09 From Brian Would that be the pattern for all stories?
10:02:39 From Jeff Miller "a lot that happens OUTSIDE the wiki platform itself that's important for learning FedWiki; it's hard to scale small-group collaboration" "Design Patterns Reading Groups" = my entree to small-group collaboration
10:03:06 From jan dittrich (er/he|they – Siegen) Small group collaboration: Yes! I think that also makes it possible to learn the interface without "Button = Action"
10:03:18 From Jeff Miller The Law of Raspberry Jam / The Law of Strawberry Jam well it's Erdos numbers super collaborator the original super collaborator
10:03:50 From Brian I paired with Ward in a bar for 5 minutes on some bizarred VM for my WC#... :)
10:04:52 From Paul Rodwell https://en.wikipedia.org/wiki/Six_Degrees_of_Kevin_Bacon
10:05:06 From zach someone bet him that he couldn’t quit the speed for a month so he did, and when he was done he said, “you have proven to me I’m not an addict, but worse you have set mathematics back a month"
10:05:22 From jan dittrich (er/he|they – Siegen) Agile by learning from others: I can imagine! My academic example is Ethnomethodology, where most people who can do it seem to be connected to Garfinkel (its inventor). Learning it from books is notoriously difficult. Garfinkel also wrote notoriously difficult as if avoiding success at all cost :D
10:05:45 From Marc Pierson Plurality. Diversity. As good rather than bad. A paradigm shift.
10:06:12 From Jeff Miller the problem of the field growing faster than wisdom can be translated
10:06:26 From Marc Pierson https://pleurality.relocalizecreativity.net/view/welcome-visitors/view/index
10:06:34 From Brian XP was a better way, somewhat enabled by Contineous Integration than the previous development methods.
10:07:32 From Jeff Miller extreme sports = you have to learn it experientially and be resilient to failures as you are learning (Eric describing experiential learning necessary for learning Extreme Programming - either you have to learn from someone who knows, or you have to have a high tolerance for failure and resilience)
10:08:54 From Jeff Miller oh gosh early continuous integration, Cruise Control, so painful and janky to set up "works for Thoughtworks, there must be a pony in there somewhere!"
10:09:56 From Jeff Miller "Where Is The Pony: Crossing the Chasm for the Discord Generation"
10:10:01 From Brian Brian, you might turn video off and go audio only for a bit. Unicode.
10:10:19 From Jeff Miller oh right, Kanji names and slugs a little like Victoria Campbell's experiments slug-ification to US-ASCII are a limitation so what does Wikipedia do?
10:11:30 From Jeff Miller leaving breadcrumbs to old names in the journal or in the site index page? "this page has been renamed..." (Eric discusses problems that FedWiki has not chosen to address as yet, which might make it more broadly adoptable)
10:12:12 From Brian http://147.182.253.245:3000/view/welcome-visitors/view/fedwiki-rename-page-feature
10:12:30 From Paul Rodwell Replying to "so what does Wikiped..." https://ja.wikipedia.org/wiki/%E5%AF%8C%E5%A3%AB%E5%B1%B1
10:12:44 From Jeff Miller (jQuery and Coffeescript modernization in progress now)
10:13:02 From zach yeah I was gonna drop it into tauri for y'all
10:13:03 From Jeff Miller Replying to "so what does Wikiped..." URL-safe characters
10:13:14 From zach Now there are two people asking for it
10:13:20 From Brian Would LSP be considered a native app?
10:13:45 From Jeff Miller Mt. Fuji! (where the browser's address line translates it back to Kanji) LSP: Language Server Protocol?
10:14:12 From zach lol
10:14:48 From Paul Rodwell Replying to "so what does Wikiped..." shows as 日本語 in the address bar
10:15:12 From Jeff Miller "Web Components" frameworks - oh the replace-a-piece-of-the-DOM technology?
10:15:24 From Brian I'd decrease the use of phone apps to as large as of extent as possible...
10:15:47 From Jeff Miller tax the bandwidth at the server? ;)
10:16:04 From zach This is what I do for a day job. I can do a mobile presentation for y’all if you want
10:16:08 From Brian Many apps now license their "apps" bandwidth to 3rd party data collectors unrelated to app...
10:16:08 From Jeff Miller oh right GraphQL as a mediator separating back and front end?
10:16:18 From Marc Pierson If “context is everything” apps are not the way to deal with everything.
10:17:03 From Jeff Miller "Currently humans are patching over the seams in the pattern of just downloading an app." - Eric
10:18:31 From Jeff Miller Marc observes the latent computational capability of FedWiki as a strong potential - having tools and data within a FedWiki which enable computation for neighborhood-level solutions. (data offered, processed, consumed) -- "That's a platform thing"
10:20:48 From Jeff Miller data as grid-shaped
10:21:02 From Brian It still might be fun to descend on Boulder or Portland for a 2 or 3 days of FedWiki brainstorming...
10:21:13 From Jeff Miller FedWiki data as not grid-shaped in order to avoid trying to compete with Excel and other spreadsheets (thinking of Fit as a grid layout tool, it was actually pretty good!)
10:22:54 From Brian To think about next version of FedWiki. 1) Retain backward compatibility, 2) Deciding on what the server object model API is. i.e. does the server maintain the journal state or does the client maintain the journal state. I think that would set one cornerstone for many subsequent choices and tradeoffs.
10:23:00 From Jeff Miller Zach observes, re being an early mobile developer before coming to web development.
10:24:09 From Jeff Miller "crossing the chasm from early adopters to pragmatists -- finding the narrowest entry point, the right tool in a very specific focus point -- hardware user groups, early in Apple's mobile dev history"
10:24:50 From Brian http://147.182.253.245:3000/juxtaposition-as-collaboration.html
10:25:08 From Jeff Miller How did the various distributed data sharing services and other Internet protocols get their entry point? (from Zach)
10:28:15
10:28:15 From Jeff Miller Ward relates a story on Flutter language promotion within Google, and talks about "consider the FedWiki json files, can you make that interesting and lively using Flutter?" - but a product mgr was not interested in something which touched the Web. (idk, it seems like Dart and Flutter could work regardless?) - JM
10:29:11 From Brian After figuring out the object api on the server, then the object naming strategy can be explored/implemented and then the rename page option would make sense.
10:29:19 From Jeff Miller (Zach continues to relate various mobile platform technologies) An interesting question is "here's a page with a name, but its twin page is a redirection to a renamed page" ?
10:30:46 From Jeff Miller Eric suggests: "build for old phones, 5 years old or more"
10:31:04 From Marc Pierson QR codes, photos directly into fedwiki.
10:31:06 From Jeff Miller aw geeze (to Eric's thought) my phone is a Pixel 3a, how old is that? it has a microphone / audio jack, super important feature
10:31:45 From jan dittrich (er/he|they – Siegen) Need to leave and have dinner! See you on matrix.
10:32:13 From Jeff Miller "5 years old, not supported by the phone manufacturer, so that mobile app development platforms may not support that phone" Mobile Web for the win, then?
10:33:34 From Jeff Miller "May 14, 2019" for Pixel 3a, says Gemini (or "May 7, 2019" lower down the page) the business model for sustaining a platform? (to Brian's thoughts)
10:34:43 From Jeff Miller no 10x growth to be had - what does sustainability work look like as a business model? (nodding to Eric's concurrence)
10:35:53 From Jeff Miller Investors prefer rate, return / time; Others prefer distance, rate * time "Move slow and make things (that last, together)" - Ward
10:36:56 From Jeff Miller "what have you DONE for us" vs. "what capabilities have you built and preserved?" (nodding to Eric)
10:38:37 From Jeff Miller resilience - so many things can damage roads; it's better to be prepared for whatever happens by re-routing and repairing, than trying to make a particular road to a five nines reliability (it's funny to me that cloud computing is based on the presumption that individual operations are fallible, but can be composed into reliable operations most of the time) Netflix and the Simian Army highlight that approach - and even so, it takes a big failure to catch the leaders' attention.
10:40:48 From Jeff Miller Marc reflects an observation of the Navy's carrier flight deck resilience study: 5-point scale as to likelihood and severity of an issue. industrial process safety and resilience has a lot of operational wisdom
10:42:30 From Jeff Miller "a CEO could understand the 5-point scale" make it part of incident response?
10:43:43 From Jeff Miller WyCash : 50% platform capability, 50% new features Eric hears: 80% features, 20% platform capability, resilience.
10:44:48 From Jeff Miller (guidance from the top of the org toward being able to seize new feature opportunity)
10:45:36 From zach I’ve pretty much come to the conclusion that new feature development in a software project that’s already profitable is misguided
10:46:08 From Jeff Miller future-proofing against one's competitors? (to Zach's point) Ward talks about quietly building for resilience and adaptability because of a common language from Smalltalk.
10:46:57 From Brian Flow based work vs interrupt driven work...there are 10 Flow based blocks available per week (the 4 hours before and after lunch each day). If there is an interruption in that flow based block, then throw out 10% of the flow based work productivity that week.
10:47:03 From zach yeah, what Ward just said. Focus on keeping speed up for responding to the needs of what already works, and if you want more money, build something new If there is an interruption in that flow based block, then throw out 10% of the flow based work productivity that week How ‘bout we throw a meeting in the middle of one each day
10:48:36 From Jeff Miller (I face a challenge as an effectively distributed team member in advocating for better practices)
10:49:02 From Brian Replying to "If there is an inter..." That gets you to 0% productivity, and seems to happen a lot more than one would think.
10:49:19 From Jeff Miller Replying to "If there is an inter..." um I kind of need the stand-up in order to get information flow Replying to "If there is an inter..." no ambient information flow since other team members are a little too quiet and are distributed
10:50:07 From Brian Replying to "If there is an inter..." If the standup is at the the beginning of the block and is short, then you *might* be able to recover the flow based block...If it goes long, then you might not get two blocks in one day.
10:50:33 From Jeff Miller Replying to "If there is an inter..." that's what pairing is for, to help recover flow and context; otherwise you checkpoint yourself by writing down a lot Replying to "If there is an inter..." (you = "me")
10:50:46 From zach Replying to "If there is an inter..." yeah, I’m a big advocate for standup abutting lunch if you’re all in the same time zone, or happening at the end of the day. Start of day might work, but programmers don’t like being told when to wake up lol
10:51:02 From Brian Replying to "If there is an inter..." It takes 20-30 minutes to get into "flow state" and the flow state can last 2-3 hours, where the large pay-off is realized. If you break the flow state, you have to start back up with another 20-30 minute get into it again stretch.
10:51:07 From Jeff Miller Replying to "If there is an inter..." I get flow in the evening
10:52:21 From Jeff Miller Marc: thanks for the Risk Assessment Matrix! "harmonica voice" digital distortion
10:55:27
10:55:27 From Jeff Miller A B C D, probablility, Likely, Probable, May, Unlikely; I II III IV, severity, Loss, Significant Degradation, Degradation, Minor Impact A x I, A x II; B x I are red 1 priority for risk prevention and recovery
11:00:24
11:00:24 From Jeff Miller Zach demonstrates a smart contract including a push / pull to Planet Nine for requesting a token exchange within FedWiki as plugin host.
11:01:07 From Brian Marick It’s that time, and AT&T wants me off the internet anyway. Seeya next time.
11:01:10 From Jeff Miller Marc reports a RenDanHeYi contract practice -the terms are adjusted every month rather than being anchored in the system rules permanently
11:01:40 From Paul Rodwell I need to leave
11:01:45 From Jeff Miller bye Paul!
11:01:46 From Brian Bye Paul. XP achieves some of that by making the "agreement" for the next two weeks and not for longer term than that.
11:03:10 From Jeff Miller Eric reflects on Procor's software supporting building construction; that the contract is renegotiated continuously through the process of planning, permitting, financing and building "You learn all of the ways that the design is wrong and you have to renegotiate the contract during the work." contractors, subcontractors, etc. A very adversarial business in large construction work
11:04:16 From zach Stacks
11:04:43 From Jeff Miller "How do we maintain a crew with capability to build things? That's a problem we've been solving for millennia." Marc observes that RenDanHeYi's frequent renegotiation is helpful for recognizing reality.
11:06:39 From zach jeff, what all’s on that shirt? awesome!
11:07:14 From Jeff Miller Amy Wibowo, better known as SailorHg cute and friendly approach to learning algorithms and computing practices
11:09:54
11:09:54 From Jeff Miller (the T-shirt is "Hello World" with a purple and yellow and pink motif with a Mac-like desktop background to the person at the Mac-like computer in the foreground)
11:10:20 From zach Reacted to "Amy Wibowo, better k..." with 💚
11:10:56 From Jeff Miller many micro-trust interactions (XP, frequent delivery, a habit of negotiating and realizing work) a healthy experience of TDD: frequent confirmation a healthy experience of DevOps: push frequently, rollback easily
11:12:15 From Jeff Miller rotating pairs: build team-based understanding via sharing information, building micro-trust at this scale (Eric) (my current priorities at work have the whole team pivoting toward a set of related features, and I so miss being able to whiteboard and pair on this)
11:13:57 From Jeff Miller (mgr is super reluctant at this sort of approach) Marc reflects on building a positive affective ratio: three positive affective strokes balances one negative stroke.
11:15:25 From Jeff Miller Marc observes that not all of these positive strokes have to be directly on the work task.
11:16:43 From Jeff Miller (talking to the engineering student who has arrived to have apple cake and milk for breakfast) "people need their basic needs met" - Brian, on the leisure to make voluntary social affiliations and work
11:18:00 From Jeff Miller My wife's mother; "We never felt poor, because we didn't have less than the neighbors, and we could rely on each others' help
11:20:06 From Jeff Miller "how you think is 80% environmental" -- Brian So: change the environment if you want to change perspectives?
11:21:10 From Jeff Miller big planning up front succeeded! (identifying risks and opportunities in a 10-yr plan, helping to build the environment aligned with the goals)
11:21:59 From Marc Pierson Zach, this may have been posted before you arrived: https://marc.relocalizecreativity.net/view/context-in-fedwiki
11:22:21 From Jeff Miller oh! Not reporting metrics in their terms, but reporting a story consistent with the org's priorities? "always have an impact story" "Provide a story for your boss to explain the work to the boss's boss."
11:23:31 From Jeff Miller "propagation of story to make the right thing happen in the environment" boss's boss's boss: 30-second summary (industry-standard robust cloud distributed platform...)
11:26:06
11:26:06 From Jeff Miller Eric recalls: thoughts are formed by environments have a story to tell up the change of command the story needs to survive going up the hierarchy, simple and direct that story justifies the resources for your work
11:27:09 From Jeff Miller Brian reflects: "low technology readiness level research is supported by A, B, C areas of work" "that's what we're doing to be well-situated in 10 years" "and so we need to keep making progress here"
11:28:46 From Jeff Miller Technology readiness levels 1. conceptual, inferential, back-of-envelope, white paper 2. expand simulation detail, more comprehensive analysis 3. field research and experimentation 4. more comprehensive field experiment
11:29:29 From Brian https://en.wikipedia.org/wiki/Technology_readiness_level
11:29:41 From Jeff Miller Brian's approach for these is about exploring concepts to reduce risk over time, things which might be risks and opportunities over a 10-yr scale.
11:29:42 From Brian https://api.army.mil/e2/c/downloads/404585.pdf
11:30:16 From Jeff Miller Low-TRL: conceptual treatments at TRL 1 of various risks, opportunities, techniques "doing spikes, in a research context" "A great idea, but it would take millions of dollars to take it to the next level - keep it on the shelf."
11:31:25 From Jeff Miller casting a wide net for concepts and puzzle pieces to help build next year's roadmap Key Result: number of conceptual ideas rejected? (are we casting a wide enough net?)
11:33:29 From Jeff Miller stock downside risk blinds business leaders to longer term opportunities?
11:39:28
11:39:28 From Jeff Miller I recall the canals of Dublin were filled, not insignificantly because of the risk to children and others. (makes me wonder about Amsterdam and canals) Eric shares the Naval Safety Centry Risk Assessment Matrix
11:40:29 From Jeff Miller Probability: not numbers, human judgments Respects expertise of people in the field. Severity in terms of the Effect of Hazard
11:41:43 From Jeff Miller Loss of: Capability; Readiness; Asset; Death (level I) "can you be responsive to the mission? I is risk to mission" II is degradation of mission readiness III is degradation of mission capability or unit readiness IV is minor impact, minimal damage
11:42:53 From Jeff Miller Ward: "It's forward-looking, will be be able to do our job based on the severity of the incident?" Eric reflects: software systems tend to be backward-looking and numbers-focused.
11:44:52 From Jeff Miller <3 for the Naval Watch Officer's Guide as being focused on transferring operating context, watch by watch, knowing when to escalate, following procedures to avoid risk of loss. Marc observes: do they take the risk matrix up the hierarchy? Eric says: You should be able to use that matrix at all levels. Marc observes: but does it go up the hierarchy as a way of thinking?
11:47:32
11:47:32 From Jeff Miller "tell stories and do things that align your work with the culture of the hierarchy" if you can't change your organization....
11:51:43
11:51:43 From Jeff Miller Brian reflects on a talk format from Ward - open a Word document, write down a couple of interesting topics, and expand on them (xpdx talks) - Ward reflects on this style as one used by the original Mac introduction, turning a set of topics into a story. "We had a broad understanding of the parts of the problems; I had background to sew the topics together."
11:52:48 From Jeff Miller Good for addressing people who have a lot of the expertise; you can use this topic format to make the connections among the parts.
11:54:04 From Brian https://en.wikipedia.org/wiki/Ishikawa_diagram can work well for some kinds of information and through line
11:54:16 From Jeff Miller Ward reflects on Brian Marick's podcast form - that there's a space for wandering around, but a shape to pull it back into a story. It's like a movie, where there are expectations for the arc of the story. Sunday calls: associative memory topic and explorations observation / explorations, observation / explorations; let's do a demo!
11:55:39 From Jeff Miller I guess I'm on deck for notes because Paul has had to go. Brian asks about Ward and Eric's work since last time. Ward's talk is coming together well, the first couple of slides express the important things; partly related to Mehaffy's work.
11:57:31 From Jeff Miller Eric gave a talk to a set of grad students, and observed how the talk didn't meet them where they were; but it was good practice for Domain Driven Design Denver in a month; they may be more familiar with the way of understanding DDD as a pattern language, and that will help as a format for the talk. a resilience pattern language? "the journey of discovery is not useful to an audience focused on applying the technique"
11:59:35 From Jeff Miller "sometimes you have to feel the thing to take the wisdom in"
12:00:57 From Jeff Miller mine is coming up, and my boss and I disagree on fundamentals (perf eval season) arrrgh!
12:02:18 From Jeff Miller "it's only five hundred words!" the proof won't fit in the margin / it's a long letter because I couldn't spend the time to make it shorter / the positive and negative strokes ratio
12:05:10
12:05:10 From Jeff Miller "the biggest challenge is understanding what your people do" (mgr's side of perf reviews) -> therefore, make your mgr's job easier
12:07:01 From Jeff Miller ...by writing your self-evaluation in a way that makes it easy for the mgr to copy/paste
12:09:10 From Jeff Miller "why aren't you moving tickets faster?" "why aren't you better at estimating?" "why do you keep getting stuck in ops support?"
12:12:40
12:12:40 From Jeff Miller Marc mentions and asks permission, on the Sunday calls, to bring a few plug-ins, turn on "record", and share screen to get help understanding how to learn, use, and master the pliug-in. that would benefit me! - Jeff a plug-in of the week, to keep and review and revise
12:13:55 From Jeff Miller do it at the beginning of the second hour Brian compliments Marc for doing something that was a little bit vulnerable, in making his request.
12:15:16 From Jeff Miller Ward responds that it was a well-formed request, with a time-bounded and specific request for recording, allowing the rest of the meeting to be more open. failure as a colleague, if not a friend