atjoslin
Joined 14 years ago
Joined 14 years ago
Now linting full codebase on precommit and it’s faster than just linting staged files with prettier!
Lots of under promising. Aggressively, even when you get tired of it.
EDIT: Nevermind, I did not read the article before commenting. My mistake.
I agree, but I hate TODOs. They're the worst form of keeping track of technical debt.
Just open a ticket! I like to have a tag/label called "debt" that I put these "TODO, bad implementation" type of problems under.
That way at least it's tracked.
With Surge, I'd have to trust some startup's build tool not to fail at a vital time.
Does that mean that they don't have to pay sales tax on any of these preorders?
A good micro-module removes complexity. It has one simple purpose, is tested, and you can read the code yourself in less than 30 seconds to know what's happening.
Take left-pad, for example. Super simple function, 1 minute to write, right? Yes.
But check out this PR that fixes an edge case: https://github.com/azer/left-pad/pull/1
The fact of the matter is: every line of code I write myself is a commitment: more to keep in mind, more to test, more to worry about.
If I can read left-pad's code in 30 seconds, know it's more likely to handle edge cases, and not have to write it myself, I'm happy.
The fault in this left-pad drama is not "people using micro-modules". The fault is in npm itself: all of this drama happened only because npm is mutable. We should focus on fixing that.