Systems/Infrastructure software at various layers.
Previous work: cohesion.dev, fission.io, filesystems at VMware.
Generally: interested in the systems of change in software and people.
Specifically: working on developer tools at Stripe.
[email protected]; no sales pitches please but I'm always interested in grabbing a coffee and talking about developer tools, infrastructure, or startups!
投稿
Show HN: Cohesion: Build serverless workflows in Python
preview.cohesion.dev
1 ポイント·投稿者 soamv··2 コメント
AWS Managed Workflows for Apache Airflow
aws.amazon.com
118 ポイント·投稿者 soamv··67 コメント
Cohesion: Rethinking Workflow Development
cohesion.dev
2 ポイント·投稿者 soamv··0 コメント
AWS Savings Plans: New AWS cost management feature
11 ポイント·投稿者 soamv··1 コメント
The war for the soul of open source (video, OSCON keynote)
youtube.com
7 ポイント·投稿者 soamv··1 コメント
10x Engineer == Management Failure
soam.dev
6 ポイント·投稿者 soamv··0 コメント
Automated Canary Deployments in FaaS on Kubernetes
blog.fission.io
3 ポイント·投稿者 soamv··0 コメント
Your Job Is Political: Tech Money in Politics
nerd.kelseyinnis.com
2 ポイント·投稿者 soamv··0 コメント
Container Orchestration Tools: Compare Kubernetes and Mesos
platform9.com
1 ポイント·投稿者 soamv··0 コメント
Show HN: Glimmer, a Simple Private Ad-free Photo Sharing Service
glimmer.cc
3 ポイント·投稿者 soamv··4 コメント
Computer Swap on Curiosity Rover
jpl.nasa.gov
2 ポイント·投稿者 soamv··0 コメント
Typeface As Programme
typotheque.com
2 ポイント·投稿者 soamv··2 コメント
A retrospective on Transactional Memory
bluebytesoftware.com
3 ポイント·投稿者 soamv··1 コメント
Rescue robots deployed in Japan earthquake ops
news.cnet.com
4 ポイント·投稿者 soamv··0 コメント
Host Your Static Website on Amazon S3
aws.typepad.com
315 ポイント·投稿者 soamv··92 コメント
Anniversaries & Ideologies
tbray.org
3 ポイント·投稿者 soamv··0 コメント
Your Smartphone’s Battery Gauge is Lying to You (and it’s not such a bad thing)
This is a great point! But there's an important tradeoff here about human engineering time versus the "learning in the open" benefits; a PR discarded privately consumes no human engineering time, a fact that the humans involved might appreciate. How do you balance that tradeoff? Is there such a thing as a diff that's "too bad" to iterate on with a human?
This leaves me with more questions than answers, how did these three companies come up with the idea of using that logo? Did they just independently arrive at same design (seems unlikely)? And how did the trademark registration process go for the second and third companies that registered it?
It might have, I remember attending a talk by Peter Chen when I was at VMware around that time, and I know there was some kind of collaboration. (I wasn't involved in record-replay at VMware, but I was interested in it due to some ancient work I did with userspace record-replay debugging, https://lizard.sf.net).
rr is fantastic work, mad props! And the multiprocess stuff in pernosco looks super neat.
Maintainers do not owe you this, in addition to maintaining the software that you can use for free. You're entitled to be upset, and they're just as entitled to say "please go somewhere else to vent, we're busy".
Well, it may be legal to create such a painting, but (depending on details) it may be a derivative work, in which case the original work's copyright still applies.
In other words, in your example, the painter is not necessarily free to distribute their painting while ignoring the original image's copyright.
People here testing out the example on this page and reporting errors seem to be missing the fact that this demo is "trained" on one example. The linked paper[0] goes into error rates, and they get better pretty quickly with a few more examples.
They are privately operated since the 80s, but the vast majority of their initial development was government funded.
As far as I understand the privatized companies are monopolies-- these companies were formed from the JNR by geographic area served (hence "JR East", "JR West" etc.)
Previous work: cohesion.dev, fission.io, filesystems at VMware.
Generally: interested in the systems of change in software and people.
Specifically: working on developer tools at Stripe.
[email protected]; no sales pitches please but I'm always interested in grabbing a coffee and talking about developer tools, infrastructure, or startups!