Probably one of the easiest things you'll ever do with gpg
Install Keybase: https://keybase.io/download and Ensure the keybase cli is in your PATH
First get the public key
keybase pgp export | gpg --import
Next get the private key
Mute these words in your settings here: https://twitter.com/settings/muted_keywords | |
ActivityTweet | |
generic_activity_highlights | |
generic_activity_momentsbreaking | |
RankedOrganicTweet | |
suggest_activity | |
suggest_activity_feed | |
suggest_activity_highlights | |
suggest_activity_tweet |
Probably one of the easiest things you'll ever do with gpg
Install Keybase: https://keybase.io/download and Ensure the keybase cli is in your PATH
First get the public key
keybase pgp export | gpg --import
Next get the private key
I've had many people ask me questions about OpenTracing, often in relation to OpenZipkin. I've seen assertions about how it is vendor neutral and is the lock-in cure. This post is not a sanctioned, polished or otherwise muted view, rather what I personally think about what it is and is not, and what it helps and does not help with. Scroll to the very end if this is too long. Feel free to add a comment if I made any factual mistakes or you just want to add a comment.
OpenTracing is documentation and library interfaces for distributed tracing instrumentation. To be "OpenTracing" requires bundling its interfaces in your work, so that others can use it to time distributed operations with the same library.
OpenTracing interfaces are targeted to authors of instrumentation libraries, and those who want to collaborate with traces created by them. Ex something started a trace somewhere and I add a notable event to that trace. Structure logging was recently added to O
/* | |
Modules are not required, although usage is encouraged. This allows existing code to work within Java 9. | |
Code defined outside of a module is put in an `unnamed module` | |
Unnamed is a special module that is able to read from *all* other modules, *but* only the exported code (see below) | |
All of this is automatic when your code compiles. It allows your existing code to continue working as expected. | |
This is an example `module descriptor`. | |
It should be placed directly under the `src` dir, e.g. for in Maven `src/main/java/` | |
Must be named `module-info.java`. | |
*/ |
# <type>: (If applied, this commit will...) <subject> (Max 50 char) | |
# |<---- Using a Maximum Of 50 Characters ---->| | |
# Explain why this change is being made | |
# |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->| | |
# Provide links or keys to any relevant tickets, articles or other resources | |
# Example: Github issue #23 |
First of all, install Homebrew itself.
As the tap is a private Git repo, you need to generate a GitHub token
with repo
scope and then add this token to your ~/.netrc
file like this:
machine github.com
login <your GitHub user>
password <your GitHub token>
Picking the right architecture = Picking the right battles + Managing trade-offs
package hu.akarnokd.reactiveflowbridge; | |
import java.util.Objects; | |
import java.util.concurrent.Flow; | |
import java.util.function.Function; | |
/** | |
* Bridge between Reactive-Streams API and the Java 9 Flow API. | |
*/ | |
public final class ReactiveFlowBridge { |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.