You are not a co founder, you are an employee. hint. founders get shares, employees get options.
you are now in the situation of whatever you can bargain for, you can get, whatever you can't bargain for, you don't get. Dealing with what you call a highly risk adverse person makes it hard to negotiate, because the most risk adverse action is bury the code and say goodbye (what they have proposed). It is likely you can change the action only by suggesting a less risky course of action.
I have been in a similar situation before, and tried to use Greed when only Fear was going to work. Many situations are like this. I now know more about sales now. I didn't get the source code (which I wrote and was useless to them) and it was probably for the best. If I didn't have the motivation to rewrite, i didn't have the motivation to start a company. Likewise, if you don't have the motivation to get new, fresh code written, you don't succeed either. There are many many ways to get code made, if you believe in this, find one. it will be the first of many trials.
According to the post, neither of them have vested shares:
> We signed a founders agreement, we each have a seat on the board, and he holds a majority of shares. None of our shares have vested - my first vesting date is in 6 months when ¼ of my shares vest.
Unvested shares are still shares. All that being unvested means is that the shares are subject to conditions such as a repurchase option that gives the company a right to buy your shares if you leave the company.
Unvested shares still have the others rights of shares, such as voting and sharing in dividends.
Vesting is just receiving the full rights of the share, option, or whatever over a specific amount of time.
If you start a company with someone you don't (er, shouldn't) just automatically get 50% of the company. That would allow you walk on day 3 and still own 50%. Instead you receive the ability to leave with your shares on a vesting schedule so that you have skin in the game.
Yes this is correct - apologize if I wasn't clear with this. From what I understand and my previous experiences at startups it was a standard vesting structure where ownership vests over 4-years with a 1-year cliff (or at an acquisition event). On day-1 neither I nor my co-founder had any shares vested.
Your credit score matters far less than you think.
Your credit score is maintained by a bunch of goons in a protection racket. 'Shame if anything would happen to that fine credit score, let me 'protect' it for you".
Unfortunately, there are few legal standards in this area. Any business can report that you have not paid something.
Write a letter to google's corporate address with all your evidence, enclose a literal paper check, keep a copy of everything. Point out in your cover letter that you are discharging your responsibilities especially regarding collections, and collections will be considered an illegal action. If it comes back and harms you, you have cause of action and documentation. Take whatever action is appropriate for harm (apparently arbitration can be really good for small cases like this, less hurdles, more getting the companies money).
> Your credit score matters far less than you think.
... uh... this is the worst financial advice i have ever heard with regards to someone living in the US.
credit scores aren't _just_ about if you get a loan or a credit card. They're used to determine if you're a safe hire. They're used when calculating your insurance rate (house / car / whatever). They're used when determining if they should rent an apartment to you.
I'm not saying these are _wise_ uses of it, but they _are_ uses of it.
Care to comment a bit further about losing data? There are two different persistence methods offered by Redis at the moment. https://redis.io/topics/persistence
It is a reasonable shorthand to say the only interesting transactions are multi row, and thus big table doesn't support transactions. More correctly, the only transactional guarantees are single row, sure. But saying it does support transactions is misleading.
Spoken as a guy whose database did not support multi row transactions and was always told that.
It'd be reasonable to understand the underlying model, however.
A "row" in BigTable is multi-level map that can grow large (100s MB). So you can essentially encode and entire star schema on that.
The full structure is row -> column-families -> qualifiers -> timesamps -> values
Why would it matter how they do it under the covers? You see correct transactions. The interesting tech in this space is aws redshift, in my testing a few years ago they dominated in price performance when you used the then new node types.
>Why would it matter how they do it under the covers?
It doesn't really matter, I suppose I just got nerd-sniped recalling the details of Spanner's internals and their (somewhat superficial) relevance to the issues of timekeeping mentioned in the blog post :)
Bittorrent clients for windows and mac are generally malware infested pits of adware. Wherever i try to be virtuous and use one, i have to clean whatever i installed. I am sure i am not the only one.
Why not build your own install using the bittorrent libraries? The security model is more complicated, for one. If i was an architect and proposed that, i would have to understand the attack vectors and present why they are than the well known solution. And taking control of the software update channel is a massive risk.
Second, i have less control of the user experience. With http, i can pay for the right amount of bandwidth, or time on a cdn. If i implement bittorrent, i still have to have buy capacity, i just have a more complicated model for how much to buy.
Suggested updates can be spread over time - and need to be, for canary purposes. I think Android often pushes an app update over 4 or 5 days, by default? Steady state infra capacity, or even better, low priority which and be interrupted, is cheap.
Given the complexity and business risk (people can't download our software! Our binary got hijacked! Two code paths to test?) And the inexpensive nature of mirrors, and the competence of cdns, there are rarely causes where it would make sense.
Google maps results are on their way to death. I was recently doing a search having gone down to a three block area, did not show the result - Google pulled out a few blocks and showed a category result there. There was a higher ranking category result in the block i remembered, i had to remove my search term and zoom in!
The problem is not ads, it is not even capitalism, is the requirement of our western capitalism to require constant growth. Doing what Google did 5 years ago, with the profits of 5 of years ago, should have been fine - but the markets demand growth, so companies have to pull into unsustainable territory and that wrecks the company.
Boeing is a great modern example.
No one ever really expected much of reddit. It could just do its thing. But now, spun off, it will have to relentlessly seek growth, and the counter is ticking for its destruction.
While building all of airbnb is hard, let's look at a clone like outdoorsy, which is airbnb for rv's. It was very functional a year ago, and i doubt if it took a decent team more than a few months. The lore of how to build for scale is now far more widely known, and anyone doing dd on a codebase can figure out if scaling a monolith will require a full scorched earth or whether its has nice modularity allowing it to scale in flight, and/or get to fairly high scale with light application of autoscale shards and now commonplace cloud methodology.
The issue is brand and usability, and wordle has it. The method for social sharing is genius, i think. A great example of privacy by design (sharing is explicit and through an image not a share button going who knows where).
I transitioned from free gsuite to paid a few years ago. For my twelve (12) bucks a month, i get 2tb of storage, great mail services, all the docs i can write, etc.
When i compare to individual apps wanting $10 per month, this is probably my best monthly spend on my list. Fitness apps are the worst.
My main gripe is services that don't work with a paid account, like nest and home automation.
