HN user

mstibbard

117 karma
Posts1
Comments46
View on HN

Is the long-term pricing model seat/usage based? Value based?

Consider how much you want/need to be charging customers in 3-5 years time and work backwards from there. Be open with early customers on these prices. Offer discounts (sometimes even permanent) against these target prices for early customers/design partners.

According to Wikipedia[1] it looks like the rebranding effort from Swagger -> OpenAPI was in November 2015, but the OpenAPI Specification was only officially renamed on 1st January 2016. OpenAI was founded on 10th December 2015. So it depends how pedantic we are being -- technically on branding, OpenAI predates OpenAPI by 21 days. In terms of the spec itself (as in, the thing they adopted), Swagger v1 was released August 2011.

[1] https://en.wikipedia.org/wiki/OpenAPI_Specification

FedNow Is Live 3 years ago

I think that was their point - the rest of the world solved this long ago, it is just the USA that lagged

Forcing consistent language, runtime, tooling etc is generally a good thing as it reduces ongoing operational burden as well as some retention & hiring dilemmas.

Fastmail brought out a Masked Email feature last year which does this for you! I'm a big fan.

"Keep your real email address private. We’ll create a new address you can use when subscribing to services online, that sends to your inbox. If you start receiving spam, you can block that address.

New Masked Email addresses will be created @fastmail.com. Want to use your custom domain? You can change this in Settings → Domains."

I think most "remotes" are within time zone-proximity.

The employment regulation burden is also massive for going truly global-remote.

Australia and NZ for example have strong employment laws AND do not overlap time zone-wise with most of the rest of the world. We have some great talent here but it's often too hard to make it work.

Disclaimer: I made https://rafo.com.au to collate remote jobs that work for Aussies & Kiwis.

Stock buybacks are (generally) done by companies when they think their stock is undervalued.

Stock buybacks destroy the quantity of shares that are bought by the company. E.g., if a company had 1,000 shares outstanding and bought back 100 of them, there's now only 900 shares outstanding. This benefits shareholders (assuming they didn't sell into the buyback) because each share is now a larger holding of the company (1/900 > 1/1000).

This decrease in shares outstanding normally corresponds to a share price increase.

I'd speculate that tech companies do buybacks as a way to keep employee remuneration high (via stock) without necessarily needing to pay them a lot of cash.

OP here.

I've recently departed Amazon to pursue building my own ideas. I decided to share some of my learnings as I go via substack - here's my first article :)

I am very keen to hear any thoughts or feedback you may have!

Cheers, MS

Most people won't post about it though. I had this exact issue (replaced the left airpod 2 weeks ago) but hadn't posted about it. Until this post, anyway!

What are you aiming to build? Without any additional detail I can say Elixir fits your criteria but may not be what you actually need! It's beginner friendly in my experience, cross-platform, and is a functional programming language which I'd put in the pros column for beginners.