4 minutes read | 771 words by Ruben BerenguelSome links are affiliate links
A week on holidays (in-between jobs), where I read more books than articles.
I have tried to avoid doing “fake work” (although I started a Scala project I want to finish “soon-ish”), because I rarely “really” take time off. So I tried to sleep a lot and do nothing useful. I failed miserably.
I forgot to mark this as read, finished a month or two ago. It was very interesting, although the audiobook is not the ideal format for this particular book, which seems to be diagram heavy. I’ll have to check the Kindle or paperback versions too.
The last part on risk mitigation and management was a bit boring, but overall the book was interesting. It was a hard contrast with Andy Grove’s High Output Management, which I have been listening to at the same time (same week, not at the same exact time). DeMarco rails against many of the things Grove suggests doing.
This was actually a form of re-read, I had totally forgotten I had read this book 4 years ago and got it on Audible. It sounded familiar overall… and my impression was kind of meh, this second time around. Probably also the first one.
I’m a print-style debugger, and for what I think is a good reason: I frequently switch languages (python, scala, go) and never delved into any debugger except gdb and valgrind when I did only numerical stuff in C.
This is a very good pitch for Metals, the Scala language server. I’ve been using it since it was very, very new (I have contributed to at least one of the “meta” repositories, but I don’t think I have helped with Metals itself… yet?). It makes Scala in VS Code as entertaining to write as Haskell, with go-to-definition, completions and all the bells and whistles you may want.