I think the point is too many times developers are a penny wise and a pound foolish when it comes to build vs buy. Because they can build, and it is often fun if you haven't done it before.
Though I often don't take my own advice, I try to ask is what I'm about to build core to our ROI/product, is there an existing solution that gets us 80% there, and yes, what is the cost.
If it is not core to the business, won't drive revenue, and cost are not outrageous, which is a company by company truth, then I much prefer to spend X time building new product than recreating an existing product/tool.
One final point - don't forget to consider the maintenance costs, which in the long term often greater then the initial investment. If your CI goes down, you just blew away and savings you were planning on.
It is the same as public markets, but just on a smaller scale. Instead of millions owning a % for $X, you have a few individuals/firms who agree % for $X. And you (the company) can exchange - tender offers, private sales, etc.
Just tried Readwise out - very nice! Pocket seems to have stagnated, so very refreshing to see innovation in the Instapaper/Pocket space. I know you all are working on a ton of things, but one suggestion is to add in other SSO options like Google (gmail). Right now I just see Amazon and Email.
Also when syncing with Pocket, perhaps mention it might take a bit to sync and you'll find the article in your Inbox - I thought the sync didn't work, but eventually appeared under Inbox, as opposed to where I expected in recently added.
I've been using Warp since it was announced on HN, and it is great. May favorite terminal yet. Fast, features such as autocomplete so much better than iTerm.
There is a lot of negative thoughts on this thread - would love to hear from the people who actually have tried out Warp and not those waxing on about the indignity of being asked to login to a free product.
A few weeks ago I saw a front-page Hacker News post on a new text based HTTP runner based on CURL and written in Rust called Hurl. Intriguing! We’ve been looking for a simpler way to run and test API requests against our social API. Here is how to use Hurl and some examples.
Really impressed. The ability to chain the http calls with assertions is great. The one thing I would prefer is to set the environment variables also in the .hurl file rather than in a .env file. Also, how do you access the key of a nested object?