HN user

siliconwrath

108 karma
Posts1
Comments29
View on HN

Statement from Michael and Susan Pretti Parents of Alex Jeffrey Pretti "We are heartbroken but also very angry. Alex was a kindhearted soul who cared deeply for his family and friends and also the American veterans whom he cared for as an ICU nurse at the Minneapolis VA hospital. Alex wanted to make a difference in this world. Unfortunately, he will not be with us to see his impact. I do not throw around the 'hero' term lightly. However, his last thought and act was to protect a woman. The sickening lies told about our son by the administration are reprehensible and disgusting. Alex is clearly not holding a gun when attacked by Trump's murdering and cowardly ICE thugs. He had his phone in his right hand and his empty left hand is raised above his head while trying to protect the woman ICE just pushed down, all while being pepper sprayed. Please get the truth out about our son. He was a good man. Thank You.

https://www.nbcnews.com/news/us-news/alex-pretti-fatally-sho...

Another case I’ve seen is to separate a specific part of the system which has regulatory or compliance requirements that might be challenging to support for the rest of the larger system, eg HIPAA compliance, PCI compliance, etc.

(To clarify, I’m not disagreeing with you!)

I’ve had to report AI summaries to Google several times for telling me restaurant items don’t contain ingredients I'm allergic to, when the cited “source” allergen menu says otherwise. They’re gonna kill someone.

I’m no Tesla fanboy, but franchise models exist now, why couldn’t it work for cars?

Leasing cars to Uber drivers has taken off in the last decade. No reason for Tesla to sit on a quickly depreciating asset like a car if they can double dip (initial purchase and Taxi profit share) without having to pay for electricity, depreciation, or maintenance.

If the guy taking orders doesn’t have to take orders in addition to his other work anymore, they can hire less staff overall.

With a true GPT ordering experience, you would just say “a Big Mac and a diet coke please” to a speaker just like you would in a drive thru and it would ring you up. It would replace the cashier

Gifthealth | https://gifthealth.com | Senior Software Engineers | Remote US (Full-time)

We're looking for experienced, product-minded software engineers with experience working with Ruby on Rails or similar tools (e.g. Django).

Gifthealth is on a mission to bring an easier, more affordable pharmacy experience to patients and providers around the country. Since our founding in 2020, we've served hundreds of thousands of patients and are growing quickly.

Listed as Hybrid but we are also hiring remotely: https://gifthealthoh.bamboohr.com/careers/122

Feel free to email me at mike (at) gifthealth.com for any questions.

I obviously don’t know the specifics, but US healthcare plans only let you change during specific enrollment periods or qualifying life events. It’s possible he wasn’t able to.

Additionally, it sounds like he picked what appeared to be the best rated plan available to him on the market. Others may have been even worse or prohibitively expensive.

With document DBs you still have "schemas", they just won't be explicit at the database layer. If you rename a field your app uses, you will end up having to either rename that field in every document, or punt on migrating and instead ensure that your app can handle either field name when reading.

While the latter may sound easier (and often is easier when you're starting out and iterating quickly), you will soon start to feel the pain of managing dozens of different versions of your "schema" at the app layer. I've always found it easier to only have to deal with a single schema at a time in any situation where you can't just regenerate all records on the fly, like a cache, and for which you don't care about what the specific schema was at a point in time.

If you actually do care about what the schema was at any point in time at the app layer, your app WILL need to account for any version of the data—but if you need this you're accepting the tradeoffs of the additional complexity.

Definitely more nuanced than "no migrations = easier" though.

It certainly does look bad for self driving vehicles, and I definitely feel terrible that a life was lost from this.

However, how does one develop a self driving vehicle that’s 100% automated without the ability to test in real driving conditions? Despite this accident, self-driving vehicles have a fairly safe driving record for the number of miles and time they have been active.

Details on California accident rates for self driving vehicles, for example, show mostly minor fender benders despite more frequent accidents: http://journals.plos.org/plosone/article?id=10.1371/journal....

Which breaking changes? The React team just rewrote the entire core of the library and kept the same API; that’s pretty impressive.

Regarding the point about Google/other large company easily being able to build something that can put your company out of business: it's a valid concern, but what if the exit strategy is to be purchased by Google?