It'll need to be shut down anyway to pull the giant metal chain out. You might as well do it right away. Patients can and will be rescheduled to other MRI facilities.

Sexing is typically done immediately after hatching, yes.

They don't feed male chicks - from the first paragraph:

> in the United States alone, approximately 350 million male chicks are routinely culled each year, typically by methods such as maceration (being ground up alive).

but they'd save on incubating the eggs which they could otherwise use or sell.

I suppose that is true. But I imagine that the scale of egg incubation to produce hens is a relatively small portion of total egg production, since each hen produces many eggs. You'd probably have to compare the cost of incubating an egg and the labor to manually sex the chick to the per-egg cost of this technology. I would be surprised if that comes out in favor of the in-egg-sexing tech right now, but it would be great if it did.

What’s a good way to Airplay to your own speakers?

Buy an older Apple TV, or an Amazon Fire. Connect them to your receiver and you're good to go. Or buy a newer Yamaha or Denon receiver and they'll be ready to go out of the box.

The "Not a Simple Operation" section really stands out for its GPT writing style ("While [pro], it's important to note [con]", "In short...").

The reason that ChatGPT and other LLMs use such language is because they often find it in the corpus of text they’ve ingested. It’s a frequent pattern in writing.

So, I don’t necessarily think that’s an immediate red flag. To be sure, I guess you’d need to go back and look at the author’s previous stories and compare writing styles.

I went to one of these this summer and had to create a full corporate account online before the people at the front desk could sell me a day pass, and I was bombarded with emails for months afterwards about signing up the rest of my "company"

I went to a wework for the first time today and they technically set up a whole corporate account for just me to be there for one day to try it out.

Today? Was this disaster tourism?

They are in chapter 11, which is aimed at reorganizing a company. They hope to still be a business going forward.

For customers, it should still be relatively the same service. I expect some amenities to change, but you should still be able to rent a desk (for at least the near term).

As mbreeze stated, this location is probably going to continue operating as some form of coworking space even if it gets spun off of wework, which it may or it may not. There were a lot of people there, I imagine that location is probably cash flow positive. It would make sense for someone to operate it, as there was clearly demand at least at that location.

I would add https://blumira.com to that list; it's more mature than at least a few of these (I'm a former employee)

What makes you call your current review culture “sane”? I’m not sure I have seen that yet in my career.

YMMV but i work at a place where

* code review is expected responsibility, so everyone participates in every part of it regularly, so they are also incentivized to keep the process sane

* we have an auto linter and we recommend saving on fix specifically so no one argues about useless style nits

* CR back and forth is measured in minutes or hours so you are not waiting days to resolve someone’s drive by comment

* CR feedback always has a specific action item that is easy to address

* reviewees submit smaller CRs which are quick and easy to review for reviewers

> * CR feedback always has a specific action item that is easy to address

Then CRs are pretty much pointless. The feedback I want as a senior developer is the complex stuff and that is half of the time not easy to address. The trivial stuff I usually, but not always, spot myself when checking the code before sending it for a review.

You ideally want that earlier and more high level than a code review.

If you are doing system/algorithm design in the code review, it’s not meant for that.

The action item can also be “can we create a issue to track and discuss this further”

Reviewers are responsible for not just pointing out issues, but also providing (at a minimum) some form of direction, or (more ideally) one or more explicit suggestions as to how to resolve those issues.

This is an essential component of a productive code review culture.

Yeah, a good review must explain why, and should ideally explain how it should be instead if it needs explaining.

* This code should be changed looks bad - not a good comment

* This code should be chabged because ten nested ternaries gets hard to read - better

* This code is hard to read because there are ten nested ternaries. Can we replace it with a helper method that returns one value using if blocks? - best, in terms of actionability

This right here! It makes for a sane, friendly culture, and junior team members also get to learn during the code review process.

Prioritize code reviews over development work. Have SLAs. If you are assigned a CR, get to a good stopping place, pause your work, do the CR, and resume. Close CRs that have become stale due to submitter abandonment.

+1, every PR should ideally be reviewed within a day, and certainly within a week.

that's exactly what it does.

It’s definitely related to the moral license thing in my opinion. As a cyclist there are a lot of bad drivers out there, but I’ve learned to treat every Tesla like I do lifted trucks. I think they feel that they are at the top of the moral hierarchy and forget about pedestrians and cyclists completely.

Not all of them, obviously, but enough.