User Profile

Attaboy Locked account

Miya@bookwyrm.social

Joined 3 years, 8 months ago

I can resist everything except temptation.

I read pretty much anything with a halfway interesting title, although mostly SF and technical books about programming.

Pronouns: any

This link opens in a pop-up window

Attaboy's books

Currently Reading (View all 7)

2025 Reading Goal

33% complete! Attaboy has read 4 of 12 books.

avatar for Miya Attaboy boosted
Milton Crane, Milton Crane: Fifty Great Short Stories (Paperback, 1983, Bantam Classics)

In this moment she felt that she had been robbed of an enormous number of valuable things, whether material or intangible: things lost or broken by her own fault, things she had forgotten and left in houses when she moved: books borrowed from her and not returned, journeys she had planned and had not made, words she had waited to hear spoken to her and had not heard, and the words she had meant to answer with; bitter alternatives and intolerable substitutes worse than nothing, and yet inescapable: the long patient suffering of dying friendships and the dark inexplicable death of love -- all that she had had, and all that she had missed, were lost together, and were twice lost in this landslide of remembered losses.

Fifty Great Short Stories by , (Page 227 - 228)

Teiva Harsanyi: 100 Go Mistakes (2022, Manning Publications Co. LLC)

Great overview

Great overview of many common Go mistakes. I've learned quite a lot, especially towards the later chapters. The examples sometimes seemed a little too 'contrived,' I guess that's just the side effect of trying to keep code extracts as short and concise as possible. I would've wished for some more real-world examples though.

Teiva Harsanyi: 100 Go Mistakes (2022, Manning Publications Co. LLC)

As we discussed, interfaces are made to create abstractions. And the main caveat when programming meets abstractions is remembering that abstractions should be discovered, not created. What does this mean? It means we shouldn't start creating abstractions in our code if there is no immediate reason to do so. We shouldn't design with interfaces but wait for a concrete need. Said differently, we should create an interface when we need it, not when we foresee that we could need it.

100 Go Mistakes by  (Page 24)

Neal Stephenson: Fall; or, Dodge in Hell (2019, William Morrow)

He wondered whether the designers of the phone had performed clinical studies on snoozers in order to decide on the nine-minute interval. Why not eight minutes, or ten? The makers of the phone were famously particular about design. This had to have been data-driven. It was no coincidence that Dodge was being afforded just enough time to lose the thread of consciousness before the alarm went off again. If the interval had been much shorter, he would not have had time to drift off and so this feature could not have truly been called a snooze alarm. Much longer, and the snooze would have deepened into true sleep.

Fall; or, Dodge in Hell by  (Page 6)

It's so much better when people with a good understanding of current technology write SF.