We're working on this indirectly by building systems to increasing the productivity of our machine learning team and reduce distractions and context switching. There are a <i>lot</i> of distractions when you do machine learning projects. The nature of the beast involves several people with different skillsets optimizing for different things and "speaking different languages".<p>This creates a lot of "taps on the shoulder": a Phd tapping on your shoulder to set up or fix their compute environment, or to get them data, or to deploy their model, or to make a temporary application to show results to a client and make it available "on the internet" behind authentication.<p>A developer who wants to use a model in an application being dragged into the ML realm when they only want to <i>use</i> the capability of the model, not get intimate with its dependencies and setting it up.<p>Ad-hoc experiment tracking schemes in spreadsheets, logs, physical notebooks, emails, verbally, and "in my head" that made it almost impossible to know what we did a couple of months ago, or <i>why</i> we did it, or what worked best, etc.<p>The fact that people needed to know a lot of things about a lot of tools in order to make things work put a lot of stress and overhead to do any work.<p>So we created our internal machine learning platform[0] to remove as many friction points as possible. Basically, we try to make everything that sucked the responsibility of that system, while maintaining flexibility, as one of the reasons we built our own is that we found the other offerings trying to force us into what they consider to be "The Right Way" or a rigid pipeline, or having to pollute our notebooks with their SDK that tied you to their stack/infrastructure instead of relying on APIs or protocols.<p>We'll allow notifications and events at some point, but we'll leverage what the users are already using instead of adding yet another distraction channel. For example, we'll enable webhooks and integrations so if people are using Slack, they can tie it to the platform to be notified when a training job's status changes in Slack, rather than asking to enable notifications. If they're not using that, they can tie it to their other systems and do things programmatically, for example. We're very sensitive about these topics.<p>The result of this is what we've been working with clients without tapping on our colleagues' shoulders for a <i>lot</i> of things, and letting them focus. This is really important as all these interruptions and "urgencies/I need it for yesterday" can devastate a team or a company, push people to quit or burn out, etc.<p>- [0]: <a href="https://iko.ai" rel="nofollow">https://iko.ai</a>