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. 📈
https://t.co/gyxEn0M8ra
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. ❤️
https://t.co/Tw7M6PBIMc
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
"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! https://t.co/iWJzRXbZTV
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)
https://t.co/OLEDmrzidp
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 👍.
https://t.co/p6KnzNatxS
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!
https://t.co/XUoF8wSFyW
@karlhigley 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.
https://t.co/QVLkpZRLtA
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.
https://t.co/3NTNgg72le
📢 Blogged: "What's in a Good Error Message?"
Discussing some recommendations for designing error messages in libraries and frameworks.
https://t.co/RUmw8OK2Jb