Hacker Newsnew | past | comments | ask | show | jobs | submit | jimbobimbo's commentslogin

"Once those additional vaccines are off the "routine" schedule, they'll be pulled by the suppliers, because it eliminates exemption from lawsuits"

Why is this bad? From one of the threads - "There IS scrutiny on vaccines, by the scientific and medical community - your "scrutiny" (as presumably neither a PhD in a relevant field or MD) is not valuable or relevant. There is decades of research that says that currently recommended vaccines are safe and effective."

OK, then there won't be grounds for lawsuits or lawsuits will be easily dismissed.

"you can be sure there'll be a bunch of crackpot right-wingers trying to prove each one is "bad" and they'll disappear sooner or later" - This logic can be applied to literally any product, be it a medicine, a vaccine, or any consumer good. Somehow pharma companies are able to sell any other drug without going into bankruptcy.


Cerebral palsy, a naturally occuring disorder, generates $10M in "malpractice" payouts, part of why giving birth in USA is so expensive.

It is true. Withdrawals from SSRIs are no joke and can take a long time.


"But accepting the full S3Client here ties UploadReport to an interface that’s too broad. A fake must implement all the methods just to satisfy it."

In NET, one would simply mock one or two methods required by the implementation under the test. If I'm using Moq, then one would set it up in strict mode, to avoid surprises if unit under test starts calling something it didn't before.


That's exactly it. What happens in a private branch is an implementation detail and reflects personal work style. Policing that is counterproductive.


No one said anything about "policing" anything. I'm not telling anyone how to write PRs, I'm just suggesting that if we had better tools we'd get "better" PRs for values of "what happens in this 'private' branch is more than an implementation 'detail' but a useful story and a useful documentation of the process". You don't need to agree that is "objectively" or "universally" a "better" way to make PRs for everyone and every project, but I'd hope you could at least respect that it's a nice goal that some of us have at least some of the time and why we would like PR tools that respect that approach as much as they seem to already respect your "no one cares how the sausage is made" approach.


"Forward Deployed Engineer" is a bodyshop with LLM.


Weell, you probably don't want to serve "Backwards Deployed Engineers" to your clients


Pretty sure this title came from Palentir who got it from the military.


"Forward Deployed Software Engineer - This role includes working in locations that include risks of getting shot and possibly killed"


One-shot, one-kill.


They could just call it "Field Service Tech" like the rest of the universe. I understand using title inflation/deflation to keep pushing the engineer title (and pay expectation) into the dirt, but still, this is dumb.


I also dislike the term. It feels concocted to evoke “tacticool” vibes.

Unless you’re pushing new firmware onto a drone in Ukraine, FDE is stolen valor.


Might I interest you in "In the trenches" and "war stories"?


Ehh, I don’t think folks are claiming to be active duty or former military personnel, which is the bar for stolen valor accusations in my book. I agree with the sentiment but not with the determination of finding fault. Folks hired for a specific role rarely pick their own job titles.


Standard out-of-the-box Windows behavior: quick Alt-Tab press switches between last two windows; pinned apps on taskbar are switched with Win-1..9 shortcuts.


You actually don't need to. Just upload this little php script to a shared host for $1/mo and call it a day.


This applies to any company homed in the US. Not sure why Microsoft is singled out. Why Google, or Amazon, or Apple would oppose demands of the US government?


I suspect it was prompted by the specific story about Microsoft blocking that mailbox. So, that is probably why they were “singled out.”


Hello, author here - yes exactly. And also I don't think companies depend that completely on e.g. AWS


Maybe that's a good correction or follow up article to consider. These concerns aren't specific to Microsoft in any way. They apply to all tech companies that wish to operate within the United States.


It is a good point and a weaker spot of the article.

First of all, I now cover MS since this incident made headlines. If you are aware of any such incident from the other providers, I am interested.

Another argument is that more companies depend on MS more. Even in high-tech startups and scaleups you'll find traces of Win machines, AD and Office. On the other hand, there are plenty of companies that don't have AWS deployments at all.


Another thing worth noting is that out of GAFAM, Microsoft is the only one that really has vertical business integration that's worth anything, which is why they're the default for so many companies.

AWS is just a hyperscaler, they don't do the full business stack outside that. Google has a full business stack (read: office tools, email, hyperscaling) as an option, but the experience is miserable because Google constantly deprecates and changes things on a dime, which is why most people avoid them. Killedbygoogle stuff doesn't just apply to their non-paying customers, it applies to their paying customers as well. The moment you try to build anything outside of Gmail or Google Docs, you're subject to their whims and depreciation policies. (Case in point; Google has been sending me scare mails that they're going to kill an OAuth service I set up ages ago because it had no logins for 6 months. They just randomly decided it and gave me a month to deal with it. Their solution isn't just "hey, are you still active" - I am, that's easy to see - it's "just do a login and make sure you do a login every 6 months". If it was just a checkbox in their admin panel, I'd probably have done it without a second thought, but I really cba to figure out what the OAuth service was for, so I guess that OAuth service is gonna bite it now. Probably a selfhosted git forge or something that offered easy Google logins?)

Apple has everything except for hyperscaling, but it's all aimed at normal users, not corporations; I'm pretty sure they don't even have a business version of iCloud? The closest is that they offer MDM and bulk buying individual plans afaik. (Facebook isn't in this industry at all.)

Microsoft is the only one who offers a full kit and the promise that they won't pull the rug out under you. They're also the only one that really tries to take legal compliance and depreciation timelines/upgrade paths seriously. (AWS and Google just pass it off onto the customer with a "figure it out", while MS has loads of infrastructure for both of these.)

It's a hard business to replace if Microsoft goes bad with O365/Azure.


C# like language compiled to Javascript.


Documentation is actually better with LLMs. In 2010s+ majority of the docs is autogenerated doxygen and alike slop or some hello world in marketing speak. Absolutely useless. The ability of LLMs to hoover up everything related to the problem at hand improved my experience manyfold.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: