After publishing near 100 #TypeScript packages, I just realized that I am doing it wrong, and so are you (probably) 🧵
I looked at dozens of popular TypeScript libraries and virtually all of them have the same developer experience problem:
If you try to command+click the dependency in your IDE, it will take you to the .d.ts file... In this example, it is going to load index.d.ts of Turbowatch
...which is useless if you are trying to understand how module works b/c this file does not contain the actual source code.
Turns out, the fix is super simple! Just add "declarationMap"
With this simple change, now you can command+click on the dependency and it will take you straight to the source code 🤯, which is a _massive_ developer-experience improvement.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Sent my family a few photos generated using @dannypostmaa's HeadshotPro and they didn't pick up on the fact that they are AI generated... Not sure how to feel about this, but the future is going to be wild 🤯
It is definitely a numbers game though. There are those that look convincing...
First, the main goal of a commit is to introduce an atomic change.
Atomic changes contain only one feature, refactor, fix, etc.
A good commit allows to evaluate one change at a time and it contains only/all the changes necessary.
Bad commits happen because of a bad workflow.
Your workflow is rarely a reflection of what should be contained in a good commit, i.e.
9 times out of 10, if you commit using `git commit -a` you are making it a 💩 commit.
The workflow should be:
* finish developing the feature and test it
* think back through all the changes you had to make and how you would want to present them
* stage selected lines/rebase to create commits that introduce them in logical chunks/order
Equity for software engineers explained in layman's terms. 👇
(Personal opinions. Founder's perspective. Not a legal advice.)
First things first, equity issued at different stages of venture backed companies is hard to compare.
USD 100k worth of equity at an early stage company (pre-seed, Series A) might increase 5x-1,000x in value over time.
At later stages (Series D, [..]), it is unlikely to 2x.
For an employee of an early stage VC backed company, this means that while their salary is likely to only gradually increase, their equity value might increase several times in just the first year,
i.e. 100k worth of equity at Series A company ≠ 100k worth at Series D company.
Giving out inflated titles does as much harm to the company as it does to the individual.
For a company, it leads to a culture of entitlement, politics, and artificial aspirations not attached to the evolving goals of the business.
As an individual, an inflated title with nothing to show for signals either that you weren't successful or bad culture. Focus on articulating your accomplishments.