I’m finishing Writing an Interpreter in Go. Not as technical as it sounds, and definitely awesome.
Is this a decent primer for learning go coming from a C# background?
sorry for the (way too) late reply. I wouldn’t use this book to use Go. Though the language is used, it’s very basically done so.
I have 2 phones.
A Samsung Galaxy S8, paid for by my employer that I carry when I am on-call.
GMail/Inbox aren’t installed there. So I don’t have access to work emails. I use it for calendar notifications though.
Only pagerduty knows the phone’s number.
My personal phone is the new Nokia 3310, which only can send texts and make phone calls (I don’t even have a data plan. So no MMS).
When I’m on-call, I’ll be carrying both phones (usually one in my pocket, the other in my backpack). When I’m not on-call, I’ll only have my personal phone.
What are you using to build new docker images (I suppose your own computer isn’t ARM)?
I don’t like the single points of failure, but other than that it looks cool.
It’s not meant as a highly-reliable cluster :-)
Isn’t that the purpose of a cluster though?
Of a production one, yes for sure. As I mentioned, the goal isn’t to build a production cluster, but to learn.
Also, removing all SPoF here would mean 2 masters, and 2 load balancers, with load balancing on both. On
raspberry pis at home, this could get very messy quite easily.
Two laptops, one for work, the other for personal stuff.
I don’t have personal email/facebook on the work laptop; I don’t have any work stuff on the personal laptop.