We did our next loglines session at @TerminusDB, since we're almost done with Episode 4, we did the next iteration of planning, refining the requirements for Episode 5 and breaking them down as Spoiler Titles for our backlogs. Our board looks quite messy, but this is actually a sign of maturity, since we "know the drill" thus our @MURAL kind of looks like our walls would if this was an in-person workshops. Not as perfectly curated as recent online sessions that require more perscriptive facilitation

I come across the advice to have a "camera on" rule for online meetings all the time. I really dislike this rule.

Cameras have their place, but the idea that you can effectively measure engagement via the camera isn't true. Measure engagement by *participation* not surveillance There are many reasons to not use a camera, but to me the most import is that you should be using real-time tools like @MURAL or @milanoteapp to collaborate, and I would rather have the participant's eyes on these these tools, rather than on the video gallery.

who wants to start an online tech conference in an old-skool text MOO? At @TerminusDB we just did on online conference, there was a lot that was cool about, like virtual booths, etc, but the tech was cumbersome, weird web 3d stuff, the awful go to meeting and crappy slack channels. Made me remember building cool stuff back on ChibaMOO

So, the loglines workshop for product design worked out even better than expected.

Here are the loglines that my team at @TerminusDB created as product ideas for upcoming iterations.

https://twitter.com/dmytri/status/1306744137497149441

Using loglines as a format works very well for design because it encourages a user-centric view with a protagonist, a goal and an obstacle, and of course fits nicely with our "spoiler titles" style of backlog item writing.

Another awesome @TrySpeakeasy Brainstorming session with @TerminusDB today.

Here is our board from today. This technique really works, here is how to run your own.

1. Create a list of "how might we" questions for your brainstorming.

A thread about icebreakers.

So, everybody is complaining about online meetings, I've posted my presentations and board templates already, but one thing that people neglect is icebreakers.

#agile #meetings #suddenlyremote People think that because these are internal meetings, that icebreakers are not required, after all, well know all know each other.

However, the point of icebreakers is not necessarily to get to know each other, but get everyone loosed up and talking.

Continuous Everything as Code as a Twitter Thread

Managing Databases in a CI/CD pipeline is a nightmare. Migration scripts are better than making changes on running servers, but become hard to manage in complex modern pipelines. Truly solving the problems requires revision control for databases so that you can clone, branch and merge your database.

So, @lukefeeney tells me people are struggling to access local files with @TerminusDB, so I added a feature to make it easier in terminus-quickstart ...

[thread]

If your container is running stop it with:
./terminus-container stop set the TERMINUS_LOCAL environment variable to the path to the parent directory of your csv:
export TERMINUS_LOCAL=/home/me/somewhere

then start your container again:
./terminus-container run

now, instead of .remote() is file, TERMINUS_LOCAL will be mounted as /app/local_files

@agentdeclan Though I've longed suspected, I'm only starting to full realize how deep it goes, happy to unpack a bit, with the caveat that I'm thinking out loud, so may tap dance a bit as I organize my thoughts here. @agentdeclan Let's start with this passage from Mao that I've quoted before: