Become a member
Sign in
David Frenk
David Frenk

David Frenk

50 Following
39 Followers
  • Profile

  • Claps

  • Highlights

  • Responses

Highlighted by David Frenk

See more

From The Joy and Pain of using Google BigTable by Jono MacDougall

In fact, as a general rule, you should always keep things simple even if your tools allow for more complex patterns. These patterns often bite you later. Complexity means you get bugs, challenging maintenance, vendor lock in, scaling issues or perhaps most importantly, the cognitive overhead of having yourself and new engineers understand these complex patterns. Always lean into the few features your tool is advertised to Do Well. This applies equally to your code.

From Interfaces in Go (part I) by Michał Łowicki

…fect is that even if interface type value holds a nil pointer then such interface value is not nil. Known mistake is to return not initialized, non-interface type value from function returning interf…fect is that even if interface type value holds a nil pointer then such interface value is not nil. Known mistake is to return not initialized, non-interface type value from function returning interface ty…

From Simple HTTP middleware with Go by Gabriel Aszalos

nd tracing middleware that I’ve defined and passed as parameters to this function…nd about with the logging and tracing middleware that I’ve defined and passed as parameters to this function.

Claps from David Frenk

See more

Train neural networks using AMD GPUs and Keras

Mattia Varile

Avoiding Double Payments in a Distributed Payments System

Jon Chew

The Joy and Pain of using Google BigTable

Jono MacDougall