the standup is a tool to help keep the team moving, and surface issues early. a good use of the standup is asking for help on a task that is taking longer than expected. often, people underestimate the time a task will take. ultimately the tasks need done. “small easy tasks” that are not A and not B represent distractions.
There is already much user demand & vendor support for running virtual machines (including for Windows) on Apple hardware, through Parallels, VMWare and Qemu.
Like there are options for containers, it is great to have another option for virtual machines.
from the video description: The Chicago and Sanitary Ship Canal is the path that invasive carp would take to reach the Great Lakes. So to stop them, the US Army Corps of Engineers has installed an electric barrier.
Did you consider leveraging buildbot (buildbot.net) when writing your infrastructure? It has some features that should be helpful.
I'm currently setting up a ci/cd build infrastructure for myself. While I've been exploring different ways to perform the build/test cycle, I expect it will be beneficial to wrap the whole thing in buildbot in the end.
Cool! I have implemented a similar workflow (certificate signatures as authentication) for some backend processes. No public write up currently. Certificate based authentication usage will only increase with time, imho
I understand that concurrent edits to the ledger will become problematic. If this really is a requirement, a distributed ledger solution (cloud based tool) may be needed
Though is the root issue just communication? At some point transactions need:
1. Recorded
2. Categorized (optional, but desirable)
3. Reconciled (This can only happen as often as bank statements are issued)
With multiple spenders, communication (to answer the question "what is this transaction for?!?!") is paramount and fits naturally at the reconciliation step or more frequently if desired.
The workflow described is synchronous, centralized and simple