Yesterday was the first day my college-freshman daughter's life was without the War on Terror.
This is a good year. Happy New Year!
https://twitter.com/EODHappyCaptain/status/1608961432552603650?s=20&t=JyIXln9s-CxWH6UteQHurQ
@davidolrik @brianokken a family favorite is The Eyre Affair by Jasper Fforde. Think a Douglas Adam's crossed with Jane Eyre mystery novel set in 1985 Britain. You must like time travel and puns.
This toot is sponsored by the toast marketing board.
@brettcannon jit is my vote. I believe it'd get greater flexibility in experimentation, jit implementation, and production use. We could see different jits for different processing use cases, written in C++, rust, java, etc., enabled in some pieces of the software and not others, etc.
If there's a good all-around jit then it could get used as a standard in sub-interpreters, and you'd still be able to use a java-implemented jit for jython-compatible code, perhaps.
It's satisfying to see my hatred of #YAML vindicated (h/t @[email protected] ) https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
Yesterday was the first day my college-freshman daughter's life was without the War on Terror.
This is a good year. Happy New Year!
https://twitter.com/EODHappyCaptain/status/1608961432552603650?s=20&t=JyIXln9s-CxWH6UteQHurQ
@james_hardaway she's right about that, and it's not just for supply chains. It's why we leave white space in the training schedule, too.
Similarly, the book The Phoenix Project does a good job of showing how over-scheduling IT workers means that there's no time available for either emergencies or improvements.
It doesn't mean folks are loafing around, not doing productive work, etc., but that the humans have time to adjust to changing conditions, opportunities, and disruptions.