My view on 💬 code comments has evolved. These days, I'm strict about leaving them.

1 reply

0 recast

1 reaction

🧪 I love that with 100% test coverage, if you discover a new bug, fix it, and add a test, you can be confident the changeset won't introduce regressions. https://github.com/0xProject/0x-parser/commit/d5c94d6fa2b8438d99a9f779d918372437ebb215

0 reply

0 recast

4 reactions

Hate when meh abstractions get added to solve small problems. Let those slide, and the whole codebase ends up full of abstractions that were premature or just plain wrong.

1 reply

1 recast

4 reactions

👩🏽‍💻 Published a new component this weekend! Demo: https://sheet-examples.vercel.app Code: https://github.com/sheet-ui/sheet Package: https://www.npmjs.com/package/@sheet-ui/sheet

0 reply

0 recast

0 reaction

I rarely use recursion, but when I do. I'll post it on my dev journal 🤩 https://github.com/0xProject/0x-parser/blob/main/src/utils/index.ts#L55-L62

0 reply

0 recast

1 reaction

is open source library ➡️ 100% test coverage is product market fit ➡️ ~80% test coverage is pre-product market fit ➡️ ~0% (or minimal) test coverage 🧪 wdyt?

0 reply

0 recast

1 reaction

Correct > Incorrect TypeScript > Typescript JavaScript > Javascript GitHub > Github 🥰

1 reply

1 recast

6 reactions

I've read this and recommend. A treasure trove of 💻 programming 🧠 insights.

1 reply

0 recast

3 reactions

Here’s a comparison of merge and rebase workflows in Git. I prefer the rebase workflow, where fast-forward merges are acceptable. The goal is to avoid three-way merge commits to maintain a linear history in Git.

1 reply

1 recast

1 reaction

Treating DRY (Don't Repeat Yourself) as a “best practice” can sometimes lead to poor abstraction and tight coupling. https://www.youtube.com/watch?v=rQlMtztiAoA

1 reply

0 recast

1 reaction