stevehind

This resonates and one way to describe it is an incentive problem. Someone whose incentives are tightly aligned with the business is going to solve the actual problem and simply and effectively as possible. Someone who is incentivized to build career capital and experience other than via impact (e.g. so they can get uplevelled, pass an external interview loop, etc) is much more likely to focus on unimportant hard problems and/or over engineer.

yikes

ITT: people who like speaking power to truth.

Some real true colours being shown in these texts (including the other thread where Elon talks about what a “hardcore engineer” he is).

Seems really bad!

Anti-vaxxers are literally winding back the clock on human progress. So frustrating.

Have you contacted Azure? On one hand you owe the money “fair and square”, but on the other if I were them I’d waive an unexpected $10k bill to a good faith actor that was incurred without any proactive notification by Azure.

Great illustration of the US’ low state capacity. Whether that’s borne of lack or will or lack of ability starts to not matter at some point…

Out of curiosity what is the best counter argument to the general thesis, eg either what positives come entangled in the hot mess or reasons it’s not a hot mess?

Hmm turns out trustless and decentralised might not be the best model for all financial infrastructure.

A problem with making declarative statements about the future is you may change your mind and then be criticised. A problem with accepting below market pay is you may later regret it. There’s a clear fix to both and I don’t see any villains here.

For most reasonable applications that is basically a great advertisement for mailchimp, Eg if you rolled your own solution you’d only save eur 500 a year before accounting for the build and maintenance of your solution.

I've been a Dark beta user since last year and have built several small side projects on it. I think it's fantastic. But I'd describe it as "just code" and not "low code".

To make it work, you have to write all the code! However, you _don't_ have to worry about provisioning databases, deploying, etc, etc, etc.

Makes it really satisfying as a learning to build something and have it be live without getting stuck in heroku / mongodb / etc hell.

Thanks Zizee!

I tend to think not.

I think a better way to approach this is to think about the evolution of the equity split over time - i.e. how do the two of your "earn" the equity?

It might make sense now if he has the idea and you bring the skills that today the company is split 20% him, 10% you, 70% held aside for investment and staff.

If after six months you're still both working on the project then you've earned a lot of equity with your work, and he's earned some as well (assuming he's working in a sales / ops role). After 6 months it becomes 30% him, 30% you, 40% others.

After another year it's 40% each (or similar)... etc until you start taking funding and giving equity to staff.