So often, these tools lack usability because they’re built generically any use case. Here, it was designed for your wife’s bakery.

The process to build a site/app like this will only get easier and more defect-free over the coming months.

Great project.

[1] https://news.ycombinator.com/item?id=44358482

The counter example is the language Go. The team running Go has put considerable care and attention into making this project welcoming for developers to contribute, while still adhering to Google code contribution requirements. Building for source is straightforward and iirc it’s one of the easier cross compilers to setup.

Install docs: https://go.dev/doc/install/source#bootstrapFromBinaryRelease

Hot shard management is a job in of itself and adds lot of operational complexity.

One major problem with tools that ask crafters to do data entry to show their value is that best people are most likely to refuse. You really need to focus on tooling to help capture what’s going on without toil.

For example, if your folks are remote and they use software to aid in pairing (eg Tuple), script the system to log the tuple sessions and perhaps even capture the pairing in the commits made together.

This can be used as an input to bring visible to be best leaders in your org.

https://data.firefox.com/dashboard/user-activity

https://kamal-deploy.org/

I’ve tried a few other approaches in the past and this seems like the simplest, given a familiarity with git.

[1] https://kamal-deploy.org/

Combined, hardware is finally approachable down to the gate level, even when modern systems add many layers of abstraction.