Most "valuation events" for startups are seed or series X fundraisers, no? So how could founders who bootstrap participate in this, if at all?
234 karma · joined December 7, 2016
https://github.com/whatl3y
https://lance.to
[ my public key: https://keybase.io/whatl3y; my proof: https://keybase.io/whatl3y/sigs/LY68u61-jMyMVoAU-iLUMvuI72WBOe879q-XSLTwQUE ]
Most "valuation events" for startups are seed or series X fundraisers, no? So how could founders who bootstrap participate in this, if at all?
> crypto currencies are a good solution for one thing only: electronic currencies.
You contradict yourself by stating above you believe there's only one valid use case for blockchain, but in your most recent comment you obviously admit there are several valid use cases (though admittedly a limited number). Maybe your initial comment was meant for emphasis and not literally that you believe there is only one use case, but be careful using quantifiable verbiage or hard numbers to portray emphasis without explicitly stating that's what you're doing, your credibility gets called into question when doing so.
What is a better solution than building a tamper proof workflow in the blockchain? Examples include:
1. I sign a contract and the notary signs and uploads a copy to the blockchain to validate the contract contents, that it was signed and by whom, and when.
2. An auditor validates a piece of evidence a client provides that proves its in compliance with a particular control in some regulatory framework. The auditor uploads a SHA256 hash of the evidence in a transaction memo to the blockchain to validate against later in peer review, a lawsuit, etc.
Edit: My examples here refer to a valid use case of a blockchain and not cryptocurrencies which is what you mention, but based on context of this discussion it looks like we all actually mean blockchain and not necessarily cryptocurrency.
In saying that, I’ve always understood and expected minimum wage jobs to be one of a couple things:
1. A first job for young people who live with their parents, or at least aren’t depended on to pay the bills, who want to cut their teeth with what it looks like to have a job and/or have some extra spending money
2. A non bread winning family member looking to contribute a little towards day to day bills
Is there documentation or something from the government that outlines expectations for exactly what the minimum wage is supposed to accomplish for a person? Is it intended to be a “living wage” or arbitrarily set to something that folks in charge deem appropriate for some reason unbeknownst to me?
If it’s supposed to be a living wage it should be data driven based on cost of living and evaluated on a relatively high frequency (at least once per year). I know this is a hot political topic, but it just seems like another issue that we could use actual data to solve based on intent of what minimum wage should be instead of poking the right or left bears and polarizing the world more than it already is.
If you're a relatively small company looking to use a plug-and-play SaaS product with a modest subscription fee to serve some business purpose this is a great tool to get some quick and dirty numbers on whether it would be better to use or maybe build in house or go another route.
If you're purchasing some large, highly configurable enterprise tool (with high implementation and support costs) that all 1k of your employees will use daily and you'd like to understand cost/benefit, other means of calculating this should be used (and it would likely require days to weeks of multiple people's time to make such a calculation).
The first time I went through it I had no idea what was going on and for the ~60 seconds that it lasted I went from thinking if this was really happening to whether I would be able to tell my family I loved them again. The subsequent 3 or 4 times I experienced it (after extensive research following the first episode) I repeated the thought that this was temporary and would go away soon forcefully until it in fact did after 60-90 seconds.
I know this is an evolutionary defense mechanism our brain/brain stem have developed over time, but wow is it awful if you ever go through it.
If nothing else I’m smarter and know a little more about what I didn’t know (and still don’t) which I find a ton of value in. Hopefully I’m slowly ridding the world of my contribution to the “ignorance” category you mention above which I admit to have been in wrt developing a secure password manager, but either way I enjoyed learning along the way.
Nonetheless I appreciate the last bullet as I definitely post to Show HN to learn and get better as a developer, and certainly expect nothing less than to receive a few “fuck your shitty project”s along the way :)
- Got it, yeah I guess my defense would be it still requires the user to make a conscious decision so it’s not as bad as it being ambiguous or unclear, although removing the ability to control this via env var might be the right move.
- I’ll look into and add something to do this soon :)
I simply append the password to itself to get 32 bytes, but SHA256 is almost certainly the better/right way. Will add a PR this weekend.
- for your second point, if you want to fork this repo and use another algo, go for it. if you install the package from npm and use it or clone and install from source without changing it, it uses the default AES256
- this could be argued as a valid point, and maybe forcing the user to use 32 bytes as their password is the right way to do it, but no 3rd party password manager forces this limitation so i don’t believe I should? Maybe just forcing a password difficulty is the right way to go? I’m certainly open to ideas, this is just a small project i enjoyed building and feel like the minimum security requirements to meet my needs are there.
[0]: https://github.com/whatl3y/hide/blob/1c3aaca634f504c3c274bac...
It's amazing how almost universally visceral, impulsive responses such as this fail to provide references to such data.
I think the point is to strive to satisfy ease of usability and function for the highest percentage of users possible. If you have multiple personas of users who use your application, the amount of time you spend with the R&D of the UX to satisfy each persona should likely be proportional to the percentage of revenue each persona brings in.
I’m a backend developer who is pretty awful at developing good UIs, but damn I appreciate a good one when it comes along and feel like the part of the brain that’s used to build a very solid UI is a special one that not many people have developed.
A simple but possibly useful scenario could be at the time of recording a video, immediately storing a hash of its content on a blockchain somewhere to validate its authenticity later (if needed). Imagine if iPhone or Android did this by default whenever a video or picture were taken.
They’re brought together not necessarily by a strong belief that the Earth is flat (though most in the community strongly believe it, or at least pretend to) but because they were bullied as kids, socially awkward, had a hard time making and keeping friends, etc. From this angle I absolutely see how strong a connection these people might have to others in this community and why it would be hard to say “screw you only friends that I’ve ever had, your theories don’t make scientific sense”. They might lose the only friends they ever had.
This somewhat reminds me of the current state of politics. Why counter even a single belief, value, etc. that your echochamber has when they’re probably friends of yours and you know it could change your relationship for the worse (even though I think it’s ridiculous that questioning a political opinion with a well thought out, logically crafted counter opinion could ruin a relationship).
I need it almost daily. Being a developer and almost always in a terminal it’s convenient to retrieve a password really quick when needed.
> The software is designed to be sold to administrators and, as currently designed is unquestionably leading to worse outcomes for patients.
disclaimer: I’m a former Epic employee who worked on their inpatient app.
Do you have data or literature to support these statements for a typical Epic implementation or is this just anecdotal and biased?
Although there were ALWAYS some sort of issues and pushback from clinicians during implementation and go live, Epic software and data flow literally revolves around patient care and not billing. I don’t recall exactly which apps came first when Epic was born in the 1970s, but I believe their billing and admin apps came much later than many of the clinical apps. It’s actually why they still use a backend on top of mumps and cache, because the way data is stored and flows in these systems can do so literally around the core patient data structure, which should theoretically make a clinicians job easier to review a complete patient record (not make it easier for billing).
So it’s the opposite of what the normal behavior is, meaning the real client IP is guaranteed to be the last in the list. I probably should have a condition to get the IP based on this logic only if the app is hosted in heroku, then use the standard express way otherwise.