Article: An await in a loop runs one request at a time
az.dev/read/an-await-in-a-lo…
263
Reading code is a more valuable skill right now than writing it, and almost nobody trains it on purpose.
We spent years writing from scratch — school, tutorials, side projects. Nobody gave us that same practice at sitting with code we didn't write and deciding if it's right.
4
184
The cost of an abstraction is usually paid by the next person who reads it, not the person who wrote it.
Writing the clever generic helper is fast and fun. Understanding it six months later, with no memory of why, takes real time — and it's usually someone else who spends it.
2
167
Git tip:
When you reformat a file, put that in its own commit, separate from any real change.
git add path/to/file
git commit -m "reformat: file"
This keeps your diffs reviewable. A commit that's 200 lines of whitespace and 3 lines of real logic buries the 3 lines that matter.
114
Me: number + array
JavaScript: Sure, I’ll assume you meant converting them both to strings first? Got it
TypeScript: WTF
TypeScript tip:
If you don't know the type of something, use `unknown` instead of `any`
any basically means I don't care about this type, just let me do anything on it. That's bad
unknown, however, means I don't know this type and I'm not really using it. That's much better
What pattern do you use to name your GraphQL operations?
71%createUser
7%userCreate
21%Something else (?)
14 votes • Final results 1
Learning React or Node today?
Retweet and follow, and I'll DM you a 100% coupon code for my 2 books, React beyond the basics and Node beyond the basics.
Note: The books are still a WIP so any feedback will be greatly appreciated.
Happy Father's Day to all dads and single moms!
Git tip:
Put any non-significant changes that do not affect the code in separate commits.
Examples: trailing whitespaces/eol, code formatting
Don't mix them with other code changes because it makes reviewing a lot harder.
1
8
