Beefin

Live in dc and have done the 180 miles of the C&O, it’s absolutely beautiful. You’re in nature pretty much the whole way.

As a backpacker I totally understand the appeal, only challenge I foresee is where to set up campgrounds so its secluded, flat and legal.

I wonder if anybody uses smell as a mnemonic device when studying. Anybody have any examples of doing this themselves? It seems that since smell is so closely linked to memory we should be taking advantage of this.

whats the point asking for permission to give feedback? there is no denial for that request without looking looney.

isn't he all about resveratrol as well?

totally agree, this is my notion homepage and it's reduced A TON of stress:

https://imgur.com/a/qTsL3l3

Anybody have any sample Notion templates that outline this structure of Goal -> System -> Measurement?

dispute .w your CC company

Congrats on the launch! I too am in the healthcare technology industry, but I've consciously been staying clear of the telemedicine space. It just seems extremely saturated especially these days in a post-COVID era.

Last I checked there are over 500 active telemedicine companies out there.

How do you plan on differentiating yourselves outside of your specialist physician-base? And how will you get the tool in front of users? I feel like SEO will be challenging and you may have to rely on grassroots/guerilla marketing approaches partnering with hospitals/payers to showcase the total cost value saving of using your product.

A similar use case I've seen is in my city a doctor friend just launched her own SMS care service, which acts as a "buffer" before medicare recipients call 911. By getting their less serious questions answered and thus discouraged from "abusing" ambulatory services, the payers (CMS) are very happy paying for this service on a per patient basis. They then market the tool to their patients and even provide financial incentives for using it. Just an idea of how you can spread!

I wouldn't say arrays are bad, and the entire paradigm of data modeling in mongodb is to store your data based on your application usage patterns. if you have to query across multiple collections via a $lookup, then maybe you'd benefit from embedding the smaller of those collections into the former.

you're comparing $lookup, an operator that nosql isn't designed for to a join, an operator sql was designed for

A better comparison to FANG are Baine McKinsey and BCG. If you can get an offer at one you can likely get an offer at the other.

The equivalent of Deloitte could be Oracle. Decent brand name for your resume but you’ll be doing lame work.

> These letters indicate that potential layoffs or furloughs are possible in the near future as air travel demand continues to suffer due to COVID-19.

it's a warning of a furlough, not an actual furlough.

most of them have apple health connectivity. i have an oura, fitbit and whoop and they all sync into apple health.

Looks like from their chart [0] the WHOOP may be the most affordable, most comprehensive (relative to COVID) wearable out there.

I actually built something to provide a "single view" of monitoring individuals' wearable metrics [1], launched it via HN a couple days ago [2]

[0] https://www.frontiersin.org/files/Articles/558695/fdgth-02-0...

[1] https://meports.com

[2] https://news.ycombinator.com/item?id=23677773

education, problem:

how can we streamline the transfer of knowledge from the oldest, wisest, individuals on the cutting edge of their field to the youngest, most ambitious sponge-like individuals just starting out their careers?

I built an MVP to solve this at a hackathon: https://devpost.com/software/oravise

anyone interested in collaborating?

yep! go wilderness camping. resets everything! circadian rhythm, routine, mental fog, etc. and added benefit of understanding how insignificant you are in the world :) optimistic nihilism.

Yeah I always have to read in between the highly engineering/tech comments on HN. they're super useful but it's always challenging balancing these details /w shipping!

There is certainly a log of triggers that the subscriber can access. Any suggestions on how to make that distinction?

Hey! all data is encrypted on the client side (https://github.com/esteininger/pymongo-fle-example) and wiped after 30 days. if there are any data breaches, it will all be useless

Well, I'd like to try to form this into a business but am certainly open to open sourcing it at some point.

I go into very high level details on what's happening behind the scenes in this blog post:

https://medium.com/@esteininger/whats-a-paranoid-son-to-do-d...

You present valuable arguments, but in this environment shipping is more important than creating an appsec team or bug bounty program as a solo developer. I'm sure you understand :)

Hey! I go into a bit more technical details on the bottom of this blog post:

https://medium.com/@esteininger/whats-a-paranoid-son-to-do-d...

My parents are both immunocompromised (asthma & hypertension) so I set out to build an alerting tool which monitors their wearables (Fitbit, Apple Watch, Oura Ring, etc.) for COVID-like symptoms.

It's pretty simple and "set and forget", hopefully it's useful for others.

This is a good of the HN MDB hate: everything referenced has been addressed long before 2013. It was a new DB then and early adopters should know what they’re getting into

i agree, there's reputational impact but again it's the trade off that early adopters make and are fully aware of.

When you're the first user of a brand new companies' database, you better bet there will still be kinks they're working through and let's face it you're the guinea pig.

i'm sure mongo is thankful for all these guinea pigs because they helped to define the roadmap and iron out the bugs. however, in the end of the day 2009 version of a product is entirely different than 2020 version. there are endless analogies (facebook, google, etc.) the only difference with an open source technology is users can analyze it under a microscope.

SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qui"]}';

vs

db.api.find({tags:"qui"}, {guid:1, name:1})

No offense taken haha

DocumentDB is a great DB, but in the end of the day it's a forked version of 3.6-ish so it's missing a ton of new features like multi-collection ACID guaratneees. Plus, whenever you use DocumentDB you're accessing it via the MongoDB official drivers, so you'll be handling that compatibility mess yourself.