travisjeffery

I'm not sure, I haven't heard of that happening before. I've asked my editor if she knows what's up. You can email me at tj at my HN username dot com if you want to follow up.

Awesome! Hope you enjoy reading the book and thanks for buying it.

Hey, I'm the author of Jocko. I've been working at Confluent the past four years.

I just finished writing a book that shows how to build similar distributed services from scratch, it walks though building a simple distributed commit log with built-in consensus and service discovery from nothing to deployment: https://pragprog.com/titles/tjgo/distributed-services-with-g...

People that are interested in this blog post will interested in a book I wrote: Distributed Services with Go (https://pragprog.com/titles/tjgo/distributed-services-with-g...). The book walks the reader through building a distributed event service from scratch that uses Serf as a library for its service discovery.

Magit is working on switching to libgit2 https://github.com/magit/magit/issues/2959 to fix this.

Yeah I'm discussing with my editor now about when to put out the beta it'll be out either after we finish editing the chapter I just finished writing or the next one. So pretty soon. I hope to have the whole book finished by July but that's a bit more TBD up to how soon I finish writing the last few chapters.

Whoops here's the proper link: https://travisjeffery.us4.list-manage.com/subscribe?u=1e3ff7...

Thanks!

I'm currently writing a book for PragProg called Building Distributed Services with Go (though it mostly applies to other languages too) that's walks you through building a distributed database from scratch. You can sign up on this mailing list to know when it's available: https://travisjeffery.us4.list-manage.com/subscribe?u=1e3ff7....

I'm not doing it for the money. Writing a worthwhile book is about the least efficient way to make money.

Yeah---each chapter begins with background on the chapter's topic, some theory, covers how and where you'd use what's we're talking about in the chapter and then we use it to build a part of the project we're building throughout the book. For example, in the consensus chapter we talk about what problems it solves and how you can use it in your projects,and then we implement Raft in the service for leader election and replication.

Awesome. Hopefully within a month or two.

Not sure, haven't gotten to that yet. Just from looking at the prices of other PragProg books somewhere around $21.95-24.95.

I'm currently writing a book for PragProg called Building Distributed Services with Go (though it mostly applies to other languages too) that's walks you through building a distributed database from scratch. You can sign up on this mailing list to know when it's available: https://travisjeffery.us4.list-manage.com/subscribe?u=1e3ff7...

I think the keyword is "typical." Which is probably true that the math is pretty basic at most universities and in most programs.

But you can go to schools like the University of Toronto, which is a strong math school and has very challenging programs like ASSPE1165 (https://fas.calendar.utoronto.ca/mathematics-specialist-scie...)

Most popular languages do, it seems reasonable.

First of all I think it's cool enneff read my post.

But pkg doesn't only make your import paths unwiedy. I'ts more like that's the only---or at least main---issue with pkg. But you get benefits from it that I talked about: consistent layout structure; know what directories are packages; separate your packages from examples, docs, etc. If pkg only made your import paths unwiedy then no one would use it.

Hey, I'm currently writing a book for PragProg that's going to announced soon. It's tentaively titled "Building Distributed Services with Go", and the Go part is secondary if it's not your language of choice. It guides you through building a distributed service from beginning to end. I don't have anything to point you to at the moment other than my mailing list and I'll let you know when the book is in beta: https://travisjeffery.us4.list-manage.com/subscribe?u=1e3ff7.... Thanks.

Here's a list of prominent Go infrastructure projects and by no means a complete list: Kubernetes, Docker, Etcd, Consul (and the rest of Hashicorp's projects), CockroachDB, Prometheus, TiDB. Maybe I'm just blind to C# but I don't remember coming across a single similar project that's written in C#.

You got it. You can be about security or UX. And when the accounts are public I'm especially in favor of taking advantage UX-wise. The issue's when both are half-assed.

This is a better argument, but rarely given. The issue is the accepted argument made for 'username or password is incorrect' is it's a best practice protecting the existence of accounts on sign ins, yet sign ups are ignored.

Correct. The UI message would always be the same, some variant of "email sent." Even if the account already existed and it wasn't actually a successful sign up of a new account.

Haha, that's cool with me.

Exactly. You got it.

Kafka 0.11 (recently released) has exactly once semantics and transactional messages built-in.

- Talk from Kafka Summit: https://www.confluent.io/kafka-summit-nyc17/resource/#exactl...

- Proposal: https://cwiki.apache.org/confluence/display/KAFKA/KIP-98+-+E...

http://stash.cool/ - Personal finance tool I'm working on that's what Mint would have been if they hadn't sold to Intuit, had all that ad garbage and tacked on features.

First, I'm a big fan of yours. I was recently interviewed by Go Time and I talked about how awesome Redis is, what a good example it/you've been for open source projects, and how funny your v4 RC blog post was.

My goals for building Jocko to start:

1. Learn more about distributed systems to the point I could build one "What I cannot build, I do not understand." sort of thing. 2. Simplify running Kafka—so remove ZK, only need to install a binary, and so on 3. Maintain compatability—so people can just drop Jocko in, Kafka clients and anything else that uses Kafka's protocol works

After that, I have some ideas on things to do but am waiting to get feedback from people. For instance, I think the configuration around setting how much disk space topics use could be better.