Thread by @rsms

Re building tools: I strongly believe that tools — software libraries, utilities, etc. — should only be created to solve an issue which you have a direct relationship to. History has proven this to be an excellent measure of success.
[Thread ...]

Most of us have probably experienced the "CRM system made for other people" that sucks, because the creators of it didn't use it themselves and thus couldn't relate to the problems their thing was solving.

So here's some good terminology:
- "Me ware"
- "Us ware"
- "Them ware"

"Them ware" is the worst possible thing; a "none of the roads taken" kind of compromise. You build something for someone else without a need of yourself. It will be incredibly hard to make something good this way since you will essentially fly blind.

"Me ware" is where most great things start, by solving an issue or realizing an opportunity which you can directly relate to, in the most straight-forward way possible.

"Us ware" is what "Me ware" hopefully becomes when it is useful for others.

However starting with "Us ware" is risky — this is what many tech start-up do; they just have a quick sip of "Me ware" and see that there's an opportunity in solving this for others at the same time \

[...] as solving it for ourselves is a good strategy. Often that is a time-efficient way to do it, but it does come with a higher risk since you'll be finding out if it's even "Me ware" after you've made some pretty big investments.

Summary:
- Avoid "Them ware"
- Start with "Me ware"
- Cherry pick "Me ware" that has helped you a lot and make it "Us ware"

Addendum:
Don’t take this advice as “only solve my own problems” but rather: whatever you are working towards, make sure you really understand it by being able to personally relate to it and eventually benefit from it. Use research, change your life habits… whatever it takes.