For, your use case of user changes, CRDTs seem like a good option. It would be interesting to explore building a version control system on top of CRDTs, if done right it could have the benefits of git with less merge conflicts.
167 karma · joined October 8, 2014
github.com enxyz angel.co ericnorman
YC Badge: 0xc88820acd35775d9adea1e4c9cfd0c6879621cc0
For, your use case of user changes, CRDTs seem like a good option. It would be interesting to explore building a version control system on top of CRDTs, if done right it could have the benefits of git with less merge conflicts.
>If hard work and long hours could be consistently transformed into “success”, then my friends and family who are teachers, nurses, social workers and factory workers would be far more successful than I am.
> 2014 June > So, we give IAP a try. That means we are now charged Apple's 30% tax and sadly have to increase our price for our fans... to €12.99 a month.
> 2015 June > Because Apple Music doesn’t have to pay the 30% IAP charge, they are able to hugely undercut us and charge €9.99. To our fans, this just looked like we were ripping you off
> 2016 May > We opt out of Apple's payment system and the artificially uncompetitive price we had to charge for using it
This one in particular feels like good advice to startup founders as their company grows:
> Trying to take on multiple roles.# In past PagerDuty incidents, we've had instances where the Incident Commander has started to assume the Subject Matter Expert role and attempted to solve the problem themselves. This usually happens when the IC is an engineer in their day-to-day role. They are in an incident where the cause appears to be a system they know very well and have the requisite knowledge to fix. Wanting to solve the incident quickly, the IC will start to try and solve the problem. Sometimes you might get lucky and it will resolve the incident, but most of the time the immediately visible issue isn't necessarily the underlying cause of the incident. By the time that becomes apparent, you have an Incident Commander who is not paying attention to the other systems and is just focussed on the one problem in front of them. This effectively means there's no incident commander, as they would be busy trying to fix the problem. Inevitably, the problem turns out to be much bigger than anticipated and the response has become completely derailed.
A large reason not to share things is some info is sensitive, for example the share count is a useful number, while the full cap table with each investor’s pricing, terms, and contact info, and other employee grants, would be sensitive and might be more guarded. Same thing about total revenue versus the customer list.
More traditional advice is to ask about the fully diluted share count, so you can see what percentage the options would be, and of course the vesting schedule and purchase terms. Also I’d also ask about cash or runway, which is related to the ability to survive a rough patch.
I was CEO and founder of a YC funded startup and have some experience hiring at the seed stage. For me personally, I wanted engaged people and asking good questions was a positive sign.
(Disclosure: Don is a relative.)
>To detect whether there is something in front of the iPhone X, it is believed that the phone uses a "time-of-flight" (TOF) sensor, powered by an LED-based infrared illuminator... If the TOF sensor detects an object, it triggers the iPhone X's True Depth camera to take a picture. If that reveals a face, the phone activates its dot projector, shining a single infrared VCSEL through an optical system to create 30,000 spots while its infrared camera captures an image. It sends both regular and spottily illuminated IR face images to an application-processing unit (APU) that can recognize the owner and therefore unlock the phone.
Actually it might be possible to hack if your screen could output IR wavelengths.
https://www.sec.gov/Archives/edgar/data/320193/0000320193170...
“Instead of building your own ground station or entering in to a long-term contract, you can make use of AWS Ground Station on an as-needed, pay-as-you-go basis... You don’t need to build or maintain antennas, and can focus on your work or research.
“We’re starting out with a pair of ground stations today, and will have 12 in operation by mid-2019. ... [T]he raw analog data from the satellite is processed ... and routed to an EC2 instance that is responsible for doing the signal processing to turn it into a byte stream.”
I get the sense that there’s a gem in your scripting, and one of those might become useful and need more work, and then you’d have a reason to scale it.
There’s [a recent interview with PG](https://www.startupschool.org/videos/36) where he talks about the joys of hacking, you might find it interesting.
Somehow in hardware this seems crazy and there's a million reasons not to actually sell the product (certification, hard to change in the field, it's expensive!), so I think it's done less often.
The Mayo story seems like something else. While you might learn something by buying the product in retail once or twice, buying in bulk to simulate demand isn't an acceleration to learning something. It's this thought that if only people could find my product, or have an easy way to buy it, it will sell. But once you stop buying, the effect goes away. It reminds me more of a dilemma that larger companies talk about: juicing this quarter's earnings at the expense of next year's.