aswihart

7 ms·

1.
by aswihart 7mo ago
> Dependencies should be updated according to your development cycle, not the cycle of each of your dependencies. For example you might want to update dependencies all at once when you begin a release development cycle, as opposed to wh
2.
by aswihart 2y ago
Figuring out whether the upgrade is safe is a hard problem. I've found renovate most successful in frontend JS projects where you have a ton of dependencies all with new versions coming out all the time, most of which are non-breaking,
3.
Show HN: Gemcompat, an open source db of undocumented rails incompatibilities(github.com)
7 points by aswihart 2y ago|0 comments
4.
AI-Assisted Dependency Updates Without Breaking Things(thenewstack.io)
1 points by aswihart 3y ago|1 comments
5.
by aswihart 3y ago
hey all! for anyone interested in open source, my team just launched a substack called Once a Maintainer. Each week we interview a maintainer and ask them about the work that they do. We're trying to bring a more human, storytelling el
6.
Into OSS? Suggest maintainers for us to interview for our Substack(onceamaintainer.substack.com)
2 points by aswihart 3y ago|1 comments
7.
by aswihart 6y ago
lol yeah we need more Juiceros
8.
by aswihart 6y ago
- don't talk over women in meetings - don't ask women to do informal "secretarial work" for the group, e.g. note-taking, summarizing meetings, ordering the Christmas cards, buying birthday presents, ordering furniture -
9.
by aswihart 6y ago
Congrats on the launch! Beautiful site. I'd like more info about how you ship the art before buying. I found your FAQ after a little digging, but it didn't really give me comfort that you ship using a method that is particularly s
10.
by aswihart 7y ago
I missed this comment earlier - we can pilot with sample/fake data to give the user a sense of how the system works and what workflows within it work best for their company. The versioning/diffs wouldn't make much sense, but
11.
by aswihart 7y ago
Interesting, I just came across Frictionless recently as part of the FISD group that's trying to implement a set of standards across the financial industry for documenting datasets.
12.
by aswihart 7y ago
We actually built in the concept of "display names" for exactly this purpose. You want to keep the actual field name in the schema so that ingestion works properly, but you also want to describe the field as helpfully as possible.
13.
by aswihart 7y ago
We would love to do that at some point. There is tons of open data out there, but not a lot of it has useful descriptions at the field level (only the dataset level), so it would take some time to put a collection together that is robust. A
14.
by aswihart 7y ago
This made our day : ) Thank you!
15.
by aswihart 7y ago
We think data-as-a-service is a new and growing category, and this includes startups we would consider "pure" data companies (e.g. a company that sells data on airfares across the web) and companies that have been around for decad
16.
by aswihart 7y ago
(This is Allison) - thank you! It's interesting for us to see how the problem is handled at different types of organizations, because as you point out the data team knows the underlying data best but is not often customer-facing.