Interesting to see comments suggesting use of constant recording as a defense against invasion of privacy via constant surveillance.
Interesting that the defense against the harms of technology is technology itself. When the humankind unlocks a new powerful technology, and when it is possible for criminals to use the technology to harm us, our best course of action may be, not to look away from it out of fear, but to spend more time understanding it and its implications, and to get there faster than adversaries do.
Just go to point X directly. Too many people shy away from their dreams and delay, because they want to learn first, practice first, and get ready before the real adventure. You will never deplete "more things to learn". You are only depleting your lifetime. And no matter how close working at a startup is to working on a startup, it will never be as close to it as itself.
If you need to save up some money or take care of any other blockers first for your own safety, fine. If there is a great company working on a great problem that you are excited by, great. But if you want to start a new company, then working at a startup is not a practice for starting a new startup. It is a practice for working at a startup and a practice for wasting another day of your life not living the way you really want to live.
The reality requires balance. For example, in university courses, prerequisites are required and enforced for good reason.
People try all the time to learn calculus with a weak foundation in precalculus, and they really struggle unnecessary. People also try to learn physics with a weak foundation in mathematics, with similar results. I would argue that the same is true for software development. You can develop bad habits (e.g. not using a style guide at all) by not doing initial prep work first first.
I agree that some people put things off indefinitely and end up in "tutorial hell," and for them it's better to err to going right to doing. But it's not always the case, and sometimes educational opportunities (e.g. getting work experience before starting a company) can really increase your skills.
> I would argue that the same is true for software development.
One can learn best practices without having to work at a startup / tech shop / MANGA. Besides, software development isn't the only skill required, there's likely a lot to learn but not enough time. With most upstarts, timing is more crucial than most other learnable factors, because you can never rollback time.
Very few things can clear this hurdle, and even less so the sorts of things that tend to come up on HN. Very, very few industrial farming topics come up on here for example.
Perhaps a more apt framework would be, "What's the reason someone is giving you money for this product?"
I assume it's because "value prop" is VC lingo which is a prompt to founders to give their customer "elevator pitch", and we're on community forum that's motivated by VC perspectives & lexicon, so those get broadly appropriated by many participants.
Just to let you know, the privacy policy makes it sound like users can. Under "The rights of Users," it states (source: https://emery.to/privacy/): "Users have the right to receive their Data in a structured, commonly used and machine readable format and, if technically feasible, to have it transmitted to another controller without any hindrance. This provision is applicable provided that the Data is processed by automated means and that the processing is based on the User's consent, on a contract which the User is part of or on pre-contractual obligations thereof."
Maybe there is a manual option on the company's end that makes this assurance valid?
Interesting that the defense against the harms of technology is technology itself. When the humankind unlocks a new powerful technology, and when it is possible for criminals to use the technology to harm us, our best course of action may be, not to look away from it out of fear, but to spend more time understanding it and its implications, and to get there faster than adversaries do.