Thinking in Events: From Databases to Distributed Collaboration Software [video]

I believe we retained Martin as a consultant for a time, so next level up from video watching. But: there are all of the above (organized initiatives, informal propagation, top-down edicts). But group video watching would be unusual. Typically these days there's a slack channel where it is encouraged to post things like this.

We have a dedicated slack channel and weekly meeting called AV Club - you watch the selected video on your own time and discuss at the meeting or in the chat.

At Amazon there are “principal of Amazon” talks every few weeks which broadcasts to the entire company. My previous team has regularly watching party for the most popular talks of all time - they are all super useful. There are many big names among the presenters

I read the DDIA book in my own time and have watched some of the internal Amazon tech talks mentioned above during work time with other engineers.

I think either way it’s important to realise that unless you’re superhuman you’re not really solidifying the knowledge, you’re making yourself aware of the concepts. If a use case comes up that requires it you have a better chance of recognising that and then going back and getting a deeper understanding of how to apply it.

I only absorbed a small fraction of DDIA but I still think reading it was invaluable.

In my Fortune 500 employer, we have pan-regional task forces/committees people can join for collaboration like this. I'm on the Engineering Training Taskforce in my region. We meet an hour a month to plan various events, including "Tech movie nights". Pre-COVID we'd get upper management to approve a small budget for popcorn during movie showings, etc. We also have a few (infrequent) long-running series of invited talks on a theme.

Follow-up discussion from earlier in a series is good, but you need it to not interfere with people being able to selectively attend events. Presumably, you'd want to budget some time after the video screening to discuss the just watched movie, followed by some budgeted time for discussing the previous video. If you start out with discussion of the previous video, you're going to scare off newcomers. Or, you have a Slack channel (or similar) for the series and have drawn out asynchronous discussion.

At least until you have critical mass, you need your series to be like an easy-watching low-context series with relatively self-contained episodes. Think The Simpsons instead of something that really requires investment to keep up with the context, like Game of Thrones.

Being on a taskforce/committee does take extra time and effort, but does show initiative and can get one valuable exposure/mindshare from upper management. At least in our organization, cross-team collaboration looks good at annual review time.

I read the DDIA book in my own time and bought it myself. It probably would be possible to get these kinds of books bought by the company and read them on company time if there is some important enough thing to learn. But I never made use of it. The way I read books you can tell I read them because they have marks everywhere. We do have initiatives to learn from each other, but the days are already filled with too much unplanned work and meetings.

There's an innovation day every 2 weeks where you work on your own projects within the company.

If it's good or a considerable effort to implement, it can become a work item after approval.

We also have tech talks to share knowledge about what you want/experienced and even industry speakers. After tech talks, a small group of interested people can form in a dedicated channel.

We try to use a Community of Practice framework, e.g. https://en.m.wikipedia.org/wiki/Community_of_practice. Active members of a CoP might then decide to set up a book club etc.

It's quite easy to draw a line from org principles ("we're always learning" etc) to active participation in a CoP, so helps align incentives on a team level (we can spend time on things outside of our immediate needs) and an individual level (it's an obvious way to get performance review evidence)

Hello, Martin here :) I use the Paper app (https://wetransfer.com/paper) on an iPad, then transfer the images to a computer, do a little post-processing in Gimp and ImageMagick, and then drop the images into PowerPoint. You might be able to present directly from the Paper app, but it's more designed for drawing than for presenting.

"Data flow programming paradigm" would be one term that describes the architecture for such a system. It is more general but if each node in the graph emits output only if novel input is received then one gets idempotency.

A Makefile (ie, for the "make" tool) or any of the similar build systems implement this pattern using file based data exchange (DFP graph edges) and graph nodes implemented as processes.

Metamine is an experimental language that supports both reactive and procedural programming modes at the same time.

Here's a previous thread about it - https://news.ycombinator.com/item?id=27555940

Fwiw this is the core concept behind React, and it is approached in a nice way there as far as my opinion goes. I'm unclear about general purpose programming languages but seems like other comments have good suggestions

Adapton falls in this category of incremental computing. http://adapton.org/