lewq

10 ms·

91.
by lewq 7y ago
Hey Lukas! Love your work on wandb and very keen to find ways to integrate/collaborate :)
92.
by lewq 7y ago
To be clear, that primitive is dotmesh and ZFS - see https://dotscience.com/technology/
93.
by lewq 7y ago
I will take a look at that and whether we can integrate with it, thanks for the tip! What do you like about it?
94.
by lewq 7y ago
Hmm interesting, what if you had database snapshots that could be driven by ML workflows? The primitive behind Dotscience can support lightweight database snapshots quite easily...
95.
by lewq 7y ago
I agree that there should be open source solutions and the core of Dotscience is a project called Dotmesh ( https://github.com/dotmesh-io/dotmesh ) which is an open source wrapper around ZFS. You can see more info about
96.
by lewq 7y ago
Thank you! I am very interested in finding open source and/or non-platform ways to deliver the solution to the community. I know how off-putting 3rd party platforms can be. That's why I put the word "tooling" on the prod
97.
by lewq 7y ago
Yeah, sorry for the ad but us startup founders have to launch our products somehow :) That makes sense about saving the model info to git, but how do you track the provenance of the data? Do you see that as being important? (e.g. to track b
98.
by lewq 7y ago
Yes, exactly. And in particular, capturing those variables at the point of the run , not just some time before/after when you remember to record it manually. Lots more detail here: https://dotscience.com/product/
99.
Run tracking liberates ML teams(dotscience.com)
35 points by lewq 7y ago|23 comments
100.
by lewq 8y ago
https://twitter.com/lmarsden/status/988647228817461248?s=19 > real humans with lives are welcome to join our startup where we understand that your life is about more than work. > mothers welcome, myself i&#x
101.
by lewq 9y ago
Looks a lot like http://github.com/weaveworks/flux which we're happy users of at dotmesh.com. Glad to see gitops getting some traction! https://www.weave.works/blog/gitops-operations-by-pull-r
102.
by lewq 9y ago
I was pleasantly surprised how quickly we converged on these principles. I've worked on teams before where some of these items took months of debate! In particular, only doing code review if the author wants one really demonstrates how
103.
Commit directly to master. Dotmesh engineering principles(dotmesh.com)
1 points by lewq 9y ago|1 comments
104.
Capture the state of many μ-services' DBs in a single commit(dotmesh.com)
1 points by lewq 9y ago|0 comments
105.
Using dotmesh to commit container volumes like git(dotmesh.com)
3 points by lewq 9y ago|0 comments
106.
$10M Seed Round to Solve Cloud Native Data Management with Git for Data(dotmesh.com)
3 points by lewq 9y ago|0 comments
107.
by lewq 9y ago
Code at https://github.com/dotmesh-io/dotmesh :)
108.
by lewq 9y ago
I love your thinking, Ivan! We have an issue for this here: https://github.com/dotmesh-io/dotmesh/issues/85
109.
by lewq 9y ago
How would you want merge to work?
110.
by lewq 9y ago
Interesting! We should compare notes! Join our slack (in website footer) and we can chat? Or I'm @lmarsden on Twitter :-)
111.
by lewq 9y ago
Did you run the curl command that's the first item in the tutorial?
112.
by lewq 9y ago
Thank you for the great feedback! 1. We mention encryption in the docs FAQ https://docs.dotmesh.com/faq/#what-do-you-encrypt -- where did you look for it? Maybe we can make it easier to find. Noted about this being a p
113.
by lewq 9y ago
Try dotmesh here: https://dotmesh.com/try-dotmesh/ Learn about architecture, use cases (tutorials) & lots more: https://docs.dotmesh.com
114.
by lewq 9y ago
Hey, thanks for the feedback! Does this help? https://docs.dotmesh.com/concepts/architecture/
115.
by lewq 9y ago
Nice! (Non snarky question) does that scale?
116.
by lewq 9y ago
Interesting feedback, thanks. I agree that the git CLI is confusing, unfortunately it's the best thing we've got that a huge number of developers are familiar with for exploring a state tree with branches and commits. If you'
117.
by lewq 9y ago
Hey! Yes, it's hard to capture the state of VMs. This is where the Docker and Kubernetes integration comes into play -- if your app is captured entirely in Kubernetes manifests, the only thing left to capture (apart from the declarativ
118.
by lewq 9y ago
ClusterHQ was a fantastic learning experience. I'm proud of what we achieved and the many strong relationships that were built in the team. Ultimately the reason that ClusterHQ failed, I think, was that we believed we had product-marke
119.
by lewq 9y ago
Together with Solomon and a core group of maintainers, we drafted some words to clarify the relationship between Moby and Docker at the Moby Summit here at DockerCon. We're updating the website at mobyproject.org to include this text a
120.
by lewq 10y ago
This post makes an excellent point. I've been bitten both by not enough automated testing when a product has traction, and by spending too much time writing automated tests for a product without sufficient traction. Carefully treading

More ›