The Missing README covers skills you'll need to be a successful software engineer, the skills your manager wants you to know, the skills not taught in school.
The Missing README was officially released yesterday! ๐
We're now #1 in Amazon's "New Releases in Software Design & Engineering" category! Thanks for all the support. ๐
amazon.com/gp/new-releases/bโฆ
The Missing README is part of No Starch's March Humble Bundle set! Pick from the 7 item, 11 item, or 18 item bundles to get TMR and a bunch of other amazing books. โค๏ธ
humblebundle.com/books/learnโฆ
One of my favorite bits in @missingreadme . If you ever get to visit, the amphitheater in Arles is incredible.
P.S. buy the book for your early career SWE friends! :-D
If y'all are lookin for a good gift this holiday season, might I recommend The Missing README?
amazon.com/Missing-README-Guโฆ@squarecog and I jammed it full of practical lessons for engineers. Plus, it's got fun autobiographical stories like this one...
A software (libraries as well as apps) design tip: validate configuration as early as you can. Validation (and failing) at build time > validation at start-up > validation at runtime. The earlier any invalid config is flagged, the faster the feedback cycle for your users.
"Ask a programmer to review ten lines of code, heโll find ten issues. Ask him to do five hundred lines, and heโll say it looks good." - Gene Kim, The DevOps Handbook.
New software engineer? Experienced eng/manager who helps new engineers? Take this 5 min survey on onboarding! All responses get a sticker and entry into raffle for a free copy of The Missing README. Please RT! docs.google.com/forms/d/e/1Fโฆ
To ๐ 1 year of @missingreadme, @squarecog and I are running an engineer onboarding survey and a giveaway.
Take the survey to help us! ๐ (< 5 min)
forms.gle/4v4eJKAut8BAnKo79
You get a free laptop sticker and a chance to win a copy of the book.
Please ๐ so we get good data!
๐ฃ๏ธ "Distill years of Java experience down to a set of best practices that help developers build high-quality Java applications and libraries"
Lots of good advice for #Java developers on this site by @JonathanGiles ๐.
java.jonathangiles.net/
Itโs The Missing READMEโs one year pre-release anniversary! ๐
Over the past year, weโve sold 1000s of copies and gotten 41 Amazon reviews with a 4.8 โญ๏ธ average. But the best part has been hearing how the book has helped engineers grow.
Thanks!
amazon.com/dp/1718501838/refโฆ
If I may tweet my own horn a bit, we mostly wrote @missingreadme for beginners, but it's lowkey good for mid-career, too (most will find at least 50% of it useful, different 50 for each person).
We cover this in @missingreadme:
๐ Do your research
โฐ Time box
๐ Show your work
๐ Don't interrupt
๐ข Prefer multicast, async communication
๐ฆ Batch your synchronous questions (interrupts)
@HarvardBiz posted a similar list with some some fresh ideas.
hbr.org/2022/02/how-to-interโฆ
We broke 30 reviews on Amazon (4.8 โญ๏ธ avg) a couple of days ago and we're above 70 on Goodreads (4.53 โญ๏ธ avg). ๐โจ
Keep the reviews coming! ๐
The Missing README will soon be available Polish
Simplified Chinese, and Russian!
We donโt have release dates, but weโll let you know when we find.
There are many chapter 9 (going on-call) learnings in this post. The post is also a good example of the "follow-up" section. It's worth a read.
blog.roblox.com/2022/01/roblโฆ
๐ข Blogged: "What's in a Good Error Message?"
Discussing some recommendations for designing error messages in libraries and frameworks.
morling.dev/blog/whats-in-a-โฆ
ALT What's in a Good Error Message? Context, the error itself, mitigation.