Lesson to Learn
summary
A cautionary account about publishing a technical book describes problems that can occur even after contracts and publicity are arranged, including a publisher canceling publication. It names six proofreaders who reviewed the manuscript, explains losing or having to renegotiate rights to publish in certain languages, and recounts a last-minute switch to self-publishing that required extra marketing and quality checks and incurred unexpected costs and canceled deals.
AI-written summary · about
related talks
30mRust: an alternative to high-level programming languages?
29mPublishing High-Quality Crates
59mTo err is human - error handling in C++26
47mKilled by Worse is Better What we can learn from the last time FP failed (TBR)
05mBenefits and Drawbacks of Adopting a Secure Programming Language: Rust as a Case Study
25mLessons Learned from Teaching Rust - Liv
29mError handling Isn't All About Errors
07mStrategies for Developing Safety-Critical Software in C++