Think of this as a very old game, with a board simple enough you can trace it on the ground and play with a few stones, with rules simple enough you can explain/understand in 30 seconds. Like tic-tac-toe, mancala, nim, chopsticks... simplicity and portability wins over perfect rules or balance.
The only valid argument against HTTP GET with a body is that it has privacy/security risks.
Exist stuff (caches, CDN, etc.) could serve private information because the HTTP GET is cached without checking the request contents. The new standard can avoid this because old stuff does not know about HTTP QUERY.
The cofounders will not put your priorities first. Their only goal is to make money for themselves. They will axe you if they feel like it.
They are not hiring a founding engineer because they want to do something nice. They've probably realised this path is cheaper than hiring an external software development company.
Don't think for a second that you will be an equal in this relationship. You will be at their beck and call. You will be forced to write bad code to get early sales.
You'll get paid less to do more. I would stay where you are.
1. The best product rarely wins. As much as it pains me, marketing and sales matter more than product. Your competitors are likely better at marketing and selling themselves and their product.
2. It's a bit cliche, but look into the candy, vitamin, and painkiller theory. Your product is not a painkiller and I suspect it's a candy. Candies are very very hard to make a successful business from.
Marketing and sales has always been and will always be the problem of running a successful app or business.
I suggest he stops coding, like he said the product is better than his competitors, which is a great start. He should focus all his energy into solving this cosmic problem of marketing and sales and with time he will have users.
The "what" is important.
reply