badoongi

4 ms·

1.
by badoongi 2y ago
Nice, this somewhat reminds Apportable: https://www.ycombinator.com/companies/apportable
2.
by badoongi 2y ago
I've been working through a legacy starlark codebase recently. My take is that the language, and the bazel phased execution model, makes it very challenging to debug. One example: as far as I can tell there is no way to get the Starlar
3.
by badoongi 3y ago
Fascinating project! I'm curious what's the business model? it's listed on Crunchbase that you raised 12M$ so I'm assuming you do have plans to make money?
4.
by badoongi 3y ago
I see testcontainers being used in tests making the test code style feel more like typical unit tests with fake implementations for system components. Which is misleading as these are more on the integration testing side typically. In essen
5.
Evo: Biological foundation model that generalizes across DNA, RNA, and proteins(arc-website-git-foundation-model-tool-arc-institute.vercel.app)
5 points by badoongi 3y ago|0 comments
6.
by badoongi 3y ago
This is also their 25M$ series A announcement coming in 10 months after their 10M$ seed
7.
OpenAI API usage monitoring in Datadog(datadoghq.com)
1 points by badoongi 3y ago|0 comments
8.
by badoongi 4y ago
Often when it's mentioned it's treated as a hard rule, claiming semver has no justification as any change is a breaking change. Though in practice most software packages are not used extensively to the point that any observable b
9.
by badoongi 4y ago
> I can run our entire backend with a single command that will work on any developer's box. Curious wouldn't `go run` give you the same? pure go code is supposed to be portable, unless you have cgo deps I guess? > I can push
10.
by badoongi 4y ago
My take - Avoid Bazel as long as you can, for most companies the codebase is not big enough to actually need distributed builds, if you've hit this problem Bazel is probably the best thing you can do today, if you're that big you