#TEDxMilano next track pls !!!

@dan_abramov The same when I try to avoid bugs in production.

@matryer In a recent project, a library I had to write for my team, I started from the earliest test: I wrote the README first, then I asked my teammates to judge the documented interface and, at last, I wrote the automatic test for the interface. 🙂 what do you think about it ?

@asteroix @davecheney Yeah, avoid standard libraries too ! I have in mind a new ideal shape for a new kind of wheel. 😂😂

@davecheney nim i —save beautiful-idea

@benbjohnson Thank you !

2)With a ref to I felt comfortable to make Todos a public attribute of the in-memory service implementation.This makes it easier to construct and test the service (I read somewhere to prefer literals over constructors). What do you think about it?Thanks!

RT @astro_luca: Instead of looking for an enemy in the different, the poor, the disenfranchised, we should unite globally to fight the one,…

RT @vronnie911: StackOverflow language popularity through the years

@tinymakesthings Damn! That's a collection!

RT @dominikhonnef: Working on Go has taught me to appreciate linear history in VCS. Meanwhile, in Kubernetes land, they're trying to recrea…

RT @mikelikesitalot: Appropriate for today. #cloud

RT @golangweekly: A Gameboy Emulator Built in Go - (It includes a mechanism for playing ga…

@peterbourgon what's your opinion about error handling in go? I read this article about some good patterns to be used for error handling: which pattern do you use the most in your projects? #golang #errorhandling

RT @iamdevloper: If your code worked first time, you missed something. If it breaks, you missed something. You missed something.

@Dio Alla tombola di Natale, ogni 5 numeri qualcuno fa tombola.

“Standard Package Layout” by @benbjohnson well written article about good golang sw architecture design and about good sw architecture design, in general.