Modified version of Signal sent copies of messages to a central server for record retention compliance, but hackers have demonstrated the messages can be accessed on the server.
Ironically, I’ve read through many of the top comments and although there are many different opinions, I hadn’t seen any that came across as hostile until I read your comment.
If you partner with a healthcare provider to provide any sort of technical services, you will be required to sign a BAA (Business Associates Agreement), which makes you similarly liable to the HIPAA & HITECH acts.
>With persons or organizations (e.g., janitorial service or electrician) whose functions or services do not involve the use or disclosure of protected health information, and where any access to protected health information by such persons would be incidental, if at all.
Based on the context from the article of the PHI uploaded being incidental, it would probably fall under this exception. It sounds like ESHYFT isn't meant to be storing any PHI based on the privacy policy above.
You are arguing against no one. The person you initially replied to explaining RRR obviously isn't talking about RRRing bowling balls specifically. They are explaining the significance of and how to interpret the common way it's taught to reduce unnecessary production and consumption.
> I'm guessing you don't do it often (understandable if its not working for you).
For me pair programming accelerates development to much more than 2x.
The value of pair programming is inversely proportional to the expertise of the participant. Junior devs who pair with senior devs get a lot out of it, senior devs not so much.
GP is probably a more experienced dev, whereas you are the type of dev who says things like “I’m guessing that you…”.
I don't agree with this at all. Pairing where there's a big skill gap isn't proper pairing, it's more like mentoring or hands on training.
In pair programming as I learned it and as I have occasionally experienced it, two individuals challenge each other to be their best selves while also handing off tasks that break flow so that the pair as a whole is in constant flow. When it works this is a fantastic, productive, intense experience. I would agree that it is more than 2x as productive. I don't believe it's possible to achieve this state at all with a mismatched pair.
If this is the experience people have in mind, then it's not surprising that they think that those who think it's only for training juniors haven't actually tried it very much.
Exactly this. And I did mean equal skill when i said “more than 2x” implying that you get more done together than if you were separate.
One interesting thing is skill levels aren’t really comparable or equatable. I find pairing is productive where skills only partially overlap, meaning the authority on parts of implementation flows between participants, depending on the area you’re in.
I have some examples where I recently paired with a colleague for about 2-3 weeks nearly every day. i’m confident that what took us a month would be near impossible just working on our own
As a senior dev, when pairing with junious I get a more skilled team. Then I can continue to give new teams the skill and we all grow as people and companies.
> I'm happy to have something like SSE but the protocol needs more time to cook.
Just how well done do you like your protocols? SSE has been part of the WHATWG standard for almost 20 years.
Every protocol requires some sort of data encoding. For SSE you need to either restrict yourself to payloads that can never conflict with the message structure (e.g. an enumeration of short strings to indicate different sorts of events), or you need to encode the data.
It sounds like you are trying to send raw, unencoded data and are surprised that it sometimes conflicts with the message structure. Well of course it does! You can’t blame the protocol for that.
Every other protocol I've used has a standard way to encode arbitrary data, but especially text data, usually using some kind of escape sequence. SSE does not.
Just because it has been around for a long time does not mean it is well thought out or complete.
If this were a cash grab, why in the world would a scammer post this to Show HN, instead of targeting a much larger, less savvy customer base via a crowdfunding platform?
Anything is possible, but I don’t know why you would jump to that conclusion without taking the opportunity to engage with the OP.
