I had an informal expertise extraction conversation yesterday, with a senior software engineer I respect. The preliminary takeaway for software design expertise is that experts *attempt to predict the direction of change* for their software requirements, and design accordingly.
Hey all, been a web developer for more than a quarter century now. Wrote books about it, even. And to paraphrase @rachelandrew, my primary tech skill is knowing how to construct good search terms. twitter.com/ChrisFerdinand…
📦 How the Box Model works in CSS 🧵 Thread 👇 pic.twitter.com/DgL9vyhByu
✨ I'm happy to announce, that basetools.io is in beta! It is a paywall for your Github repository or npm package. Just connect to GitHub, set a price, and charge for access to your repository.
- Charge for access to a package
Nailed it! (via @whyarentucoding / whyarentyoucoding.com/meeting). pic.twitter.com/gZewCQBuGk
Over the past few months, we've looked at hundreds of technical blogs to compile the top entrants in each category. I'm really proud of the team at @draftdev for all their work, but here are a few of my favorites. 🧵 pic.twitter.com/yRvqxJJoWv
Seriously, code duplication should be adored and taught as the number one solution. Always. There's nothing more toxic for a long-term code maintenance than false / premature abstraction. DO repeat yourself until you are 💯 sure, that repetition comes from missing generalization.
- "DO repeat yourself until you are 100% sure, that repetition comes from missing."
I’ve reviewed over 750 PR’s at AWS. As my team’s tech lead I provide insightful feedback and enforce a high code quality bar. But as a jr engineer I couldn’t review code. I didn’t know where to start, what to look for or how to comment. Here’s how I review PR’s. 🧵 👇
- Agree with notes on how to do this well, although I think the PR process is outdated & inefficient. Everything below is important long term, but I would take a review that brings the functionality & UX up to par over one that makes code more readable. With advent of PR apps (Heroku & Netlify), it'd be cool to see UX/usability also becoming part of code review.
- Code reviews purpose:
- Coaching opportunity.
- Strengthen readability & system understanding.
- Read code deeply to get a good understanding.
- "avoid using “you” or “your."
- "prefix nitpicks with “nit.”
- "I approve when and only when the PR is good enough."