The Annotated Turing is probably my favorite technical and historical book, there's nothing else like it. But I'll never forgive the utterly strange typo in it:
"In a famous 1907 paper on relativity, Hilbert's friend Hermann Minkowski would coin the word Zaumreit or spacetime."
Zaumreit literally translates to "bridle riding" and is probably a play on words, Raumzeit means spacetime. This has puzzled me for over a decade now. How does this even happen?
You find it surprising that an American author and book editor don't read or speak German?
I'm guessing the author remembered the word incorrectly and wrote it down that way. It's not hard to transpose two letters when you don't know the language.
The book is really well researched, it includes 5 pages of selected bibliography. I doubt the author wrote about a scientist coining a word and then recalled said word from memory. There's no misspelling of the word "Entscheidungsproblem" which occurs like 80 times. It just stuck out to me, maybe the source material was already wrong, maybe he was trying to be funny or nerd snipe someone, it's a mystery.
A large portion of products we buy in second hand stores are children's toys and clothing. The prices of new toys are insane, we leave a second hand store about once a month with a large bag of stuffed toys, board games, worn in shoes, skates etc. for the cost of a single new item. Kids don't care at all and mine refuses to wear new shoes even.
That's how we got reintroduced to thrifting/preowned shopping/whatever you want to call it: we had a kid. It wasn't even so much a financial thing as it was this sense that otherwise there would be so much waste (the financial aspect is nice though too). So many clothes and toys that are just fine but they grow out of them. After that we started looking into stuff for ourselves.
I'm guessing somewhere along the lines of /r/learnjavascript or /r/learnpython. The browser is the lowest barrier REPL/Interpreter installed on any modern computer and it's possible to make somethig analogous to GORILLAS.BAS with MDN, an HTML5 canvas and a few lines of JS.
They should get whatever they ask for. There isn't a workday where I don't think to myself Man, we'd be so screwed if curl didn't exist. It runs more business than Excel. If there ever was a Log4j style CVE in curl I'd just become a fisherman or a blacksmith.
I use it for building various tools and Ansible plugins in operations. Mainly requests for talking to REST APIs, json for json, aiohttp and asyncio for parallelism, pyparsing for parsing, argparse for sane CLIs. Python is installed everywhere and most people understand it enough to clone a repo, edit what needs changing and ./go in a pinch.
Not in the EU. I pay for a lot of nonrecurring things via money transfer and I need a TAN for every online transaction. Before mobile apps they would occasionally mail me a list of like 50 of them [1] but that's not a thing anymore. Every online credit card transaction has to be confirmed in the banking app as well.
European versions have this rule [1]. I wasn't aware that the US version allowed adjacent ship placement until I bought a commercial version for my kid last Christmas and started looking into strategies.
I have my doubts. If I need to implement say Dijkstra's in Haskell and pick up a random algorithms book then it's not going to help me at all. If I then ask a hundred programmers how they would do it I'd get a hundred wildly different answers. From my point of view algorithms and data structures in functional languages are not very well understood or explained due to their stateful nature. If functional programming was the most popular paradigm I'd expect a lot more literature on this topic.
Monads and Functors aren't particularly exciting in Python because properties or contexts can be expressed with e.g. boolean flags and properties or contexts can be ignored when applying functions to unrelated parts of an object.
# milk_cows :: Person -> Tired Person
def milk_cows(person):
...
person["tired"] = True
return person
# feed_pigs :: Person -> Tired Person
def feed_pigs(person):
...
person["tired"] = True
return person
# birthday :: Person -> Person
def birthday(person):
person["age"] += 1
return person
# willy :: Person
willy = {"age": 32, "tired": False}
# fmap and >>=
print(milk_cows(birthday(feed_pigs(willy))))
In Haskell there would be a 'Tired a' type with a Monad instance to express the tiredness property and a Functor instance to apply functions to it with no impact on or knowledge of tiredness, e.g. aging.
