noahdesu
Joined 17 years ago
Karma
369
Submissions
153
Member since
Aug 14
https://makedist.com
View on Hacker NewsRecent submissions
Comment · 6 years ago
Worked on a project with similar goals [0]. By no means a production level implementation, but much of the system exists as a proof-of-concept.
Comment · 6 years ago
I can sympathize with this take. Although I'm generally fine with either async or sync--whichever is most efficient--it seems that individuals don't usually know which is right for them.
Comment · 6 years ago
I'll take this further: I think that bad commit messages breed resentment. It's highly context dependent, but needing to understand some code and its historical context is already a big challenge. git-blaming your way back through time only to encounter brain dump commit messages full of ambiguity and non-essential information is excruciating. Writing good commit messages--like any technical writing--is more art than procedure, and it's hard to do well without feedback and revision. I believe that commit messages should be subject to the same level of review as the code they are presumably documenting.
Comment · 6 years ago
This is such an important feature that has a direct impact on code quality and time savings that I'm not sure why it isn't a priority feature. As a reviewer, having to choose between "review everything again" or "trust the submitter didn't introduce extra changes in the revised pr" is such a terrible choice to have to make.
Comment · 6 years ago
Migrating away from a development model based on attaching patches to bugzilla tickets is sure to improve the development experience, especially for new contributes. Good move switching.
Comment · 7 years ago
This sounds really similar to some of the work coming out of Vectorized on Redpanda [0]. They're building a Kafka API compatible system in C++ that's apparently achieving significant performance gains (throughput, tail latency) while maintaining operational simplicity.
Comment · 7 years ago
I'm working on Rook+Ceph at Red Hat. Rook 1.0 was just released last week which added support for the very latest Nautilus release of Ceph.
Comment · 7 years ago
If you are thinking about starting a Seastar project, definitely check out SMF [0]. It's a highly optimized RPC framework that uses Seastar, and makes it easy to build high-performance servers and clients. Seastar itself is RPC agnostic, and this project has a great implementation of functionality most developers will eventually need.
Comment · 7 years ago
In the latest release (0.9) Ceph in Rook has been declared stable.
Comment · 7 years ago
This seems to serve a purpose similar to Rook [0] for deploying distributed (or non-distributed) storage systems, including database. For example, Rook can deploy CockroachDB and also Ceph, which would have a lot of the same challenges as deploying some of the databases supported by KubeDB.
[0]: https://rook.io
disclaimer: red hat employee working some on rook.
Comment · 8 years ago
Been using the cloud native version for about a year now, and I'm debating if I should renew. What are you using now if not YNAB?
Comment · 8 years ago
the experience you have described that occurs after about 2 weeks is a very distinct state of mind. I find that I can to a certain extent reliability reproduce it (1) whenever I have a deadline and I'm procrastinating, (2) occasionally after smoking some marijuana (3) and on long distance runs.
Comment · 8 years ago
This is the type of project announcement that gets me excited to work on my own open-source efforts. Congrats Drew, this is great.
Comment · 8 years ago
Thanks. Our team is also remote, so we don't use whiteboards for collaboration. It seems like, at least here in SF, every room in any company that I go to has a whiteboard. One might then conclude they are indispensable, but I would really like to figure out how to put a number on it.