The US government has the Plain Language movement which is rewriting policy and legal documents in clear, plain language.
The plainlanguage.gov site is an excellent all-around writing resource. I direct junior developers here when they are trying too hard to sound fancy when communicating technical concepts in documentation and design documents.
> But he could understand so much more than he could say. If you asked him to point to the vacuum cleaner, he would.
Perhaps worth noting that it is possible to teach infants (often starting at around 9 months) sign language so that they can more easily signal their desires.
Some priority recommended words would probably be:
* hungry/more
* enough/all done (for when they're full)
* drink (perhaps both milk/formula and water† gestures)
These are not (AFAICT) 'special' symbols for babies, but the regular ASL gestures for the work in question. If you're not native English-speaking you'd look up the gestures in your specific region/language's sign language:
† Another handy trick I've run across: have different coloured containers for milk and water, and consistently put the same contents in each one. That way the infant learns to grab a particular colour depending on what they're feeling like.
I agree that it is no synchronization primitive and that even if it was, it's very fragile. However I found it in nearly every project I worked on, in backend tests, frontend tests and even in integration tests where the library driving the browser should take care of waiting for elements to appear on screen. Modals and browser dialogs are particularly good at breaking stuff.
The dynamic is: developers write the the test and it usually works on their machines. If it does not there is a chance that they figure out what's wrong and rewrite it in the proper way. Tests often work locally, where the CPU and disk are nearly 100% available to run them. Sometimes they fail on CI systems. Developers scratch their heads and attempt the easy fix of adding a sleep of 1 second. That almosts always work and it took 5 minutes, code, commit, test run. They know that it stinks but they have stuff to do. Every few months somebody attempts to remove some of those sleeps with mixed and often unsuccessful results. Integration tests are particularly nasty.
> Managerialist culture is founded on the notion that workers must be supervised and controlled.
That's a shallow view of the situation. What you're describing is "Taylorist" management, or "Theory X" management.
Modern management theory also discusses "Theory Y" management, in which providing context and trust is more important than supervision and control.
Many managers are unaware of this concept, even though it's Management 101. If that's the case in your company, it's not a problem with "managerialist culture"... it's a problem with your company's culture.
TLDR Addendum for people like me who aren't immediately familiar with these terms
High
- Distributed practice: Implementing a schedule of practice that spreads out study activities over time
- Practice testing: Self-testing or taking practice tests over to-be-learned material
Moderate
- Elaborative interrogation: Generating an explanation for why an explicitly stated fact or concept is true
- Interleaved practice: Implementing a schedule of practice that mixes different kinds of problems, or a schedule of study that mixes different kinds of material, within a single study session
- Self-explanation: Explaining how new information is related to known information, or explaining steps taken during problem solving
Low
- Highlighting: Marking potentially important portions of to-be-learned materials while reading
- Imagery use for text learning: Attempting to form mental images of text materials while reading or listening
- Rereading: Restudying text material again after an initial reading
- Summarization: Writing summaries (of various lengths) of to-be-learned texts
- The keyword mnemonic: Using keywords and mental imagery to associate verbal materials
For people interested in more details about Postgres internals I cannot recommend https://www.interdb.jp/pg/ enough, an excellent text with lots of details
Yeah, it's not commonly necessary for real world engineering, but it's certainly good to know, at least as a mental exercise. There's a nice free algorithms textbook used at UC Berkeley that covers the concept pretty well: http://algorithmics.lsi.upc.edu/docs/Dasgupta-Papadimitriou-...
Sure, for 1, Nietzsche is always a good choice if you want someone to challenge modern assumptions. René Guenon if you're looking for a mystical, metaphysical approach to religion, especially Hinduism and Islam. I also really love the Tao Te Ching and think it's a totally different approach to Western ones.
For 2, I used Virginia Klenk's Understanding Symbolic Logic in a course and recommend it.
Can I heavily recommend the use of them as a pihole + Wireguard VPN + DNSCryptProxy Server.
Pihole -> Great use for a network wide adblocker/DHCP server.
Wireguard VPN -> In combination with a DDNS setup and some port forwarding enables the use of a global private VPN. I think it's a prerequisite for a decent home-automation setup.
DNSCryptProxy -> Great for ensuring all DNS requests on the network via DNS over HTTPS. Kind of useful because frankly ISPs are sniffing DNS traffic. Also useful for bypassing DNS based ISP filters.
The above basically enabled me to create a 5 country wide private VPN by giving VPNs to family members. It enables me to print/scan things from abroad, access CPU resources/servers/GPUs/Webcams/automation and obviously browse as if I am in another place.
My family when they are abroad, can now work as if they aren't.
It also saves power (reducing analytics traffic), improves privacy and takes about a weekend to setup.
The New York times consistently creates amazing online experiences using current tech, and the result requires fewer resources, is more accessible, and works significantly faster than any project of any people that whine about Safari on Reddit and HN.
Here is example code and blog series for a step-by-step DDD-based refactoring of an existing app. Don't know if they are the same as what's used in the book, but found them quite interesting.
The plainlanguage.gov site is an excellent all-around writing resource. I direct junior developers here when they are trying too hard to sound fancy when communicating technical concepts in documentation and design documents.
Here are some great examples:
https://www.plainlanguage.gov/examples/before-and-after/ambi...
https://www.plainlanguage.gov/examples/before-and-after/mont...
https://www.plainlanguage.gov/examples/before-and-after/use-...