I have a new keyboard. It’s a ZSA Moonlander, so it’s a split keyboard and has a QWERTY layout. This is how my desk looks now:

Learning that new layout is hard, and so I’m the slowest typist I’ve been in years. But it’s getting better 🙂

Thesis-wise, this week was all about the Interviews I did with NetCheck. I learned these main things:

• different people need different documentation styles. While Jeremias is fine reading source code, Sten preferred a PDF or HTML report,
• to signal which expectations are critical (as in: failures should halt execution) vs relaxed (should warn, but not halt), Jeremias had the great idea to use should/must vocab as used in RFCs
• Steven noted that he’d be interested in a tool that evaluates specific KPIs externally. “datadog for data monitoring”, basically. I’ll think about that.
• all three could imagine using the tool I’m building :yay:

Result of Jeremias should/must suggestion, I’m making the following change to the API design:

# old
income_datafox.salary.expect_normal(alpha=0.05, critical=True)

# new
income_datafox.salary.should.be_normal(alpha=0.05)
income_datafox.salary.must.be_normal(alpha=0.05)

I then followed up on this by getting some rough integration with Jupyter Notebooks going. See this screeencast for an introduction:

https://www.loom.com/share/51362432bc99410c8f7f3bf0e9a532c7

Next Week, I’ll most likely continue fleshing out the prototype, and do some more brainstorming around branding.

That’s it for the week. Off to friday beers (organised by us, drop by!). Have a wonderful weekend y’all! Simon