Show HN: dk
organize and document command line tools for ease of discovery
organize and document command line tools for ease of discovery
https://github.com/hq6/ProtobufJson
Simple wrapper over the Protobuf C++ API for converting back and forth between JSON and Protobuf.
I built it a few months ago, and my team at Square has been using it to save time during both development and debugging when interacting with gRPC and proto-over-http servicse defined in protobuf.
If you use protobuf-based services, please feel free to play with it and let me know what you think!
There are two contexts I'd like to consider.a) When COVID first broke out, many companies moved to remote work. If your company did this, how did you measure productivity before & after the shift to remote work?b) A few companies have done trials of a 4-day workweek and claim that productivity increases. If your company was to do such a trial, how would you measure it?
In OSDI 2016, Google published a paper describing Slicer, a system to make it easy to build stateful applications by solving the distributed problems associated with sharding applications.https://www.usenix.org/system/files/conference/osdi16/osdi16-adya.pdfMy current team at Square is building a (simplified) clone of Slicer to simplify feature development, improve load balancing, and reduce...
I completely agree that people in most companies do not push down P99 enough.
I think this is a direct response to the second question, and assumes that people are setting timeouts statically. Is my understanding correct?
There are two sub-questions here. 1. Is the same timeout T set for every instance of service X making request A to service Z, or is a timeout chosen at runtime? 2. How is the static (or dynamic) timeout value chosen?As a clarification, this is more of a poll to understand what people are actually doing, rather than a request for recommendation on what I should do. If you are willing to state...
However, to make the institutional knowledge useful, it must be easy to find. Thus, I think the second most important thing for capturing institutional knowledge is to have a small number of easily searchable places where documentation lives. Markdown files in the source are convenient place for documenting particular projects or code, but more general-purpose knowledge should be in a wiki or any other document store that is centrally searchable and update-able. An example of such general purpose knowledge is "how-to knowledge": How do I request the appropriate privileges to integrate my service with Service X? How do I make and deploy a staging build? How do I set up a new service?
Another sort of general-purpose knowledge that should have a single home is knowledge around context for past decisions that were made for good, but not obvious reasons. My team maintains a document called a Decision Log, where we record the context around and reasons for every decision that required more than roughly 10 minutes of thought. Longer decisions have their own docs, but they are linked from the central Decision Log.
Last year, Intel announced that they were deprecating CilkPlus, and would remove it from their development kit in a couple of years. However, no reason was given for the decision.Does anyone here have thoughts or information on why this happened? Was there something about the technology that was fundamentally limited?
The API is to shorten is simply a POST request to hq6.me/u/ with `fullUrl` and optional `desiredShortUrl` as parameters.