Brief Thoughts on Two Books I Read Recently
The first one wasn't really a technical book—more about how we work—and the idea of "automate everything you can automate" kept coming up, which resonated quite a bit as a developer.
The second was a novel, and the ending felt a bit empty. I was hooked through the middle, but it lost momentum in the latter half. Still, the prose was good, so I read it to the end.
What are you reading these days?
10 answers
'Automate everything that can be automated'—these days, I’m not so sure about that. Once you automate something, you still end up needing someone to maintain it, and when a script goes wrong, you lose half a day tracking down the cause. Of course, the book’s context is probably different.
Agreed—a novel’s ending is really important.
What's the title of the first book? I've been looking for automation-related books lately, so I'm curious.
A novel with an anticlimactic ending really makes you feel betrayed lol. It gets you hooked through the midpoint, then loses steam at the end, and the letdown is twice as bad. Still, if the prose was good enough that you read it to the end, doesn’t that make it a success in its own way? I usually just close the book if the ending is off.