cyrusaf

Great article! I found the section on "GC Assists" very informative:

> You can think of this like a tax that your goroutine must pay for allocating during a GC cycle, except that this tax must be paid upfront before the allocation can actually happen.

Sum types would add much needed compiler safety to returned errors and optional values. We often see nil pointer dereferences during runtime due to the usage of pointers as optional types.

It's very unlikely they store their passwords in plaintext. They were probably logging during login requests and didn't realize the whole request body was being logged. Can happen if you have a proxy/load balancer with logging enabled.

This is not what happened. The tokens were mapped to user IDs and when people signed in, the db created new users which may have had the same IDs as old deleted accounts. When they restored the DB, these tokens pointed to other users and granted access to these other users' accounts. Quite an unfortunate situation. May have been mostly avoidable if UUIDs were used instead of incrementing IDs, but hindsight is 20/20.

Hopefully these will be implemented soon by the community. Open source rules :)

HTTP: - gRPC for microservices - graphql for combining microservices for the frontend

DB: - dynamodb/psql depending on features. aws-sdk or base go sql package. - redis for caching. go-redis package.

Stats/logging: - statsd/graphite/grafana - sirupsen/logrus for logging

I usually write a wrapper for packages that will automatically report stats + logging.

I think you would be better off using more well known statistics for betting (ie. multivariate regressions, t-tests, etc..). These stats methods are less of a black box than ML (neural networks, etc..) so you'll be able to understand why they have chosen specific bets and you'll be able to tweak them easier.

ML is often just stats under the hood in most cases -- I think I am targeting neural networks specifically with this comment.

In person I use a thumb drive. You could encrypt the credentials using PGP and send it to a coworker if they are remote.

Sometimes I just go on google hangouts and share my screen if I'm feeling lazy.

I don't see this as a comparison between Ryzen and Intel. He compares a custom built PC with a 2017 3.6 GHz 8 core Ryzen to an older 2013 2.3 GHz 4 core i7. He could have replaced his Ryzen CPU with a similar priced intel processor and seen the same performance.

I think many would make the argument that not enough is being done environmentally and that more action needs to be taken. Cutting funding to the EPA and lifting restrictions are reversing the progress that we have made environmentally in the past couple decades.