Earlier quoted context omitted.
Yes. People forget it was a response to abominations such as Yahoo Answers, which quickly devolved into a cesspool of mouthbreathers, haha. Also expert-sexchange/quora which tried-to/often-did hide the answers. Without its "tough love" Stack would have had a similar trajectory. Maybe a few policies here and there were problematic but overall it was and continues to be a huge benefit to the developer/IT community.
Yahoo answers gave us MBMBAM. For that I will always be thankful.
Nobody cracks open a programming book anymore
361–367 of 367 posts
Re: Nobody cracks open a programming book anymore
#362Re: Nobody cracks open a programming book anymore
#363Beyond the slowing you to type, the key part of the good books was the considered and mindful order of presentation. This is what had me spending money when I could get the reference manual for free - a guide , a book that taught me unfamiliar concepts in top down fashion, and took some degree of responsibility to be both accessible and comprehensive. I love the tutoring of LLM, but to this day as a complement to a g…
Unfortunately even in the old days, a truly good programming book like you’re describing was depressingly rare. Younger me really enjoyed some of the game programming books by Andre Lamothe. Most “Learn Language X” books were terrible with over focus on syntax and very little thought into organization.
"Python for Data Analysis" by McKinney (2018)
"The Go Programming Language" by Donovan and Kernighan (2016)
"Hacker's Delight" by Warren (2013)
"Algorithm Design Manual" by Skiena (2008)
"Purely Functional Data Structures" by Okasaki (1998)
"Structure and Interpretation of Computer Programs" by Abelson and Sussman (1985)
Re: Nobody cracks open a programming book anymore
#364The decline of programming books removed a constraint on programming language complexity. At one point, the basic set of books for Java was six volumes. That's when language books broke down from sheer complexity. The combination of Google search and Stack Overflow allowed programming to become more complex than anyone could keep in their head. C++ bloated to the point that people who used to be C++ language lawyers…
Do you happen to have any links to more info about this schedule system. If I Google “sears schedule system” I get a bunch of results about vaccines, and if I append “logistics” the top result is your comment.
Here's the concept. The simple way to fulfill orders is Doordash Shopping. One person goes to a store and picks the entire order. Performance degrades with the size of the store. This takes O(orders * inventory size) effort. If too many shoppers are trying to fill orders, they get in each other's way and the building traffic starts to choke. This is why Doordash Shopping has a big markup vs. Amazon.
The classic Sears schedule system takes the incoming order and breaks it down by department and picker. Pick slips are generated, originally by hand, and sent to the various pickers, originally by pneumatic tube. Pick slips have a 45 minute time window and a destination bin number. Pickers get pick slips, all of which are for items in their area, grab the item, and put it on a conveyor with the pick slip attached. The conveyor leads to the destination bin area, where orders are assembled in the bins. At the end of a 45 minute cycle, all bins are sent to order checking and outprocessing, and new empty bins are placed for the next fill cycle.
The order paperwork is already attached to the bin, so the checker checks off the items in the bin vs. the items on the order. Excess items from picker errors become go-backs; missing items are not charged to the customer. The total is computed and billed. The bin and paperwork go off to packing and shipping.
Each picker moves only short distances. No running around the giant warehouse. That gets the overhead down to O(orders * log(inventory size)). Pneumatic tubes carry the data that drives the pickers, and conveyors do most of the carrying. The system can develop a backlog in the incoming order area, where it's obvious and can be managed. The picking areas don't usually choke, because their load is bounded by the number of bins per cycle.
It was all done with paper, forms, carbon paper, clipboards attached to totes, cash registers, conveyors, and pneumatic tubes. Julius Rosenwald (1862-1932) designed the original system and became quite wealthy.
Sears should have become Amazon. They had the fulfillment system. They had catalog ordering working well. They never got the online front end right.
[1] https://www.searsarchives.claeys.co/history/history1900s.htm...
Re: Nobody cracks open a programming book anymore
#365- it was edited, so ideas and text are consistent
- the examples worked (at some point in time)
- the author has enough time-space to clearly describe a lot of material well
Nothing beats a book for an enormous amount of detailed information. Even just reading the table of contents helps to help understand what to focus on during study.
My copy of "DevOps Handbook" is covered in tags and handwritten notes. Brett Slatkin's "Effective Python" is way too much for me, but I got a ton out of the parts I focused on. No other media is like books!
Re: Nobody cracks open a programming book anymore
#366Earlier quoted context omitted.
I like this metaphor. Spanish ñ, Catalan or French ç, German ß. Similarly for ł and other Polish letters. It seems strictly speaking the latin alphabet cannot cover many european languages. But mostly we can say latin can express that. You can write "ss" for German and l for Polish, etc, so it can definitely be used. Source: whatssap messages.
"ss" is a different sound in German. Trasse (line/ train path) vs Straße (street)