“Excellent hand-picked articles & videos about programming from all over the Internet”.
#golang defer makes you sloppy. Try to avoid when dealing with mutexes— Anton Kaliaev (@akaliaev) November 2, 2018
defer + mutexes makes you forget that— Anton Kaliaev (@akaliaev) November 2, 2018
a) while we're locked, nobody else can access the object (unless its read lock) -> better to unlock earlier
b) when you put more code & call other functions between lock / unlock, it becomes easier to deadlock
c) defers are slow
More times you don't need a defer pic.twitter.com/DYrbJQJwgS— Anton Kaliaev (@akaliaev) November 2, 2018
Must read for anyone writing docs.
Must read for anyone writing code.
- No stand-ups
- No planning at regular intervals
- No retros
- All meetings are optional
This may sound extreme. But there is some logic to this madness.
“where we are today is bullshit. As engineers, we can, and should, and will do better.”
- “Uncle” Bob Martin - “The Future of Programming”
Reflection on the history of programming (from 1948).